Reporting-2 icon

3DS Authentication report

Analyze 3D Secure authentication performance.

The 3DS Authentication report includes information about transactions for which Adyen attempted 3D Secure authentication or applied a 3D Secure exemption. This report does not include transactions for which 3D Secure authentication did not apply, or transactions for which a different authentication provider attempted authentication.

The 3DS Authentication report will replace the 3D Secure Authentication report. The 3DS Authentication report has updated filtering logic. Because of this, you cannot fully reconcile the numbers between these two reports.

You may have to update your report data ingestion logic if you automatically generate, download, and ingest reports or ingest manually downloaded reports into your system.

Generating and downloading: Get this report manually or automatically.

Time zone: CET time zone.

Date range: Select the date range of data included when you generate the report in your Customer Area.

Availability: Available for company accounts and merchant accounts.

How to use this report

You can use the 3DS Authentication report to analyze authentication performance for transactions where Adyen is the authentication provider. The filtering logic has been updated compared to the previous version of the report, and we have added new columns to provide more context when looking at authentication performance.

The scope of the 3DS Authentication report differs from the 3D Secure Conversion report. The conversion report includes all card transactions that started as an offer, can contain drop-offs, and does not contain all transactions where Adyen attempted 3D Secure or exemptions. The authentication report includes all 3D Secure transactions and exemptions, and should be used to analyze authentication performance.

Structure

Entries

Under the header line, each line in the report is a separate entry. Each entry represents a transaction.

Columns

Each column shows specific information about the entries.

The data type for each column is string, but the data type can change depending on the application you use to read the CSV file.

# Column Data Type Description
1 3DS Version String The 3D Secure version applied for the transaction. For example 2.1.0 or 2.2.0.
2 3DS Version from Request String The requested 3D Secure version as provided in the payment request. The 3D Secure version that is applied can differ from the requested 3D Secure version.
3 3DS2 Redirect String The value will be True if the transaction went through the 3D Secure redirect flow.
4 Acquirer Response String The acquirer's response to the authorization, summarized in three possible categories. Possible values:
  • Approved
  • Declined
  • Unknown
5 ACS Reference Number String The unique Access Control Server (ACS) identifier assigned by EMVCo.
6 ACS URL String The fully qualified URL of the Access Control Server (ACS) to be used for the challenge.
7 Amount String The transaction amount (in the currency listed in the Currency Code column).
For example, 100.00.
8 Amount (EUR) String The transaction amount (in EUR).
For example, 100.00.
9 ARes TransStatus String The transStatus from the Authentication Response (ARes). This column was called directory_response previously.
10 ARes TransStatus Reason String Provides information on the reason for the transStatus from the Authentication Response (ARes). See the 3D Secure 2 API reference for possible values.
11 Authentication Flow String Specifies which 3D Secure flow Adyen and the issuer used for the authentication stage when processing the transaction. For example, Frictionless. This can be be different from the requested authentication flow.

We recommend looking at this column in combination with the Authentication Success column. See the table later on this page for possible values.
12 Authentication Only String The value will be True if the transaction was sent through the Authentication Only flow. This flow requires additional configuration, and the payment request must contain the authenticationOnly parameter.
13 Authentication Success String If Adyen considers the transaction to be successfully authenticated. For example, 1.

We recommend looking at this column in combination with the Authentication Flow column. See the table later on this page for possible values.
14 Authentication Type String Indicates which authentication method the issuer used to challenge the cardholder. This can be static (value 01), dynamic (value 02), or OOB (value 03). Possible values:
  • 01
  • 02
  • 03
15 Bin String The first six digits of the card number, known as the Bank Identification Number (BIN).
16 Card Holder Name String The name of the cardholder.
17 Challenge Cancel String Indicator informing the Access Control Server (ACS) and the Directory Server (DS) that the authentication has been canceled.
18 Challenge Indicator String Indicates if a challenge was requested for this transaction.
19 Challenge Indicator from Request String Indicates if a challenge was requested for this transaction in the payment request.
20 Company Account String The name of your company account as registered in the Adyen payments platform.
21 Creation Date String The timestamp indicating when the payment was created on the Adyen payments platform. The timestamp will be in CET or CEST, depending on the date when the transaction was created. Format: YYYY-MM-DD HH:MM:SS.
For example: 2023-07-26 19:58:55.
22 Currency Code String The three-character ISO currency code for the transaction.
23 Device Channel String The channel that was used to initiate the transaction. Possible values:
  • None (empty/missing)
  • Browser
  • App
