Version 2 Challenge

3DS 2.2.0 Challenge Testing Scenarios

Device Channel: Browser

Scenario #DescriptionMessage CategorytransStatusCard Number
28Payment Authentication request that results in a fully authenticated challenged authenticationPAY2303779951000446
29Non-Payment Authentication request that results in a fully authenticated challenged authentication.NPAY2303779951000297
30Payment Authentication request that results in a not-authenticated challenged authenticationPAN2303779951000453
31Payment Authentication request that results in a not-authenticated challenged authenticationPAU2303779951000420
32Non-Payment Authentication request that results in a Not Authenticated challenged authentication.NPAU2303779951000289
35Whitelisting. Non-Payment Authentication request that results in a fully authenticated challenged authentication with a successful whitelist response.NPAY2303779951000305

Device Channel: 3RI

🚧

PLEASE NOTE

A challenge will not be mandated for a 3RI 3DS request unless explicitly requested via the optional DecoupledAuthenticationDetails object in the authentication request.

The below scenarios are only valid when the desired transStatus is obtained by calling the ChallengeResults method. The Authentication response will indicate a challenge when Decoupled Authentication is requested via the Authentication request by providing the optional DecoupledAuthenticationDetails object and setting the value of the DecoupledAuthenticationDetails.DecoupledIndicator to true.

Scenario #DescriptionMessage CategorytransStatusCard Number
59Payment Authentication request that results in a fully authenticated decoupled authenticationPAY2303779951000537
61Payment Authentication request that results in a not-authenticated decoupled authenticationPAN2303779951000511
60Non-Payment Authentication request that results in a fully authenticated decoupled authenticationNPAY2303779951000495
62Non-Payment Authentication request that results in a not-authenticated decoupled authenticationNPAN2303779951000479