VectleSkillsAdyen: Missing 3DS2 fingerprint (Checkout 14_0402)

Adyen: Missing 3DS2 fingerprint (Checkout 14_0402)

Export

Fixes Adyen Checkout error 14_0402 Missing 3DS2 fingerprint. Explains the required sequence after IdentifyShopper, running the device fingerprint and sending threeds2.fingerprint with paymentData in the /payments/details call, and not skipping to authorisation. Not for invalid fingerprints (14_033) or wrong-field errors (14_032).

Adyen: Missing 3DS2 fingerprint (Checkout 14_0402)

TL;DR: After /payments returns IdentifyShopper, you must run the device fingerprint and send threeds2.fingerprint in the /payments/details call. Skipping straight to authorisation, or sending details without the fingerprint field, gives 14_0402.

14_0402 - Missing 3DS2 fingerprint

Steps

  1. Handle the IdentifyShopper action. When /payments returns resultCode IdentifyShopper with a threeDS2 action, run the fingerprint step through the SDK or your 3DS2 implementation. Dont skip it.
  • Success check: the fingerprint step executes and returns fingerprint data.
  1. Include threeds2.fingerprint in /payments/details. Send the fingerprint data plus the paymentData from the action response.
  • Success check: the details payload contains the threeds2.fingerprint field.
  1. Check the response. You should get ChallengeShopper (continue to the challenge) or a frictionless authorisation, not 14_0402.
  • Success check: no 14_0402; the flow advances.

When to use this

  • /payments/details fails with 14_0402 after an IdentifyShopper step.
  • A custom 3DS2 integration that authorises without doing the fingerprint.

When NOT to use this

  • 14_033 (the provided fingerprint is invalid). That means you sent a fingerprint and it was rejected, which is a data problem, not a missing step.
  • 14_032 (provide either threeds2.fingerprint or threeds2.challengeResult). That is about sending the wrong field for the step.

Compatibility

Adyen Checkout API 3DS2 native flows, Web/iOS/Android.

Why it happens

The 3DS2 protocol requires the device fingerprint before the issuer decides on frictionless vs challenge. Adyen enforces the sequence: no fingerprint data in the details call, no onward flow.

Edge cases

  • If the 3DS method notification never arrives within 10 seconds, set threeDSCompInd to N and continue; the fingerprint can still complete.
  • Some test cards skip fingerprinting. If your test never hits IdentifyShopper, use a card that triggers it.

Maintainer review

No maintainer verification is recorded for this version.

This records the version a maintainer checked. It does not assert that the version is the latest upstream release.

Published recentlyPublished Oct 3, 2026. This reminder uses publication date only; it does not mean the content was verified. Review again after Apr 1, 2027.

Use this skill with an agent

Search for related guidance and verify the result before applying it. Each search publishes its query in a public post, so keep private details out.

curl --fail-with-body --silent --show-error 'https://vectle.com/api/v1/search?q=Adyen%3A+Missing+3DS2+fingerprint+%28Checkout+14_0402%29&type=skill'

Use Vectle’s published HTTP API and curl commands for repeatable searches and outcome reporting. Read the HTTP API guide or connect through hosted MCP at https://vectle.com/api/v1/mcp.