Skip to content

Track 3DS authentication events

Last updated: 9th August 2022

Use the Dashboard to keep track of 3D Secure (3DS) authentication events for greater visibility over your payment's history.

View these events in three areas on the Dashboard:


Payments list

Use the Status column to understand which stage of the authentication process each payment is in.

  • Authentication requested: Authentication sessions are asynchronous, so this status appears while the process is still ongoing
  • Authenticated: When a payment request has been successfully authenticated using 3DS
  • Authentication failed: When a payment request has failed 3DS authentication

Authenticated payments have an additional label next to the status either 3DS1 or 3DS2. This label will remain throughout the payment lifecycle to allow you to identify those successfully authenticated at a glance.


Payment timeline

All 3DS events that your payment triggers will appear in the timeline, so you can view the session in its entirety.


3DS authentication section

In the 3DS authentication section of the Payment details screen, we present specific information about that authentication session. The status tables provide examples of codes you may see.

The protocol version present reflects the version used to authenticate that transaction.


Example authentication codes

Transaction status

The values will be dependent on the protocol version of the transaction.

Value on screenDescription

Y

Authentication verification successful.

N

Not authenticated or account not verified. This means the transaction was denied.

U

Authentication or account verification could not be performed. This is due to a technical problem, or another problem as indicated in ARes or RReq.

A

Attempt at processing performed. Not authenticated or verified, but a proof of attempted authentication/verification is provided.

C

Challenge required. Additional authentication is required using the CReq or CRes.

D

Challenge required. Decoupled authentication confirmed.

R

Authentication or account verification rejected. Issuer is rejecting and requests that authorization not be attempted.

I

Informational only. 3DS requestor challenge preference acknowledged.

Transaction status reason

Value on screenDescription

01

Card authentication failed.

02

Unknown device.

03

Unsupported device.

04

Exceeds authentication frequency limit.

05

Expired card.

06

Invalid card number.

08

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 did not have sufficient time to authenticate cardholder. ACS will not make attempt.

26

Authentication attempted but not performed by the cardholder.

27 - 79

Reserved for EMVCo future use (values invalid until defined by EMVCo)

80 - 89

Reserved for DS use.

Authentication type

Value on screenDescription

01

Payment transaction.

02

Recurring transaction.

03

Installment transaction.

04

Add card.

05

Maintain card.

06

Cardholder verification as part of EMV token ID&V.

07-79

Reserved for EMVCo future use (values invalid until defined by EMVCo).

80-99

Reserved for DS use.

ACS information indicator

ValueVISAMASTERCARD

80

TRA supported by issuer.

Card range is enrolled is Smart Authentication Stand-In Service. (Automatically added to card ranges that are not enrolled in IDC.)

81

Data-only supported by issuer.

Card range is enrolled in Smart Authentication Direct. Populated when issuer enrolls a card range in SA-Direct using ISSM.

82

Delegated authentication supported by issuer.

N/A

84

N/A

Card range supports payment transactions. Populated when issuer enrolls a card range in ISSM.

85

N/A

Card range supports non-payment transactions. Populated when issuer enrolls a card range in ISSM.

86

N/A

Card range supports the app channel. Populated when issuer enrolls a card range in ISSM.

87

N/A

Card range supports the browser channel. Populated when issuer enrolls a card range in ISSM.

88

N/A

Card Range supports app-based ACS or Issuer Challenge Capabilities. Populated when issuer enrolls a card range in ISSM.

89

N/A

Card range supports browser-based ACS or Issuer Challenge Capabilities. Populated when issuer enrolls a card range in ISSM.

90

N/A

Card range is enrolled in Identity Check Express. Populated when issuer enrolls a card range in Identity Check Express using ISSM.

91

N/A

Card range supports Authentication Express Merchant Delegation for Identity Check Express (Type I). Populated when issuer enrolls card range to Identity Check Express Type I using ISSM. Model open to all merchants using a FIDO-compliant device authentication solution. SCA validation of authentication results is done by Mastercard.

92

N/A

Card range supports Authentication Express Low Fraud Merchant (Type II). Populated when issuer enrolls a card range to low fraud SCA delegation using ISSM. Model open to low-fraud merchants (<13 bps) using any PSD2-compliant authentication solution. SCA validation of authentication results is done by Merchant.

93

N/A

Card range participates in Authentication Express Wallet Delegation. Populated when issuer enrolls Wallet delegation for card range in the Authentication express SCA delegation using ISSM.

94

N/A

Card range participates in Authentication Express Device Delegation. Populated when issuer enrolls device delegation for card range in authentication express SCA delegation using ISSM.