Choose from any of our gift cards to give to your loved ones
Razorpay Test Card Details: A Developer's Testing Guide
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.
A Razorpay dummy card is a test card number you use with test mode API keys. It looks like a normal card number, it passes the same validation a real card would, and it moves exactly zero rupees. The payment shows up in your Razorpay dashboard as a test transaction. It never appears in settlement reports, and no bank is involved at any point.
Razorpay publishes its test card list inside the dashboard when you switch to Test Mode, and in the payments test documentation. I check the current list whenever I start a new integration, because the numbers and their mapped outcomes get updated from time to time. Copying a list from an old blog post is how people end up debugging a card that was retired two years ago.
Then repeat the whole flow with a decline card. The interesting bugs live in the failure path, not the happy path. I also test a deliberate timeout and a user who closes the sheet mid payment, because those are the states that leave orders stuck in a pending queue.
The first is mixing key modes. Everything looks right, the card is valid, and the payment still fails because the frontend got a live key from a build variable. The second is assuming the test card is a shortcut to something real. It is not. It exists so developers can exercise code paths without touching a bank network.
The third is testing only the frontend. A dummy card payment that shows success in the browser can still leave your backend without an order, because the webhook signature check failed silently. Log the raw payload during integration and verify the signature before you trust it.
It cannot authorize a real transaction, verify a real card, or reveal anything about a live cardholder. Test numbers are public by design and are rejected outside the sandbox. Any site that offers to sell card details for testing is not selling test data. Storing a real CVV after authorization is prohibited under PCI rules regardless of how the data was obtained, so keep sensitive authentication data out of your database entirely and let the gateway tokenize it.
