Authentication-only integration

In a 3D Secure 2 authentication-only flow, you perform the 3D Secure 2 authentication independently of the payment authorisation flow. When performing an authentication-only flow:

1. Submit a payment authentication request.
   The transaction can go through either a frictionless or a challenge authentication flow.
2. Perform the required authentication flow.
3. Get the 3D Secure 2 authenticated data.
4. Use the authenticated data to authorise the payment either with Adyen, or with another PSP or acquirer.

Before you begin

Before you begin to integrate, make sure you have followed the Get started with Adyen guide to:

• Get an overview of the steps needed to accept live payments.
• Create your test account.

After you have created your test account:

1. Get your API Key. Save a copy, because you'll need it for API calls you make to the plataforma de pagamentos da Adyen.
2. Build your own payment form, or use one of our client-side solutions for collecting card details.
3. Read our 3D Secure 2 integration guide.

Ways to trigger 3D Secure Authentication-only flow

There are two different triggers for 3D Secure Authentication-only flow. You can choose one of the options for your integration:

• If you set your Dynamic 3D Secure rule to Always or configure a Dynamic 3D Secure rule to trigger 3D Secure.
• If you set authenticationData.attemptAuthentication to always in your /payments request.

Submit a payment authentication request

Make a /payments request, specifying:

Parameter name	Required	Description
paymentMethod		Object that contains the shopper's card information from your front end or client app. For higher authentication rates, we strongly recommend that you include the shopper's name in the holderName) field.
channel		Specify platform that you are using. Set to web, iOS, or Android.
authenticationData.authenticationOnly		Set to true. Indicates that the transaction went through Authentication-only flow.
authenticationData.threeDSRequestData.nativeThreeDS		Set to preferred. Indicates that your payment page can handle 3D Secure 2 transactions natively.
browserInfo		Object that contains information about the shopper's browser. Full object is required for channel web. For mobile integrations (channel iOS and Android), the userAgent and acceptHeader fields are required to indicate that your integration can handle 3D Secure 2 redirect authentication in case the transaction is routed to redirect flow. If your mobile integration is unable to generate this information, you can send the same data as in the code samples below.
returnUrl		In case of a 3D Secure 2 redirect flow, this is the URL where the shopper will be redirected back to after completing authentication. This URL can have a maximum of 1024 characters.
origin		Required for channel web. The URL of the page where you are loading the 3D Secure 2 Component from. The origin should not include subdirectories and a trailing slash. You can also get this by opening the browser console and calling window.location.origin. The origin can be a maximum of 80 characters.
shopperIP		The shopper's IP address. Required for channel web.
billingAddress		The cardholder's billing address.
shopperEmail		The cardholder's email address.
authenticationData.attemptAuthentication		Set to always. Perform 3D Secure authentication.

For higher authentication rates, we strongly recommend that you also include:

• Acquirer-related data. A mismatch of acquirer data between the authentication and authorisation requests can be a reason for issuing banks to refuse the transaction.
• Additional shopper information. Sending this data increases the likelihood of achieving a frictionless flow.

A sample request for channel: web using raw card data:

If the /payments response includes resultCode: AuthenticationNotRequired, this means that the transaction does not require 3D Secure authentication. You can proceed to authorise the payment with Adyen, or another PSP or acquirer.

If the /payments response includes an action object, proceed to perform the required authentication flow.

Perform the authentication flow

If the /payments response contains an action object, the transaction will need to go through one of the 3D Secure authentication flows. Perform the required authentication flow using one of our client-side solutions.

Whenever you make a /payments/details request to submit the authentication results, also include:

• authenticationData.authenticationOnly: true

Sample /payments/details request to submit the device fingerprint:

You receive a response containing:

• resultCode: If the authentication process has finished, you receive AuthenticationFinished.
• threeDS2Result.transStatus: Indicates the result of the authentication. The value Y means that authentication is successful. If you get another value, see the list of possible values to learn what it means.
• threeDSPaymentData: You need this if you want to continue to authorise the payment.

Get the 3D Secure 2 authenticated data

After a successful authentication, you get 3D Secure 2 authentication data in the threeDS2Result object:

Some issuers do not provide all fields; the Applies to column shows which issuers provide each field.

You can get this authentication data in the response of one of the following endpoints:

• /payments/details
• /getAuthenticationResult
• /retrieve3ds2Result: For Cartes Bancaires, you must use this one.

Optional: Provide additional acquirer-related data

Get the following details from your acquirer. These details are part of the 3D Secure 2 enrollment process between your acquirer and card schemes.

If you are unable to get these details from your acquirer, contact our Support Team.

• acquirerBIN: Supported from API v49 and later. The acquiring BIN enrolled for 3D Secure 2. This string should match the value that you will use in the authorisation.

  If you are building a test integration, you can use the string 123456 in place of an actual acquirerBIN.

• acquirerMerchantID: Supported from API v49 and later. The authorisation MID enrolled for 3D Secure 2. This string should match the value that you will use in the authorisation.

  If you are building a test integration, you can use the string 123456 in place of an actual acquirerMerchantID.

