Before testing 3DS in sandbox there is some configuration required:

  • Configure 3DS for each of the schemes that you want test with against your primary card connector
  • Ensure Flow rules do not skip 3DS for your specific test scenarios

Our 3DS server uses different card numbers and/or amounts to simulate various responses. You can use the following test cards.

Enrolled PANs

Test PANScheme

Each connector handles sandbox testing and test PANs differently, so it may or may not be possible to use these PANs to test end-to-end in sandbox. Please reach out should you have any questions about testing different 3DS scenarios end-to-end.

Simulate responses with amounts

Amount3DS Flow3DS Result
20000challengeSuccessful or Declined - status ‘Y’ (ECI 05) or ‘N’
20001frictionlessSuccessful - status ‘Y’ (ECI 05)
20002frictionlessDeclined - status ‘N’
20003frictionlessSuccessful - status ‘A’ (ECI 06)
20004challengeSuccessful - status ‘Y’ (ECI 05)

status in the above table refers to the transaction API response field three_d_secure.response_data.authentication_response