24 Directory Server Transaction ID String The universally unique transaction identifier assigned by the Directory Server (DS) to identify a single transaction.
25 ECI String The Electronic Commerce Indicator (ECI), a payment system specific value provided by the Access Control Server (ACS) or Directory Server (DS) to indicate the results of the attempt to authenticate the cardholder.
26 Execute 3DS from Request String The value of the executeThreeD parameter sent in the payment request, if present.
27 Issuer Country String The ISO country code of the issuer.
28 Issuer Name String The name of the issuer.
29 Merchant Account String The name of the merchant account that was used to process the original payment request.
30 Merchant Reference String The transaction reference that was specified in the payment request.
31 Merchant Requested String The value will be True when you have requested 3D Secure through the payment request (see the column Execute 3DS from Request) or Dynamic 3D Secure rules.
32 Metadata String Additional information included in the payment request, in the form of key value pairs.
33 Original Event Date String The date the transaction was created on the Adyen payments platform.
34 Payment Method String The payment method used for the transaction.
35 PSD2 Scope String The value will be True if the transaction is in scope of the PSD2 regulations, which means that 3D Secure is mandatory.
36 Psp Reference String Adyen's 16-character unique reference associated with the transaction/the request. This value is globally unique; quote it when communicating with us about this request.
37 Raw Acquirer Response String The raw acquirer response to authorization.
38 Recurring Processing Model String The type of recurring payment used in the payment request.
39 Requested Authentication Flow String Adyen's preferred authentication flow for the transaction, for example Frictionless. This can be be different from the authentication flow enforced by the issuer, for example Challenged.

See the table later on this page for possible values.
40 Risk Scoring (pre Authorisation) String The risk score of the transaction before authorization.
41 RReq TransStatus String The transStatus from the Results Request (RReq). This column was called authentication_response previously.
42 RReq TransStatus Reason String Provides information on the reason for the transStatus from the Results Request (RReq). See the 3D Secure 2 API reference for possible values.
43 SCA Exemption String The strong customer authentication (SCA) exemption that Adyen requested for the transaction.
44 SCA Exemption from Request String The strong customer authentication (SCA) exemption that was requested in the payment request.
45 SCA Retry String The value will be True if the transaction was retried automatically by Adyen using 3D Secure, because the initial authorization was soft-declined.
46 Shopper Country String The ISO country code of the shopper, if available.
47 Shopper Email String The shopper's email address.
48 Shopper Interaction String The shopper's interaction type. Possible values:
  • ContAuth
  • Ecommerce
49 Shopper IP String The shopper's IP address.
50 Shopper Reference String The shopper ID or reference that was specified in the original transaction.

Authentication flows and success

The possible values for the columns Authentication Flow, Requested Authentication Flow, and Authentication Success correspond with the authentication scenario for the payment. The table lists the mapping of possible values and a description of the scenario.

Possible values

Authentication Flow / Requested Authentication Flow column
Description Possible values

Authentication Success column
No 3DS (exemption) One of the following PSD2 SCA exemptions is applied: lowValue, transactionRiskAnalysis or secureCorporate. None
Challenged The issuer or Access Control Server (ACS) challenges the shopper. 0 or 1
Frictionless No challenge required, shopper does not have to perform SCA. 1
Data only Data is sent to the scheme instead of the issuer to handle the decision making. The scheme then forwards the data with their decision to the issuer, who handles the authentication request. The shopper does not have to perform SCA. 1
TRA in AReq The PSD2 SCA exemption transactionRiskAnalysis was applied in the Authentication Request (AReq). 1
Rejected The issuer rejected the authentication attempt, authorization was not attempted. 0
Attempted Authentication was attempted, and the issuer covers liability. 1
Declined The issuer declined the authentication attempt. 0
3DS1 The authentication attempt runs over the 3D Secure 1 rails. 0 or 1
Error The transStatus from the Authentication Response (ARes) indicates an error. 0
Unknown The transaction cannot be categorized as any of the authentication flows. 0

See also