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's own sandbox test cards are the top pick for testing a Razorpay integration, because they are the numbers wired to Razorpay's documented test flows. Pick a card on four criteria: the flow you need to exercise (success, failure, or 3DS), the network you must cover, whether the number is reserved for sandbox use, and whether it will still work after the next documentation update. Everything below runs in test mode, where no money moves and no real cardholder data is involved.
Razorpay publishes a set of test cards inside its dashboard and developer documentation. You copy them into your checkout the same way a customer would type a real card, but the request goes to the sandbox instead of the card networks. Sandbox validation tends to be lenient: a future expiry date and a three digit CVV usually pass, and the test OTP flow uses the value shown next to the card in the docs. Confirm the current rules in your dashboard, since gateways revise sandbox behavior without much notice.
Use these when you are building or debugging the integration itself: order creation, checkout callback handling, signature verification, and webhook delivery.
The wider payments industry keeps reserved numbers that never route to a live issuer. The Visa test number 4111 1111 1111 1111 is the best known example and behaves as a successful authorization in most sandbox environments, including Razorpay test mode.
Use these when your test suite spans multiple providers and you want a lowest common denominator card.
A test suite that only proves the happy path is not a test suite. Razorpay and most gateways expose cards or card values that force a decline, a timeout, or a 3DS challenge.
payment.failed events.Use these when you are hardening the checkout, not building it. Run the decline case on every release.
Test mode stops at the gateway boundary. It cannot tell you how a real issuer responds to a velocity check, how a genuine 3DS challenge renders on a customer's phone, how settlement and refund timing works with your bank, or how your app handles a real chargeback. It also will not surface problems caused by live keys, KYC status, or account configuration. Treat a green sandbox run as a smoke test, then do a small live transaction before launch.
Sandbox numbers are safe to paste anywhere. Real card numbers are not. PCI DSS rules forbid storing the CVV after authorization, and rules in India restrict card on file storage for merchants, which is why gateways push tokenization. Never log a full PAN, never email a card number, and never let a test shortcut become a production habit.
Recommended plan: use Razorpay sandbox cards for integration work, one reserved industry number for cross gateway tests, and failure cards in every release pipeline. Then run one small live transaction before you open the doors.