How to use Test cards
- 1. Pick a gateway. India: Razorpay, Cashfree, PayU, Instamojo. Global: Stripe, PayPal, Braintree, Adyen, and more.
- 2. Filter by scenario. Success, decline, 3D Secure, insufficient funds, expired, or wrong CVC.
- 3. Copy PAN or full fields. Copy the number alone, all fields as text, or a JSON object for API tests.
- 4. Use test mode only. Match sk_test / Razorpay test keys / PayPal sandbox — never live gateways.
About this tool
Every payment processor publishes test PANs that only work in sandbox or test mode. This page collects the official Stripe, Razorpay, and PayPal numbers in one place — with expiry and CVV rules, 3DS scenario cards, Razorpay UPI test IDs, and a Luhn checker. Charging these on production will fail or worse; they exist so you can ship checkout without touching real money.
Stripe test cards
4242424242424242 is the Visa most developers reach for first. Stripe also documents decline cards (4000000000000002), insufficient-funds cards, 3D Secure cards (4000002760003184), incorrect-CVC cards, and expired-card simulations. Use sk_test_ keys, any future expiry, any three-digit CVC, and billing ZIP 42424 for US-address tests.
Razorpay test cards and UPI
4111111111111111 is the domestic Visa every Indian integration tutorial mentions. Razorpay also lists domestic and international Mastercards, debit cards, and Amex numbers — all with random CVV and future expiry in test mode. For UPI, enter success@razorpay or failure@razorpay at Checkout. Netbanking and wallets redirect to a mock page where you choose success or failure.
PayPal sandbox
PayPal flows often need sandbox buyer and seller accounts, not just a PAN. Public test card numbers supplement those logins. Always use sandbox client credentials from developer.paypal.com.
Luhn and format testing
A valid Luhn checksum does not mean a card is issued or will authorize. Use the built-in Luhn checker and random generators when you need format validation or load-test data — not for live charges. For deeper checksum work, open the Check digit tool.
Test mode checklist
Confirm API keys are test/sandbox prefixed. Confirm the Dashboard toggle says Test mode. Confirm webhooks point at staging. Never log full PANs in production — even test numbers teach bad habits.
Code examples
Stripe Visa (success)
4242424242424242
Expiry: 12/34 CVV: 123 ZIP: 42424Razorpay domestic Visa
4111111111111111
Expiry: any future date CVV: any 3 digitsRazorpay UPI success
success@razorpayStripe PaymentIntent test JSON
{
"number": "4242424242424242",
"exp_month": 12,
"exp_year": 34,
"cvc": "123"
}