Search

Are you looking for test card numbers?

Would you like to contact support?

Default icon

ThreeDSecureData

You can submit a request to authorise payments using authenticated data from another 3D Secure provider. Get the authentication data from a 3D Secure 1 MPI (Mastercard SecureCode or Verified By Visa) or a 3D Secure 2 provider and pass the values in the mpiData object.

If you are authorising a payment for a co-branded card, you also need to specify the scheme to make sure that we process the request with the same scheme that authenticated the transaction. You can do this in the selectedBrand parameter if you are using /authorise or in paymentMethod.type if you are using /payments.

See the integration pages for the endpoint you are using for more details:

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, this is the transStatus from the last CRes (Challenge Response) message or in the RReq (Results Request) sent after the shopper completes the challenge. If the transaction was frictionless, set this to Y.
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 1, this is the enrollment response from the VERes message from the directory server.
In 3D Secure 2, this is the transStatus from the ARes (Authentication Response). The possible values are A or Y for a frictionless flow, or C for a challenge flow.
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.