A Razorpay test card is a placeholder card number you use inside Razorpay's sandbox to simulate a customer payment. It looks and behaves like a real card during checkout, but it never touches a live bank account, so nothing is charged and no money moves. Developers use it to confirm that orders, webhooks, refunds, and error messages all behave correctly before switching the integration to live keys.
What is a Razorpay test card used for?
Test cards exist so you can rehearse the whole payment journey. You drop a test API key into the checkout, enter a dummy card, and Razorpay returns a realistic response: success, failure, or a pending authentication step. That makes it easy to reproduce edge cases such as a declined card, an expired card, or an abandoned 3D Secure prompt without involving a real customer or a real bank.
Key Features
- Works only with test-mode API keys and the sandbox checkout experience.
- Includes a standard success number, widely cited as 4111 1111 1111 1111.
- Covers other networks for compatibility checks, such as the Mastercard and Amex test numbers listed in the docs.
- Provides dedicated failure numbers that simulate declines, insufficient funds, and authentication errors.
- Supports UPI test handles such as success@razorpay and failure@razorpay for non-card flows.
- Lets you exercise authorized, captured, refunded, and failed payment states in the dashboard.
- Produces no real charges, no settlement, and no stored cardholder data.
- Works with standard checkout, payment links, subscriptions, and recurring mandates in test mode.
Specs and sandbox behavior
Test cards only respond when the integration is pointed at test mode. Enter any future expiry date and the CVV published alongside the number in the official table, then complete the simulated one-time-password step the sandbox presents. Amounts, currency, and payment states behave like live data, so your dashboard fills with realistic orders you can capture, refund, or let expire. Because these numbers are public and disposable, they must never be used to process a genuine payment, and live keys should never be mixed into a test environment.
Is it safe to use test cards?
Yes. Sandbox payments are isolated end to end: no settlement occurs, no cardholder data is retained, and no real account is debited. Treat the environment as disposable and reset it whenever you want a clean slate.
Do Razorpay test cards work in live mode?
No. The live gateway rejects them. If a test number appears to succeed in production, your integration is still running on test keys and needs to be corrected before launch.
Where do I find the current list of test cards?
Razorpay publishes the up-to-date numbers, CVVs, and UPI test handles in its developer documentation. The list changes occasionally, so confirm it there before you hard-code anything into an automated test suite, and reach out to sandbox support if a documented number stops responding.