• mcc: Supported from API v49 and later. The four-digit Merchant Category Code registered with the scheme for the same acquirerMerchantID sent in the request.

• merchantName: Supported from API v49 and later. The merchant name that the issuer presents to the shopper if they get a challenge. We recommend using the same value that you will use in the authorisation. Maximum length is 40 characters.

• threeDSRequestorID: Required for Visa and Mastercard. Unique requestor ID assigned by the Directory Server when you enroll for 3D Secure 2.

• threeDSRequestorName: Required for Visa and Mastercard. Unique requestor name assigned by the Directory Server when you enrol for 3D Secure 2.

Submit an authentication request by making a /payments request containing the required 3D Secure 2 fields, the acquirer fields listed previously, and the authenticationData.authenticationOnly parameter.

• authenticationData.authenticationOnly: true

Request with additional acquirer-related information

curl https://checkout-test.adyen.com/v70/payments \
-H 'x-api-key: ADYEN_API_KEY' \
-H 'content-type: application/json' \
-d '{
    "amount":{
        "currency":"EUR",
        "value":1000
    },
    "reference":"YOUR_ORDER_NUMBER",
    "paymentMethod":{
        "type":"scheme",
        "encryptedCardNumber":"adyenjs_0_1_18$MT6ppy0FAMVMLH...",
        "encryptedExpiryMonth":"adyenjs_0_1_18$MT6ppy0FAMVMLH...",
        "encryptedExpiryYear":"adyenjs_0_1_18$MT6ppy0FAMVMLH...",
        "encryptedSecurityCode":"adyenjs_0_1_18$MT6ppy0FAMVMLH..."
    },
    "authenticationData": {
        "authenticationOnly":true,
        "threeDSRequestData": {
            "nativeThreeDS": "preferred"
        }
    },
    "threeDS2RequestData": {
        "acquirerBIN": "YOUR_ACQUIRER_BIN",
        "acquirerMerchantID": "YOUR_ACQUIRER_MERCHANT_ID",
        "mcc": "YOUR_MCC",
        "threeDSRequestorID": "YOUR_3DS_REQUESTOR_ID",
        "threeDSRequestorName": "YOUR_3DS_REQUESTOR_NAME"
    },
    "browserInfo":{
        "userAgent":"Mozilla\/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit\/537.36 (KHTML, like Gecko) Chrome\/70.0.3538.110 Safari\/537.36",
        "acceptHeader":"text\/html,application\/xhtml+xml,application\/xml;q=0.9,image\/webp,image\/apng,*\/*;q=0.8",
        "language":"nl-NL",
        "colorDepth":24,
        "screenHeight":723,
        "screenWidth":1536,
        "timeZoneOffset":0,
        "javaEnabled": true,
        "acceptHeader": "text/html" //Retrieve this from your sever.
    },
    "origin" : "https://your-company.com/",
    "returnUrl" : "https://your-company.com/checkout/",
    "merchantAccount":"YOUR_MERCHANT_ACCOUNT"
}'

Optional: Send a payment authorisation request with 3D Secure authentication data

Make a POST  /payments request and include the required fields for the issuer.

Sample request

Sample response

You will receive an  Authorised resultCode if the payment authorization was successful. See  Result codes for a complete list of possible responses.

Authentication data expiry

Authentication data and cryptograms expire depending on card schemes. This means that you can no longer use the authentication data after it expires.

When authentication isn't required

You get an AuthenticationNotRequired result code in the /payments response when a transaction doesn't require 3D Secure authentication. If you get this code, you can proceed to authorise the payment with Adyen or any other PSP or acquirer.

Check the authenticationNotRequiredReason value to learn why strong customer authentication (SCA) was not required.

The list of possible values includes:

Testing 3D Secure 2

To test how your integration handles different 3D Secure 2 authentication scenarios, you need to use a card number for the specific flow.

When prompted for 3D Secure 2 text challenges, use the following credentials to authenticate:

• For native mobile integrations, use password: 1234
• For web and mobile browser integrations, use password: password

Depending on the authentication option, you can receive the following result codes:

• RedirectShopper: you receive this result code if you are using the Redirect authentication flow.
• IdentifyShopper: you receive this result code if you are using the Native authentication flow.
• ChallengeShopper: you receive this result code after you submit the 3D Secure 2 device fingerprinting result in a Native authentication, unless you specify a frictionless flow.

Depending on your integration, use the following test cards to simulate different authentication flows.

Challenge without fingerprint

To test the web-based flow where the device fingerprinting step is skipped (because the issuer's ACS has not configured a threeDSMethodURL), and you get a ChallengeShopper resultCode immediately after submitting the payment request, use the following card:

Fingerprint without challenge

To test the frictionless flow, in which you perform a fingerprint but no challenge, use the following test card number:

Native authentication

To test authentication scenarios for native mobile (app-based) integrations, use the following test cards:

Technical error

To test simulate an error due to a timeout during the 3D Secure 2 authentication on the issuer side, use the following test card:

Advanced scenarios

We recommend that you build your logic around the resultCode, but you can additionally use the following test cards to test scenarios involving different transStatus values:

See also