Test Cases — Cards
Test cards for every outcome: approved, declined, 3DS and insufficient funds.
Use these cards to simulate payment scenarios in the Stage environment before going live. They work
exclusively in https://stage.tonder.io — they will not work in production.
For a better experience, we recommend getting in touch with your Tonder representative to obtain test cards specific to your integration and region.
Test cards
| Card number | Expected result |
|---|---|
4000 0000 0000 0077 | Successful payment |
5451 9515 7492 5480 | Card declined |
4456 5280 8038 9860 | 3DS authentication required |
4456 5400 0000 0063 | Non-3DS flow |
4574 4412 1519 0335 | Processing error (does not generate a log in Tonder) |
4349 0012 1084 6432 | Insufficient funds |
The CVV should be 3 digits and the expiration date can be any future date in MM/YY format.
Certification scenarios
All scenarios must be tested end-to-end, receiving and validating the webhook for each one.
| Scenario | Card | CVV | Expiry | Amount | Expected result |
|---|---|---|---|---|---|
| ✅ Success | 4000 0000 0000 0077 | 123 | 11/26 | 94.00 | Status Success · payment_id present |
| 💳 Refund | 4000 0000 0000 0077 | 123 | 11/26 | 94.00 | Status Success → then initiate refund |
| ❌ Decline | 5451 9515 7492 5480 | 123 | 11/26 | 95.00 | Status Declined |
| 💸 Insufficient funds | 4349 0012 1084 6432 | 123 | 11/26 | 96.00 | Declined — insufficient funds |
| 🔒 3DS | 4456 5280 8038 9860 | 123 | 11/26 | 97.00 | 3DS redirect → Status Success |
Additional validations: receive the webhook with the final status for each scenario, validate
that payment_id and order_id are present, and confirm webhook deduplication works.