Testing Credit Card Purchases
Developers can use this documentation to test various credit card scenarios.
Card Purchases
Approvely provides a set of test credit cards that can be used to test a purchase on sandbox. You may use any CVV, address, name, and future expiration date with the below numbers to simulate a successful purchase. To simulate a failed purchase, set the card zipcode to 99999. To simulate a rejected chargeback protection decision, set the card zipcode to 00000.
| Card | Card Number | Zipcode | Status |
|---|---|---|---|
| Visa | 4111 1111 1111 1111 | any | Success |
| Mastercard | 5431 1111 1111 1111 | any | Success |
| Discover | 6011 1111 1111 1117 | any | Success |
| American Express | 3782 822463 10005 | any | Success |
| Visa | 4111 1111 1111 1111 | 99999 | Failed |
| Mastercard | 5431 1111 1111 1111 | 99999 | Failed |
| Discover | 6011 1111 1111 1117 | 99999 | Failed |
| American Express | 3782 822463 10005 | 99999 | Failed |
3DS Enabled Card Purchases
Merchants who have 3DS configured can use the below test cards on sandbox to test different 3DS challenge scenarios.
Note: When testing a friction challenge, you may use any number as the 2FA.
| Card Number | CVV | Expiry Month | Expiry Year | Card | 3DS Challenge Type |
|---|---|---|---|---|---|
| 2303 7799 9900 0275 | 275 | 08 | 26 | Mastercard | Frictionless Challenge |
| 2303 7799 9900 0408 | 408 | 08 | 26 | Mastercard | Friction Challenge |
| 2303 7799 5100 0453 | 453 | 08 | 26 | Mastercard | Friction Challenge Failure |
| 2303 7799 5100 0347 | 347 | 08 | 26 | Mastercard | Rejection |
Testing on Production
When testing in production it is important to adhere to the following guidelines:
- Totals for testing transactions being $2+ per transaction
- Not more than 1 purchase by same card in a 15 minute increment
- Not more than 3 test transactions per card in a day
Failure to follow these guidelines could result in your production account being suspended.
Updated 4 months ago