Version 2 Challenge
3DS 2.2.0 Challenge Testing Scenarios
Device Channel: Browser
| Scenario # | Description | Message Category | transStatus | Card Number |
|---|---|---|---|---|
| 28 | Payment-Authentication request that results in a fully authenticated challenged authentication | PA | Y | 2303779951000446 |
| 30 | Payment-Authentication request that results in a not-authenticated challenged authentication | PA | N | 2303779951000453 |
| 31 | Payment-Authentication request that results in a not-authenticated challenged authentication | PA | U | 2303779951000420 |
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 # | Description | Message Category | transStatus | Card Number |
|---|---|---|---|---|
| 59 | Payment-Authentication request that results in a fully authenticated decoupled authentication | PA | Y | 2303779951000537 |
| 61 | Payment-Authentication request that results in a not-authenticated decoupled authentication | PA | N | 2303779951000511 |
| 60 | Non-Payment authentication request that results in a fully authenticated decoupled authentication | NPA | Y | 2303779951000495 |
| 62 | Non-Payment authentication request that results in a not-authenticated decoupled authentication | NPA | N | 2303779951000479 |
Updated about 1 month ago