Skip to main content
Before testing 3DS in sandbox there is some configuration required:
  • Configure 3DS for each of the schemes that you want to test with against your primary card connector. You can use any random data for the Acquirer BIN and other fields.
  • Ensure Flow rules do not skip 3DS for your specific test scenarios
Our 3DS provider uses different card numbers to simulate various responses. You can use the following test cards.
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. We recommend using the card simulator to test 3DS independent of your payment service provider’s sandbox.

Frictionless flow - Successful

This will return a frictionless response with a directory response Y.
Test PANSchemeExpirySecurity Code
5200000000001203mastercard03/30100
4111111111101203visa03/30100
340000000022003amex03/301000
3558111111121203jcb03/30100
8171998927611203unionpay03/30100

Challenge flow - Successful or Declined - status ‘Y’ (ECI 05) or ‘N’

This will return a directory response with code C, and once the challenge completes this will either return N or Y authentication response.
Test PANSchemeExpirySecurity Code
5240000000001072mastercard03/30100
4111111111181072visa03/30100
340000000082072amex03/301000
3558111111121872jcb03/30100
8171998927611872unionpay03/30100