Search docs

Are you looking for test card numbers?

Would you like to contact support?

Start searching Adyen's documentation...

  Documentation

ThreeDSecureData

To authorise payments with Adyen using 3D Secure authenticated data, send an /authorise or /payments request with an mpiData object containing the following parameters. Get the values from the authentication data produced by a 3D Secure 1 MPI (Mastercard SecureCode or Verified By Visa) or a 3D Secure 2 provider.

Field Type Required Description
authenticationResponse String -x- In 3D Secure 1, this is the authentication response if a shopper was redirected. In 3D Secure 2, include this parameter if the transaction goes through a challenge authentication flow. This is the transStatus from the last CRes (Challenge Response) message from the ACS to the 3D Secure client or in the RRes (Results Request) from ACS to 3D Secure server sent after the shopper completes the challenge.
cavv String -x- This is the cardholder authentication value (base64 encoded, 20 bytes in a decoded form).
cavvAlgorithm String -x- Include this only for 3D Secure 1. The CAVV algorithm used.
directoryResponse String -x- The enrollment response from the directory server. In 3D Secure 2 specifications, this is the transStatus from the ARes (Authentication Request) message sent by the ACS to the 3D Secure provider.
dsTransID String -x- Supported for 3D Secure 2. The unique transaction identifier assigned by the DS to identify a single transaction.
eci String -x- The electronic commerce indicator.
xid String -x- Supported for 3D Secure 1. The transaction identifier assigned by directory server (base64 encoded, 20 bytes in a decoded form).
threeDSVersion String -x- Include this only for 3D Secure 2. The current supported version is 2.1.0.