Payment Gateway Test Cards
The official sandbox card numbers published by each payment gateway — including the ones that deliberately fail. Generated cards pass a Luhn check but no gateway will approve them; these are the numbers that actually work against a sandbox.
Stripe
20 cardsOfficial Stripe test card numbers for successful payments, every decline code, and 3D Secure authentication flows.
View test cardsPayPal
11 cardsPayPal sandbox test card numbers, plus the cardholder-name triggers that simulate refusals, fraud and insufficient funds.
View test cardsAdyen
8 cardsOfficial Adyen test card numbers for every major scheme, with the expiry and CVC values Adyen expects.
View test cardsBraintree
23 cardsBraintree sandbox test card numbers for successful and declined transactions, plus the amount thresholds that force processor errors.
View test cardsSquare
9 cardsSquare sandbox test card numbers, plus the CVV, postal code and expiry values that trigger each specific error state.
View test cardsRazorpay
14 cardsRazorpay test card numbers for domestic and international payments, subscriptions and EMI, with the OTP rule that controls success or failure.
View test cardsGateway test cards vs generated cards
They solve different problems, and using the wrong one wastes an afternoon.
A generated card number is structurally valid: it has a real BIN prefix, the right length for its scheme, and a correct Luhn check digit. That makes it ideal for testing your own form validation, your database schema, or a UI that formats and masks card input. No payment processor will authorise it, because it does not correspond to an account anywhere.
A gateway test card is a number the gateway itself recognises in its sandbox and maps to a scripted outcome. That is what you need once you are testing the integration rather than the form — and crucially it is the only way to exercise the failure paths. Roughly half of a payment integration is what happens when the charge is declined, the card is expired, the CVC is wrong, or 3D Secure demands a challenge.
Every number listed here comes from the gateway's own documentation, and each page links back to the source so you can confirm it has not changed.