Using device fingerprinting in the run transaction flow with an iframe

Before starting this tutorial, make sure you understand the following topics from the Quick start section:

If you are saving a card with the iframe while running a transaction, device fingerprinting is built into the flow. After you have created a fingerprint, it is automatically saved with the card token and then sent and purged with the first auth (or, after 12 hours of no use, the system automatically purges the fingerprint). Card tokens can be used to process through any MID on your account. They are not restricted to a specific merchant account or currency.

Generally, you use a device fingerprint for the first transaction with a card. Openpay requires a new device fingerprint to be created with every transaction (included by default with the Nexio iframe), while it is strongly recommended for Kount. For information about device fingerprinting requirements, see the gateway-specific information for the Connections you use.



In order to take advantage of device fingerprinting, you must meet one of the following prerequisites:

  • Kount must be enabled on the merchant account. If necessary, contact Integrations Support to ensure Kount is enabled on the merchant account.
  • You must have a gateway that requires a device fingerprint. For example, the Openpay gateway.

Running a transaction with a new card

In the run transaction flow with an iframe, use a device fingerprint with a new card by following these steps:

  1. Complete steps 1-6 of the Creating a card checkout page with the iframe tutorial.



    When the iframe loads, the following happens:

    • Kount data collector is automatically included.
    • If everything is working correctly, you'll see a fingerprintPosted event from the web browser.
  2. When the customer accesses the checkout page, completes the form, and submits the information, the transaction is processed and the card is saved to the Nexio vault (unless processingOptions.saveCardToken is set to false).

  3. Listen for Nexio's response to determine where to send the customer next. For example, a success page could be a receipt. You may also want to send a receipt to the customer via email.
    On success, the processed event contains the token object that you can save to your system for later use of the customer's saved card (specifically, the token.token parameter). For more information about this object, see the Iframe events topic in the Developer Tools section.

Running a transaction with a card that is on file

In order to run a transaction with a card that is on file, you must use the process specified in the run transaction flow with your own form tutorial.

See also

Alternately, you can use device fingerprinting with the following other options: