Device fingerprinting lets you log the attributes of the shopper device and analyze them during repeat visits of the same shopper.
Using the device fingerprint is optional.
The only risk rule that can take the device fingerprint into account as one of the variables is the velocity rule Shopper initiated a transaction more than X times within a time period.
If you decide to use the device fingerprint in this risk check, we recommend that you use it in combination with the other variables.
If you just started integrating with Adyen, or if you're already using one of our online payments integrations, we recommend that you use one or more of the other variables (shopper email address, shopper IP or persistent cookie) for the risk check Shopper initiated a transaction more than X times within a time period.
Adyen provides the options listed below to submit the device fingerprint for classic integration types.
Get the fingerprint
First, calculate a fingerprint on a client side and submit it to your server, along with other payment details.
Calculating the device fingerprint might take some time varying on the shopper's computer speed and Internet connection. Run fingerprinting on page load to ensure that the fingerprint is successfully calculated while a shopper fills out payment details.
To get the device fingerprint:
- Add a hidden field with any
idto your page.
Calculate a fingerprint for the hidden field by calling the
dfDofunction with the field's
idas a parameter.
If you want to calculate the device fingerprint dynamically, for example after the DOM is loaded, use the
dfSetfunction instead of
Below is an example form that calculates the device fingerprint using the
bar hidden field.
Submit the fingerprint to Adyen
After the device fingerprint is calculated and submitted to your server, include this fingerprint into the payment request in the
deviceFingerprint field value. The Adyen payments platform then uses this fingerprint for fraud checks on the payment request.