Test cards
Genuine card numbers will produce an error in your test environment. To simulate payments, use any of the test card details provided in the tables below. You can use any valid CVV and any expiry date (mm/yy) as long as it's in the future.
Estimated/final authorization response
| Card number | Response code | Card type |
|---|---|---|
| 10000 | Credit |
| 10000 | Credit |
| 20005 | Credit |
| 20020 | Credit |
| 20068 | Debit |
| 200R1 | Credit |
Incremental authorization
| Card number | Scheme | Response code | Error code | Card type |
|---|---|---|---|---|
| Visa | N/A | incremental_autho rization_unsupported | Credit |
| Visa | N/A | incremental_autho rization_restricted _for_mcc | Credit |
| Visa | 20005 | N/A | Credit |
| Visa | 20068 | N/A | Credit |
Commercial cards
You can use these cards to trigger a fallback to 3DS1. A fallback occurs when the cardholder or issuer is not using 3DS2.
Using these cards in a Sessions direct integration and in combination with the ‘magic amount’ (123321) will trigger a very specific scenario.
A fallback to 3DS1 will be triggered after the merchant initiated a 3DS2 that failed during the first authentication call (e.g. for the reasons of technical issue or a timeout on the side of the ACS).
| Number | Scheme | 3D Secure version supported | Card type |
|---|---|---|---|
| Visa | 3DS1 | Credit |
| Visa | 3DS1 | Prepaid |
| Mastercard | 3DS1 | Debit |
Non-3D Secure enabled cards
To simulate a non-3DS card payment, use one of the following test cards.
| Scheme | Number | CVV | Card type |
|---|---|---|---|
Visa |
|
| Credit |
Mastercard |
|
| Prepaid |
AVS match
Providing any valid value in the source.billing_address.address_line1 will result in an AVS match A (Street Match).
CVV check code
Providing any valid CVV will result in a Y CVV check code.