Learn how you can authorise a payment with Adyen, using data from a third-party 3D Secure 2 provider.
Before you begin
Before you can start accepting 3D Secure 2 authenticated transactions on browsers or in-app, make sure that you:
- Sign up for an Adyen test account at https://www.adyen.com/signup.
- Get your API Key. Save a copy as you'll need it for API calls you make to the Adyen payments platform.
Get authentication data
Get the following data from your 3D Secure 2 provider. You will need these values when submitting a payment authorisation request with Adyen.
transStatusfrom the Authentication Response (
ARes) sent by the issuer. The
AResindicates if the cardholder has been authenticated or if the issuer requires further interaction to complete the authentication.
transStatusfrom the Results Request (
RReq) sent by the ACS to the 3DS Server after a challenge flow is completed. The
RReqindicates the result of the authentication.
messageVersion: The value should be 2.1.0.
Send a payment authorisation request with 3D Secure 2 authentication data
Make a POST
/authorise request and include
mpiData: Object that contains the authenticated data.
directoryResponse: This is the
transStatusfrom 3D Secure device fingerprinting.
authenticationResponse: This is the
transStatusfrom challenge flow. If the transaction was frictionless, set this value to Y.
cavv: This is the
threeDSVersion: The value should be 2.1.0.
additionalData: Object that contains the acquirer information.
acquirerCode: This is the name of the Adyen acquirer that you want to authorise the transaction with.
authorisationMID: This is the MID of the Adyen acquirer account that you want to authorise the transaction with.
Sample request with mpiData
resultCodeif the payment authorisation was successful. Otherwise, see Result codes f or a complete list of values and the actions that you need to take.