The 3D Secure Authentication report includes information about 3D Secure authentication attempts.
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.
Structure
Entries
Under the header line, each line in the report is a separate entry.
Columns
Each column shows specific information about the entries.
| # | Column | Data Type | Description | ||
|---|---|---|---|---|---|
| 1 | company | Unicode Text (80-character) | Your company name. | ||
| 2 | merchant | Unicode Text (80-character) | Your merchant name. | ||
| 3 | acquirer | Unicode Text (80-character) | The acquiring license used. | ||
| 4 | payment_method | Unicode Text (30-character) | The payment method. | ||
| 5 | directory_server | Unicode Text (30-character) | The scheme used for performing the authentication. | ||
| 6 | pspreference | Unicode Text (16-character) | The payment service provider (PSP) reference to the transaction. | ||
| 7 | merchant_reference | Unicode Text (80-character) | Your reference to the transaction. | ||
| 8 | shopper_reference | Unicode Text (80-character) | Your unique shopper ID. | ||
| 9 | currency | Alpha Text (3-character) | The type of currency. | ||
| 10 | amount | Fixed point number | The transaction amount. | ||
| 11 | bin | Integer | The Bank Identification Number (the first 6 to 8 digits of the card number) | ||
| 12 | issuer_name | Unicode Text (256-character) | The issuer name. | ||
| 13 | issuer_country_code | Alpha Text (2-character) | The issuer country (ISO code). | ||
| 14 | creation_date | Date field + Time field | The date of creation of the transaction. | ||
| 15 | time_zone | Alpha Text (4-character) | The time zone of the transaction (ISO code). | ||
| 16 | risk_score | Integer | The pre-authorisation fraud score. | ||
| 17 | shopper_interaction | Alpha Text (30-character) | The type of shopper interaction. | ||
| 18 | recurring_processing_model | Unicode Text (80-character) | The type of recurring processing model. | ||
| 19 | device_channel | Alphanumeric (2-character) | The device channel that the transaction was created with. For example, 01 is in-app and 02 is browser. | ||
| 20 | message_category | Alphanumeric (2-character) | The category of the 3D Secure message. For example, 01 is PA (payment). | ||
| 21 | threeDS_version | Unicode Text (80-character) | Version of 3D Secure used. For example, 1.0.2, 2.1.0, or 2.2.0. | ||
| 22 | authentication_only | Boolean | If the transaction was sent with the authentication-only flag. | ||
| 23 | sca_retry | Boolean | If the transaction was retried automatically by Adyen because the initial authorisation was soft-declined. | ||
| 24 | sca_exemption_requested | Unicode Text (30-character) | Any SCA exemption Adyen requested. For example, TRA or low value . | ||
| 25 | data_only | Boolean | If the transaction went through data-only flow. | ||
| 26 | threeDS2_redirect | Boolean | For 3D Secure 2: the transaction went through the redirect flow. | ||
| 27 | threed_directory_response | Alpha Text (1-character) | For 3D Secure Redirect: the
threeDOfferedResponse
. For 3D Secure 2: the transStatus in the
threeDS2Result
when the transaction goes through the frictionless flow. |
||
| 28 | threed_authentication_response | Alpha Text (1-character) | For 3D Secure Redirect: the
threeDAuthenticatedResponse
. For 3D Secure 2: the transStatus in the
threeDS2Result
when the transaction goes through the challenge flow. |
||
| 29 | trans_status_reason | Alphanumeric (2-character) | For 3D Secure 2: The
transStatusReason
. |
||
| 30 | eci | Alphanumeric (2-character) | The electronic commerce indicator. | ||
| 31 | threeds_server_transaction_id | Unicode Text (36-character) | For 3D Secure 2: The
threeDSServerTransID
transaction identifier assigned by the 3DS Server. |
||
| 32 | threeds_completion_indicator | Alpha Text (1-character) | For 3D Secure 2: The
threeDSCompInd
|
||
| 33 | threeds_requestor_name | Unicode Text (40-character) | For 3D Secure 2: The
threeDSRequestorName
|
||
| 34 | threeds_requestor_challenge_indicator | Alphanumeric (2-character) | For 3D Secure 2: The
challengeIndicator
|
||
| 35 | dstransid | Unicode Text (36-character) | The unique transaction identifier assigned by the DS. | ||
| 36 | acs_reference_number | Unicode Text (32-character) | For 3D Secure 2: The unique ACS identifier assigned by EMVCo. | ||
| 37 | acs_trans_id | Unicode Text (36-character) | For 3D Secure 2: The unique transaction identifier assigned by the ACS. | ||
| 38 | acs_url | Unicode Text (2048-character) | For 3D Secure 2: URL of the ACS to be used for the challenge. | ||
| 39 | acs_challenge_mandated | Alpha Text (1-character) | For 3D Secure 2: Indicates whether a challenge is mandated for authorisation. | ||
| 40 | acs_operator_id | Unicode Text (32-character) | For 3D Secure 2: The unique ACS identifier assigned by the DS. | ||
| 41 | ares_authentication_type | Alphanumeric (2-character) | The type of authentication method the issuer used to challenge the cardholder. Returned in the ARes. |
||
| 42 | card_holder_info | Unicode Text (128-character) | For 3D Secure 2: Text provided by the ACS/Issuer to Cardholder during a frictionless or decoupled transaction. | ||
| 43 | acquirer_response | Unicode Text (30-character) | The acquirer response to authorisation. | ||
| 44 | raw_acquirer_response | Unicode Text (300-character) | The raw acquirer response to authorisation. | ||
| 45 | cvc_supplied | Boolean | If the CVC was supplied. | ||
| 46 | cvc_response_code | Unicode Text (80-character) | The CVC response code. | ||
| 47 | avs_response | Unicode Text (80-character) | The address verification system response. | ||
| 48 | challenge_cancel | Alphanumeric (2-character) | For 3D Secure 2: Indicates that the challenge is canceled. For example, 01 means cardholder cancelled. | ||
| 49 | interaction_counter | Integer | For 3D Secure 2: The number of authentication cycles attempted. | ||
| 50 | rreq_authentication_type | Alphanumeric (2-character) | For 3D Secure 2: The type of authentication method used by the ACS in the RReq. |
||
| 51 | results_status | Alphanumeric (2-character) | For 3D Secure 2: The status of the RReq. For example, 01 is received for further processing. |
||
| 52 | liability_shift | Boolean | If the transaction benefits from a protection against fraudulent chargeback. | ||
| 53 | shopper_name | Unicode Text (80-character) | The shopper's name. | ||
| 54 | shopper_ip | Unicode Text (50-character) | The shopper's IP address. | ||
| 55 | shopper_country | Alpha Text (2-character) | The shopper's country (ISO code). | ||
| 56 | shopper_email | Unicode Text (256-character) | The shopper's email address. | ||
| 57 | authentication_mid | Unicode Text (35-character) | For 3D Secure 2: The MID used in the AReq. | ||
| 58 | authorisation_mid | Unicode Text (50-character) | The MID used in the authorisation. | ||
| 59 | error_code | Alphanumeric (3-character) | For 3D Secure 2: Indicates the type of problem identified in the message. | ||
| 60 | error_component | Alpha Text (1-character) | For 3D Secure 2: Indicates the 3D Secure component that identified the error. | ||
| 61 | error_description | Unicode Text (2048-character) | For 3D Secure 2: Describes the problem identified in the message. | ||
| 62 | error_detail | Unicode Text (2048-character) | For 3D Secure 2: Additional information regarding the error. | ||
| 63 | error_message_type | Alpha Text (4-character) | For 3D Secure 2: Identifies the message type that was erroneous. | ||
| 64 | threeds2_fallback | Boolean | If a fallback from 3DS2 to 3DS1 took place. | ||
| 65 | threeds2_fallback_directory_response | Alpha Text (1-character) | The 3DS2 directory response corresponding to the fallback. This is initial (failed) 3DS2 attempt. |