A Razorpay test card is a published card number that works only in Razorpay test mode, letting you simulate payment success, failure, and 3D Secure steps without moving real money. The standard example is 4111 1111 1111 1111 with CVV 123 and any future expiry date. The same number is rejected as soon as your integration uses live API keys.

What a Razorpay test card actually does

Test cards exist so developers can run the full checkout flow, including authorization, OTP entry, webhook delivery, and refund logic, against the Razorpay sandbox. No bank is contacted and no funds settle. The card data is synthetic, which means it cannot be used to buy anything outside the test environment.

Because the numbers are public, they are safe to store in your repo, share with a QA team, and paste into automated test suites.

Common Razorpay test card details

• Visa: 4111 1111 1111 1111, CVV 123, any future expiry date
• Mastercard and RuPay: Razorpay publishes network-specific test numbers on its test card reference page, including cards that force specific error codes
• Cardholder name, email, and phone: any synthetic values, since nothing is verified against a real account
• OTP step: the simulated 3D Secure challenge accepts the test OTP listed in the Razorpay documentation

Test cards only work with test mode keys

This is the mistake that wastes the most debugging time. Your key ID must start with rzp_test_. If the integration is initialized with a rzp_live_ key, Razorpay routes the request to the live network, where a test card number fails as an invalid card.

The reverse case is just as important. A real card number entered into test mode will not process, and entering real card data into a sandbox creates a compliance problem for no benefit.

Simulating failures, UPI, and netbanking

• Card failures: the test card page lists numbers that trigger insufficient funds, expired card, and authentication failure responses so you can exercise error handling
• UPI: test VPAs such as success@razorpay and failure@razorpay control the outcome of a UPI payment in test mode
• Netbanking: test mode exposes a bank list with simulated success and failure paths
• Webhooks: point your endpoint at a test URL and confirm that signature verification passes before you go live

Rules for clean test data

1. Keep test keys and live keys in separate environment files so they cannot be swapped by accident
2. Never store the CVV after authorization, even in test mode, because that habit tends to follow code into production
3. Use fake names, emails, and addresses in test payloads instead of copies of real customer records
4. Rotate test keys if they were committed to a public repository
5. Re-run the full flow with live keys and a small real transaction before launch, since test mode does not replicate bank latency or issuer rules

Quick checklist before you ship

Confirm that your success, failure, and pending states all render correctly, that refunds settle in the dashboard, and that webhook retries are Idempotent. If those pass in test mode with a Razorpay test card, your payment integration is ready for a live smoke test.