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.
Quick reference: the default test card for each gateway
The first successful card each gateway documents, with the expiry and security code it expects.
| Gateway | Test card | Expiry | CVV |
|---|---|---|---|
| Stripe | 4242 4242 4242 4242Visa | Any future date, e.g. 12/34 | Any 3 digits (4 for Amex) |
| PayPal | 4005 5192 0000 0004Visa | Any future date | 3 digits (4 for Amex) |
| Adyen | 4111 1111 1111 1111Visa | 03/2030 | 737 |
| Braintree | 4111 1111 1111 1111Visa | Any future date | Any valid CVV |
| Square | 4111 1111 1111 1111Visa | Any future month and year | 111 (1111 for Amex) |
| Razorpay | 4100 2800 0000 1007Visa | Any future date | Any random CVV |
| Authorize.Net | 4111 1111 1111 1111Visa | Any date after today | Any 3 digits (4 for Amex) |
| NMI | 4111 1111 1111 1111Visa | 10/29 | CVV 999 returns a match |
| Cybersource | 4111 1111 1111 1111Visa | Any future date | Any 3 digits (4 for Amex) |
| Worldpay | 4000 0000 0000 2701Visa | Not specified by Worldpay | Not specified by Worldpay |
| Checkout.com | 4242 4242 4242 4242Visa | Any future date | Any 3 digits (4 for Amex) |
| Shopify | 4242 4242 4242 4242Visa | Any future date | Any 3 digits (4 for Amex) |
| Apple Pay | 4622 9431 2318 9285Visa | Varies by card, e.g. 01/30 | Varies by card, e.g. 111 |
| Mollie | 2223 0000 1047 9399Mastercard | Any | Any |
| Paystack | 4084 0840 8408 4081Visa | Any future date | Varies by card (408 for 4084 0840 8408 4081) |
| Mercado Pago | 5480 8328 0103 3311Mastercard | 11/30 | 123 (1234 for Amex) |
Stripe
38 cardsOfficial Stripe test card numbers for every card brand, 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 cardsAuthorize.Net
10 cardsOfficial Authorize.Net sandbox test card numbers, with the ZIP code, AVS and CVV values that trigger declines and address responses.
View test cardsNMI
17 cardsOfficial NMI (Network Merchants) sandbox test card numbers, plus 3-D Secure cards for frictionless, challenge and bypassed flows.
View test cardsCybersource
10 cardsOfficial Cybersource sandbox test card numbers, with the invalid-data cards and amounts that force declines and request errors.
View test cardsWorldpay
7 cardsOfficial Access Worldpay test card numbers, with the cardholder-name values that trigger authorised, refused and error results.
View test cardsCheckout.com
20 cardsOfficial Checkout.com sandbox test card numbers for approvals, declines, response codes and 3-D Secure outcomes.
View test cardsShopify
21 cardsTest Shopify checkouts with the Bogus Gateway and Shopify Payments test-mode cards, including success, decline and error scenarios.
View test cardsApple Pay
15 cardsApple Pay sandbox test cards for apps and the web, covering Visa, Mastercard, Amex, Discover, JCB and China UnionPay.
View test cardsMollie
3 cardsMollie test-mode card numbers for Checkout and Components, plus the EUR amounts that trigger each failure reason.
View test cardsPaystack
10 cardsPaystack test card numbers for no-validation, PIN, OTP and bank-authentication flows, plus decline and refund-failure cards.
View test cardsMercado Pago
4 cardsMercado Pago Brazil test cards and the cardholder-name codes that simulate approved, pending and rejected payments.
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.