Razorpay test cards are dummy card numbers that work only in test mode. The standard Visa number is 4111 1111 1111 1111, paired with any future expiry date and any three-digit CVV. The Mastercard equivalent is 5267 3181 8797 5449. Both are processed against test API keys, so the payment appears in your dashboard as captured while no real card is charged and no money moves.

What test mode changes

Test mode swaps the live payment network for a simulator. Card validation, 3DS screens, and webhooks behave like production, but authorization is faked. A test key ID starts with rzp_test_; a live key starts with rzp_live_. If a test card is entered on a checkout loaded with a live key, the payment fails, and if a real card is entered in test mode, nothing is charged but nothing is verified either.

Prerequisites

• A Razorpay account with dashboard access
• Test mode API keys generated under Account & Settings
• A checkout page or server-side order flow already wired to the Razorpay SDK

How to pay with a Razorpay test card

1. Open the Razorpay Dashboard and switch the mode toggle from Live to Test.
2. Go to Account & Settings, then API Keys, and copy the key ID beginning with rzp_test_.
3. Replace the live key ID in your checkout code with the test key.
4. Create a test order on your server and pass the order ID to checkout.
5. Load your checkout page and choose the Card payment method.
6. Enter 4111 1111 1111 1111 as the card number.
7. Enter any future month and year as the expiry.
8. Enter any three digits, such as 123, as the CVV.
9. Complete the simulated bank page if it appears; it does not contact a real issuer.
10. Submit the payment and confirm the status in the dashboard Payments tab.

Values that work in the sandbox

• Visa: 4111 1111 1111 1111
• Mastercard: 5267 3181 8797 5449
• Expiry: any month and year in the future
• CVV: any three digits
• Cardholder name, email, and address: any well-formed value

The same pattern applies to other instruments. Test UPI IDs such as success@razorpay approve a payment and failure@razorpay decline one, which is faster than filling a card form when you only need a captured payment.

Testing declines and 3DS

Razorpay keeps a separate list of test cards that trigger specific failures, including insufficient funds and authentication failure. Pull the current list from the test card reference in the dashboard before writing decline-handling tests, because the numbers are changed when the simulator is updated. Do not invent random card numbers: test mode validates against a known set and rejects anything else with a generic failure that tells you nothing about your error handling.

Rules that keep test data clean

• Keep test keys out of production builds and commit history.
• Never let test card numbers reach a live endpoint, even in a debug flag.
• Tag test customers or orders so analytics and support queues can filter them.
• Delete test orders before enabling live traffic on the same account.

Test card data is public by design, and that is exactly why it must stay inside the sandbox. Production systems should only ever see card numbers entered by real customers through a PCI-compliant form.