Simulate card payment outcomes in the Sandbox - from successful payments to declines, 3DS challenges, and fingerprint scenarios.
The cards are grouped by whether they trigger a 3D Secure (3DS) challenge, with a separate group for fingerprint (3DS Method) scenarios.
How it works
Test cards are the Sandbox counterpart of real cards. Once your integration points at the Sandbox environment, use them to exercise every card payment scenario your integration handles - from successful payments to declines, 3DS challenges, and fingerprint flows - before you switch to Production.
Test cards only work in the Sandbox environment. This applies to API integrations, plugins in test mode, and payment links alike.
A test payment follows the same flow as a live one:
- Make a card payment in your integration with the test number, using any 3-digit
CVVand any futureexpiry date(MM/YY). - If the card triggers a 3DS step, complete it: 3DS challenge cards ask the customer to complete a challenge, and fingerprint (3DS Method) cards run a silent device check in the background. In the Sandbox environment, the 3DS simulator stands in for the bank's 3DS pages.
- The payment then reaches the outcome the card number determines -
authorised,declined, orfailed. Verify the outcome by retrieving the payment details or with webhooks.
When testing payments with authorisation_type: pre_authorisation, use a test card that results in an authorised payment. Test cards that produce declined or failed outcomes cannot complete a pre-authorised payment.
For more information on testing incremental authorisation in Sandbox, see: Incremental authorisation.
Non-challenge scenarios
The following test cards don't trigger a 3DS challenge: payments with these cards are either authorised or declined without the customer seeing a challenge page.
Successful payments
Use the following test cards to simulate successful payments in the Sandbox environment.
| Card PAN | Brand |
|---|---|
4929420573595709 | VISA |
5281438801804148 | MASTERCARD |
You can also use these cards to test the flow of saving a customer's payment method and charging it later. For more information, see: Charge a customer's saved payment method.
Error cases
Use the following test cards to create payments that produce error codes in the Sandbox environment. This is useful when you want to:
- See how different errors are shown to your customers.
- Implement custom error handling.
| Card PAN | Case | Decline reason | Payment state |
|---|---|---|---|
4929573638125985 | Payment declined due to insufficient funds. | insufficient_funds | declined |
4532336743874205 | Payment declined due to card being expired. | expired_card | declined |
2720998837779594 | Payment declined due to Do Not Honour - the customer's bank declines the transaction due to internal reasons, such as triggered fraud rules or a temporary hold on the card. | do_not_honour | declined |
5555550070163102 | Payment declined during a frictionless 3DS flow, without a challenge. | issuer_decline | declined |
5555550070153103 | Payment rejected by the issuing bank. | issuer_decline | declined |
5555550079153104 | Payment declined because 3DS is unavailable for the card. | issuer_decline | declined |
3DS challenge scenarios
Use the following test cards to simulate payments that require the customer to complete a full 3DS challenge.
| Card PAN | Case | Decline reason | Payment state |
|---|---|---|---|
5555550079553105 | Payment authorised after the customer completes the 3DS challenge. | N/A | authorised |
5215674115127070 | Payment failed because the 3DS challenge failed. | technical_error | failed |
5555550029553106 | Payment failed because the 3DS challenge timed out. | customer_challenge_abandoned | failed |
5555550028553107 | Payment failed because the customer abandoned the 3DS challenge. | technical_error | failed |
5555550928553108 | Payment declined because the 3DS challenge was declined. | issuer_decline | declined |
These cards only reach their final payment state when the customer completes the 3DS challenge. If your tests don't complete the challenge, the payment proceeds to the same final outcome after the challenge times out.
On how to complete the challenge - including how the widget and our plugins render the challenge page automatically - see: 3DS simulator.
Fingerprint (3DS Method) scenarios
Use the following test cards to simulate payments that start with the silent fingerprint (3DS Method) step.
| Card PAN | Case | Payment state |
|---|---|---|
5555550000043101 | Payment authorised after a successful fingerprint step, without a 3DS challenge. | authorised |
5555550079553105 | Payment authorised after a successful fingerprint step and a completed 3DS challenge. | authorised |
For the fingerprint mechanics - including how to simulate a fingerprint timeout - see: 3DS simulator.