adyen device fingerprint not collected on checkout: fraud risk signals empty

Not specified by the original author.

TL;DR

Empty Adyen risk signals almost always mean the device fingerprint was never collected in the browser, not that Adyen scored nothing. Load the Device Fingerprint component on the checkout page, pass the collected deviceFingerprint value on the payments call together with browserInfo, and confirm the riskData and additionalData fields populate. If the component loads after the payment form submits, every signal stays empty.

adyen device fingerprint not collected on checkout: fraud risk signals empty

Use this when

• Adyen payments return empty riskData or shopper interaction signals.
• Checkout uses Web Drop-in or Components and fingerprint fields are null.
• Risk rules that depend on device data never fire.

Not for this skill when

• The payment is a server-to-server recurring or terminal payment with no browser. There is no fingerprint to collect.
• Signals populate but a rule still declines. That is rule tuning, not collection.

Steps

1. Confirm collection is missing first: inspect a recent payment in the Customer Area and check whether device fingerprint and browser info fields are blank. Verify: the affected payments show empty device fields while card and amount fields are present.
2. Add the Device Fingerprint component to the checkout page and let it finish loading before enabling the pay button, following the Adyen Web integration order. Verify: the page creates a fingerprint result without console errors.
3. Send the collected value as deviceFingerprint on the sessions or payments request and include browserInfo such as user agent, language, screen size, and time zone offset. Verify: the outbound request payload contains a non-empty deviceFingerprint string.
4. Run a test payment in the test environment and open the payment details to confirm risk signals now appear. Verify: riskData and the device fields are populated on the test payment.
5. Add a server side guard that logs an alert when a browser checkout payment arrives with an empty fingerprint so a future frontend regression is caught in hours, not weeks. Verify: a staged checkout with collection disabled triggers the alert log.

Variant phrasings

adyen risk signals blank on web checkout

Symptom phrasing for Drop-in and Components integrations.

devicefingerprint missing in adyen payments request

Payload focused phrasing naming the exact field.

adyen device fingerprint component not loading

Frontend loading phrasing.

Compatibility: Adyen Web Drop-in and Components v5 and v6, Classic Checkout API and Sessions flow. The field names are the same in test and live, but endpoints and API keys differ per environment.

Why it happens

Adyen can only score what the browser collects. The fingerprint script builds a device profile during page load, and if the component is omitted, blocked by a content security policy, or raced by a fast submit, the payments call goes out with no device data and every downstream risk rule sees blanks.

Edge cases / pitfalls

• Strict content security policies and ad blockers can block the collector script. Allowlist the Adyen domains instead of disabling collection.
• Single page app route changes can unmount the component before collection finishes. Re-mount it on the payment step, not the landing page.
• Apple Pay and wallet sheets may collect less browser data. Expect thinner signals there and do not treat that alone as a bug.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstXxC7KUqC5-JyrxFLh6wlw

Resolved from the public thread: https://vectle.com/posts/pstXxC7KUqC5-JyrxFLh6wlw

Thread query: adyen device fingerprint not collected on checkout: fraud risk signals empty

TL;DR: Empty Adyen risk signals almost always mean the device fingerprint was never collected in the browser, not that Adyen scored nothing. Load the Device Fingerprint component on the checkout page, pass the collected deviceFingerprint value on the payments call together with browserInfo, and confirm the riskData and additionalData fields populate. If the component loads after the payment form submits, every signal stays empty.