Razorpay Dummy Card: What It Is and How to Test With It
A Razorpay dummy card is a test card number that works only with test mode keys. Here is how to find it, run a full test payment, and avoid the usual mistakes.
Redeem your gift cards at any of our Merchants
You can purchase a gift card from any of these locations
Onyx Gift Cards is a Grenadian company designed to introduce, market and manage gift cards systems in Grenada for retailers and corporations. We are enthusiastic about the effect and influence we will have on the local market. We intend to expand our systems regionally with a range of product offerings and services.
Gift cards are the preferred way of giving and receiving gifts. They carry a monetary value that can be redeemed for gifts at your favorite store.
Onyx GiftCards are “Open Gift Cards” which means that they can be redeemed at multiple merchant locations. They are standard credit card size, can fit into the average wallet and made of PVC plastic. Onyx GiftCards are Barcoded for security and safety for the consumer and bear a disclaimer at the back.
Onyx Giftcards can be bought with a branded Card backer which is black in colour and is designed to fit the card. There is an area to write a brief message to the recipient as well.
My top pick for a first pass is the Visa number 4111 1111 1111 1111 with any future expiry date, any three digit CVV, and OTP 1234. It is the entry most consistently listed in Razorpay's own test card set, and it walks the success path in hosted checkout, the JavaScript SDK, and the Orders API. I judged every option below on four criteria: whether the number appears in Razorpay's published test card list, whether the result is repeatable, whether it works across checkout flows, and whether it stays inside test mode with no real money moving.
Test card details are fake card numbers that Razorpay publishes for its sandbox, called test mode. You activate test mode with test API keys, and the gateway responds with simulated results instead of contacting a card network. No authorization is sent to an issuer, no settlement happens, and the numbers are public by design. The expiry field accepts any future date and the CVV accepts any three digits, so the only thing that matters is the card number and the mode your keys belong to.
One caveat matters more than the numbers themselves. Razorpay updates its test card list from time to time, so confirm the current set in the dashboard under the test mode payment section before you write it into a test suite.
Use this when you need a payment to succeed on the first attempt and you want the least configuration across flows.
Use case: smoke tests on a new integration and demo environments where you want a payment to complete without extra setup.
This is the usual second card in the same test set and the one to reach for when your checkout branches on network.
Use case: regression runs that need at least two networks, and any UI that displays a card brand icon.
A success card alone will leave your error handling untested, and error handling is where most production incidents start. Razorpay's test card list includes entries that trigger specific failures such as a declined payment, an expired card, or a processing error. Rather than hardcoding a decline number you found in a blog post, pull the current list from your dashboard and map each failure card to the error code your code expects.
Use case: pre launch QA and any change to your payment result handler.
Razorpay also documents test instruments for other methods, which matters because a large share of real traffic will not use a card at all.
success@razorpay and failure@razorpay as the VPA handle for simulated outcomes.Use case: verifying that your method selection screen and each downstream handler works, not just the card form.
Test cards typically route through a simulated authentication screen. Enter 1234 as the OTP to approve, and use the failure option on that screen to simulate an abandoned or rejected authentication. Confirm that a cancelled 3DS step leaves the order in a state you can retry rather than a state that looks paid.
Real card numbers and CVVs should never appear in a test environment or a repository. Handling genuine card data brings PCI DSS obligations, so keep production credentials out of developer machines entirely.
Start with 4111 1111 1111 1111 for a success run, add 5104 0600 0000 0008 to cover the second network, then add one failure card per error branch in your code. Add the UPI handles for non card coverage. That set of six or so instruments covers most of the paths a Razorpay integration can take, and it stays entirely inside test mode.