Razorpay Test Card 2025: How Test Payments Work
Razorpay test cards run checkout, refunds, and failure cases in test mode using fake numbers, test keys, and no real money.
Redeem your gift cards at any of our Merchants
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.
Razorpay test payment cards are fixed sandbox card numbers that Razorpay publishes in its own developer documentation. They work only when your account is in test mode with test API keys, they never reach a real bank network, and no one sells them. You copy a number from the docs, drop it into your checkout, run the scenario you need, and move on. Any vendor offering a working live card number or CVV is not selling you a Razorpay test card, and buying that data is a federal offense in the United States under 18 U.S.C. 1029.
A test card is a documented credential pair: a card number, an expiry, a CVV, and often a fixed one time password. The number is public, shared by every developer using the platform, and tied to a simulated response rather than an issuer. Razorpay builds its sandbox around a catalog of these numbers so that specific numbers trigger specific outcomes, such as a successful capture, an insufficient funds decline, or a step up authentication challenge.
This is why test cards are free and downloadable. Their value comes from being predictable, not from being secret. If a number is secret, it is not a test card.
Write down the result your code must handle, then find the number mapped to that result. Teams commonly need four cases: a clean success, a soft decline the customer can retry, a hard decline that ends the attempt, and a challenge that routes through an authentication step. Pick one number per case and keep a small table in your test fixtures so nobody hunts through docs mid sprint.
Test cards behave differently depending on whether you run a standard checkout, a saved card charge, a subscription mandate, an international card, or a wallet. A number that succeeds in a one time payment may not exercise recurring behavior, and a domestic test card will not simulate cross border rules. Match the card to the flow under test.
Many sandbox cards push the transaction through a simulated verification screen with a fixed code. If your integration skips that screen, you are testing a path real customers will hit and your code will not see.
No. They are published free in Razorpay's developer documentation. Paying for them means you are buying something else, most likely stolen card data.
No. Test mode transactions are simulated end to end. Nothing settles, no funds move, and no issuer sees the request.
Usually one of three causes: you are in live mode with test credentials, you grabbed a card that is mapped to a decline outcome on purpose, or your request is missing a field the simulation validates.
Yes, if you use a card documented for recurring or mandate flows. Standard one time cards often will not simulate the follow on charge behavior.
They are safe in the sense that they are public, but keep them in a clearly labeled fixtures file so nobody mistakes them for live credentials during an audit.