No momento, esta página não está disponível em português
Online-payment icon

Third-party authentication

Use authentication data from third-party to authorize payments.

You can use a third-party 3D Secure provider to perform authentication, and use the obtained authentication data when making a payment request to Adyen. This allows you to use a third-party 3D Secure 2 provider to perform authentication while using Adyen to authorize payments.

This page describes passing authentication data in a /payments API request. If you are using the /authorise endpoint, refer to 3D Secure Classic integration.

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 and store it securely in your system. You will need it for API calls you make to the plataforma de pagamentos da Adyen.
  2. Check that you are using v46 or later of the /payments endpoint.

Step 1: Get third-party authentication data

To authorize a 3D Secure 2 authenticated payment, you need the following data:

Some card schemes don't provide all fields; the Applies to column shows which fields are required for which schemes.

Field Applies to
authenticationResponse All schemes
directoryResponse All schemes
authenticationValue All schemes
dsTransID All schemes
eci All schemes
threeDSVersion All schemes
cavvAlgorithm Cartes Bancaires
challengeCancel Cartes Bancaires
challengeIndicator Cartes Bancaires
exemptionIndicator Cartes Bancaires
riskScore Cartes Bancaires

Step 2: Make a payment with third-party authentication data

If you didn't authenticate with Adyen, refer to Mapping Adyen parameters to EMVCo fields. You first need to map the third-party authentication data to Adyen parameters when making a payment request to Adyen.

Make a POST /payments request that includes an mpiData object containing the following:

Some card schemes require different fields. The Applies to column shows which fields are required for which schemes.

Field Applies to
paymentMethod.type All schemes.
Learn more for co-badged cards.
mpiData.authenticationResponse All schemes
mpiData.directoryResponse All schemes
mpiData.cavv All schemes
dsTransID All schemes
mpiData.eci All schemes
mpiData.threeDSVersion All schemes
threeDS2RequestData.challengeIndicator Cartes Bancaires
mpiData.cavvAlgorithm Cartes Bancaires
mpiData.challengeCancel Cartes Bancaires
mpiData.riskScore Cartes Bancaires
additionalData.acquirerCode Cartes Bancaires.
Set to "AdyenCartesBancaires".
additionalData.scaExemption Cartes Bancaires
shopperInteraction All schemes
recurringProcessingModel All schemes

Co-badged cards

If you are making a payment with a co-badged card, you need to set the paymentMethod.type value to the scheme that authenticated the payment. For example, if you are making a payment with a card co-badged with Visa and Cartes Bancaires, set the value to either visa or cartebancaire, depending on which scheme performed the authentication. Otherwise, the payment can be refused.

Sample request

Sample response

You will receive an  Authorised resultCode if the payment authorization was successful. See Result codes for a complete list of values and the actions that you need to take.

See also