Razorpay Test Card: Test Payment Cards for Sandbox

A Razorpay test card is a fake card number that Razorpay publishes for test mode, letting you push a payment through checkout without moving real money. Test cards work only with test API keys, are not tied to any bank account, and every detail you enter stays inside the sandbox.

What makes a card a test card

A test card looks like a normal card on the surface: 16 digits, an expiry date, and a CVV. What separates it from a real one is where it lives and what it can do.

• It is issued by the payment gateway for testing, not by a bank.
• It is accepted only when your integration runs on test keys, which usually start with rzp_test_.
• No settlement, payout, or bank transfer happens. Captured test payments stay in your dashboard as records.
• Validation still behaves like production: number format, expiry checks, CVV length, and the simulated 3D Secure step all run as usual.

Where to find the current Razorpay test card list

Razorpay maintains its own list of test cards in the developer documentation and in the test mode section of the dashboard. That page is the only source you should trust, because card numbers, supported networks, and available payment flows change over time.

Numbers that circulate in blog posts and forum threads are starting points at best. Many are variants of the same handful of publicly documented sandbox numbers, for example a Visa test card such as 4111 1111 1111 1111 or a Mastercard test card such as 5267 3181 8797 5449. With these, the expiry can be any future date and the CVV can be any three digits, or four digits for American Express. Confirm every value against the official page before you build a test suite around it.

How test cards trigger different outcomes

The same card list is used to reproduce both happy paths and failures, which is why it matters for QA.

• Successful payment: use a standard success test card and complete the simulated authentication step.
• Declined payment: some listed cards are designed to return a failure status so you can test retry and error messaging.
• Authentication flows: the test environment shows an OTP screen for cards that require it, and the docs list which OTP values pass or fail.
• Method coverage: separate entries cover domestic cards, international cards, debit cards, and netbanking or wallet flows.

Run a test payment step by step

1. Switch your Razorpay dashboard to test mode and copy the test key ID and secret.
2. Load your checkout with those keys, or open the gateway's own test checkout.
3. Enter a test card number, a future expiry date, any valid CVV, and a name.
4. Complete the simulated authentication screen if it appears.
5. Confirm the payment appears in the test payments list with the expected status.
6. Trigger a refund, webhook, or subscription charge against the same test record to test the rest of your flow.

Why a test card gets rejected

• Your integration is still running on live keys, so the sandbox number is unknown to the gateway.
• The expiry date you typed is in the past, or the CVV length does not match the network.
• The payment method is switched off in your account settings, for example international cards or a specific wallet.
• The card does not match the currency or method combination you selected.
• A field is missing, such as the cardholder name or billing contact.

Handling card data correctly while you test

Sandbox work is a good moment to lock down habits around sensitive data. Never paste a real card number into a test environment, and never store the CVV, even for a real customer, because the PCI DSS rules forbid retaining sensitive authentication data after authorization. Use the gateway's tokenization or saved card tokens when you need repeat payments, and keep your test keys out of public repositories. Test data should always look like test data, with nothing that could be mistaken for a live card.

Quick answers

Do Razorpay test cards work in live mode?

No. They exist only for test mode, and live mode rejects them.

Can I reuse the same test card many times?

Yes. Test cards have no balance limit, so you can run the same number as often as your test suite needs.

Is the CVV on a test card real?

No. Any valid-length CVV is accepted for most test cards, and it is not linked to any account.