3-D Secure Testing

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

• Configure 3DS for each of the schemes to test with against the primary card connector. Use any random data for the Acquirer BIN and other fields.
• Ensure Flow rules do not skip 3DS for specific test scenarios

The 3DS provider uses different card numbers to simulate various responses. 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. Using the card simulator to test 3DS independent of your payment service provider’s sandbox is recommended.

Frictionless flow - successful

This returns a frictionless response with a directory response Y.

Test PAN	Scheme	Expiry	Security Code
5200000000001203	mastercard	03/30	100
4111111111101203	visa	03/30	100
340000000022003	amex	03/30	1000
3558111111121203	jcb	03/30	100
8171998927611203	unionpay	03/30	100

Challenge flow - successful or declined - status ‘Y’ (ECI 05) or ‘N’

This returns a directory response with code C, and once the challenge completes, this either returns N or Y authentication response.

Test PAN	Scheme	Expiry	Security Code
5240000000001072	mastercard	03/30	100
4111111111181072	visa	03/30	100
340000000082072	amex	03/30	1000
3558111111121872	jcb	03/30	100
8171998927611872	unionpay	03/30	100