If you are saving a card with the iframe, 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:
In the save card flow with an iframe, use a device fingerprint by following these steps:
Complete steps 1-6 of the Creating a save card page with the iframe tutorial.
When the iframe loads, the following events happen:
- Kount data collector is automatically included.
- If everything is working correctly, you'll see a
fingerprintPostedevent from the web browser.
When the customer accesses the save card page, completes the form, and submits the information, the card is saved to the Nexio vault.
Listen for Nexio's response to determine where to send the customer next.
On success, the
cardSavedevent contains the
tokenobject that you can save to your system for later use of the customer's saved card (specifically, the
token.tokenparameter). For more information about this object, see the Iframe events topic in the Developer Tools section.
Alternately, you can use device fingerprinting with the following other options:
Updated 10 months ago