3-D Secure
3-D Secure Testing
3-D Secure
3-D Secure Testing
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
skip3DS 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 PAN | Scheme |
|---|---|
340000000000009 | amex |
5500000000000004 | mastercard |
4111111111111111 | visa |
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
| Amount | 3DS Flow | 3DS Result |
|---|---|---|
20000 | challenge | Successful or Declined - status ‘Y’ (ECI 05) or ‘N’ |
20001 | frictionless | Successful - status ‘Y’ (ECI 05) |
20002 | frictionless | Declined - status ‘N’ |
20003 | frictionless | Successful - status ‘A’ (ECI 06) |
20004 | challenge | Successful - status ‘Y’ (ECI 05) |
status in the above table refers to the transaction API response field three_d_secure.response_data.authentication_response
Was this page helpful?