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.

GatewayTest cardExpiryCVV
Stripe4242 4242 4242 4242VisaAny future date, e.g. 12/34Any 3 digits (4 for Amex)
PayPal4005 5192 0000 0004VisaAny future date3 digits (4 for Amex)
Adyen4111 1111 1111 1111Visa03/2030737
Braintree4111 1111 1111 1111VisaAny future dateAny valid CVV
Square4111 1111 1111 1111VisaAny future month and year111 (1111 for Amex)
Razorpay4100 2800 0000 1007VisaAny future dateAny random CVV
Authorize.Net4111 1111 1111 1111VisaAny date after todayAny 3 digits (4 for Amex)
NMI4111 1111 1111 1111Visa10/29CVV 999 returns a match
Cybersource4111 1111 1111 1111VisaAny future dateAny 3 digits (4 for Amex)
Worldpay4000 0000 0000 2701VisaNot specified by WorldpayNot specified by Worldpay
Checkout.com4242 4242 4242 4242VisaAny future dateAny 3 digits (4 for Amex)
Shopify4242 4242 4242 4242VisaAny future dateAny 3 digits (4 for Amex)
Apple Pay4622 9431 2318 9285VisaVaries by card, e.g. 01/30Varies by card, e.g. 111
Mollie2223 0000 1047 9399MastercardAnyAny
Paystack4084 0840 8408 4081VisaAny future dateVaries by card (408 for 4084 0840 8408 4081)
Mercado Pago5480 8328 0103 3311Mastercard11/30123 (1234 for Amex)

Stripe

38 cards

Official Stripe test card numbers for every card brand, every decline code, and 3D Secure authentication flows.

View test cards

PayPal

11 cards

PayPal sandbox test card numbers, plus the cardholder-name triggers that simulate refusals, fraud and insufficient funds.

View test cards

Adyen

8 cards

Official Adyen test card numbers for every major scheme, with the expiry and CVC values Adyen expects.

View test cards

Braintree

23 cards

Braintree sandbox test card numbers for successful and declined transactions, plus the amount thresholds that force processor errors.

View test cards

Square

9 cards

Square sandbox test card numbers, plus the CVV, postal code and expiry values that trigger each specific error state.

View test cards

Razorpay

14 cards

Razorpay test card numbers for domestic and international payments, subscriptions and EMI, with the OTP rule that controls success or failure.

View test cards

Authorize.Net

10 cards

Official Authorize.Net sandbox test card numbers, with the ZIP code, AVS and CVV values that trigger declines and address responses.

View test cards

NMI

17 cards

Official NMI (Network Merchants) sandbox test card numbers, plus 3-D Secure cards for frictionless, challenge and bypassed flows.

View test cards

Cybersource

10 cards

Official Cybersource sandbox test card numbers, with the invalid-data cards and amounts that force declines and request errors.

View test cards

Worldpay

7 cards

Official Access Worldpay test card numbers, with the cardholder-name values that trigger authorised, refused and error results.

View test cards

Checkout.com

20 cards

Official Checkout.com sandbox test card numbers for approvals, declines, response codes and 3-D Secure outcomes.

View test cards

Shopify

21 cards

Test Shopify checkouts with the Bogus Gateway and Shopify Payments test-mode cards, including success, decline and error scenarios.

View test cards

Apple Pay

15 cards

Apple Pay sandbox test cards for apps and the web, covering Visa, Mastercard, Amex, Discover, JCB and China UnionPay.

View test cards

Mollie

3 cards

Mollie test-mode card numbers for Checkout and Components, plus the EUR amounts that trigger each failure reason.

View test cards

Paystack

10 cards

Paystack test card numbers for no-validation, PIN, OTP and bank-authentication flows, plus decline and refund-failure cards.

View test cards

Mercado Pago

4 cards

Mercado Pago Brazil test cards and the cardholder-name codes that simulate approved, pending and rejected payments.

View test cards

Gateway 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.