3DS 2.x Reference
EMVco 3DS 2.x Definitions
Definitions of the elements in the EMVco 3DS 2.2 specification and the corresponding elements in the NDC 19.2 structure.
Term | Description | Corresponding NDC Element |
---|---|---|
Merchant Name | Merchant name assigned by the Acquirer or Payment System. Length: Variable, maximum 40 characters | SecurePaymentVersion2.AuthenticationMerchantName |
Authentication value | A cryptographic value generated by the ACS to provide a way, during authorization processing, for the authorization system to validate the integrity of the authentication result. The AV algorithm is defined by each Payment System. Base64 is the encoding applied to the Authentication Value data element as defined in RFC 2045 Length: 28 characters | SecurePaymentVersion2.AuthenticationValue |
DS (Directory Server) transaction ID | Universally unique transaction identifier assigned by the Directory Server (DS) to identify a single transaction. Length: 36 characters | SecurePaymentVersion2.DirectoryServerTrxID |
ECI (electronic commerce indicator) | Payment System-specific value provided by the ACS or DS to indicate the results of the attempt to authenticate the Cardholder. Length: 2 characters For more information about about the ECI (ECI - Electronic Commerce Indicator ) | SecurePaymentVersion2.ElectronicCommerceInd |
Transaction Status | Indicates whether a transaction qualifies as an authenticated transaction or account verification. Length: 1 character Possible values are in the table “Transaction Status Values” below | SecurePaymentVersion2.TrxStatusText |
Transaction Status Reason | Provides information on why the Transaction Status field has the specified value Length: 2 characters Possible values are in the table “Transaction Status Reason Values” below | SecurePaymentVersion2.TrxStatusReasonText |
Transaction Status Values
Status | Description | Result |
---|---|---|
Y | Authentication Verification Successful | Transaction successful |
N | Not Authenticated/Account Not Verified | Transaction denied |
U | Authentication/Account Verification Could Not Be Performed | Technical or other problem, as indicated in the ARes or RReq |
A | Attempts Processing Performed | Not Authenticated/Verified, but a proof of attempted authentication/verification is provided |
C | Challenge Required | Additional authentication is required using the CReq/CRes |
D | Challenge Required | Decoupled Authentication confirmed |
R | Authentication/ Account Verification Rejected | Issuer is rejecting authentication/verification and request that authorization not be attempted |
I | Informational Only | 3DS Requestor challenge preference acknowledged |
Transaction Status Reason Values
Status Reason | Description |
---|---|
01 | Card authentication failed |
02 | Unknown Device |
03 | Unsupported Device |
04 | Exceeds authentication frequency limit |
05 | Expired card |
06 | Invalid card number |
07 | Invalid transaction |
08 | No Card record |
09 | Security failure |
10 | Stolen card |
11 | Suspected fraud |
12 | Transaction not permitted to cardholder |
13 | Cardholder not enrolled in service |
14 | Transaction timed out at the ACS |
15 | Low confidence |
16 | Medium confidence |
17 | High confidence |
18 | Very High confidence |
19 | Exceeds ACS maximum challenges |
20 | Non-Payment transaction not supported |
21 | 3RI transaction not supported |
22 | ACS technical issue |
23 | Decoupled Authentication required by ACS but not requested by 3DS Requestor |
24 | 3DS Requestor Decoupled Max Expiry Time exceeded |
25 | Decoupled Authentication was provided insufficient time to authenticate cardholder. ACS will not make attempt |
26 | Authentication attempted but not performed by the cardholder |
UPDATE as of December 17, only people with an Iberia or IAGGBS account will be able to access them. Write to jira.support.ib@iberia.es and we will help you with the change. ACTUALIZACIÓN a partir del 17 de diciembre, sólo podrán acceder a ellas personas con cuenta de Iberia o IAGGBS. Escribe a jira.support.ib@iberia.es y te ayudaremos con el cambio.