Razorpay Test Card: How to Use It for CVV Testing
Discover how to use a Razorpay test card for CVV testing in this comprehensive guide.
Choose from any of our gift cards to give to your loved ones
Razorpay Test Card 2025: How Test Payments Work
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.
You do not buy a Razorpay test card. The gateway publishes its test card numbers for free in its developer documentation, and those numbers only work against the sandbox, never against live payments. Your real decision is not which card to purchase but which published number reproduces the exact response you need: success, failure, authentication challenge, or refund behavior. Pick the card that matches your test case, keep it inside the test environment, and treat it as a placeholder rather than as card data.
Group your test cards by the behavior they produce instead of memorizing individual numbers. One band should return an immediate approval. A second band should return a decline, and you want declines at both the authorization stage and the capture stage so your error handling is tested in two places. A third band should force an authentication challenge, which lets you confirm what happens when a customer abandons the challenge or fails it. A fourth band should simulate insufficient funds or an expired card so your retry messaging is accurate. A fifth band should cover refunds, partial captures, and voids, because money movement after the sale is where reconciliation errors surface.
Test cards carry no value and belong to no one. Real card numbers do, and their storage, transmission, and processing fall under a strict industry standard. If your product handles live card data, the safer architecture is to let the gateway collect the card details in its own hosted or embedded form and return only a token to your servers. That approach keeps sensitive data out of your systems and shrinks your compliance scope considerably. Test cards are the tool you use to verify that this flow works before real customers touch it.
No. They are published free as part of the sandbox tooling and exist only for development and quality assurance work.
No. Test mode is isolated from the live payment network, so no funds move and no real cardholder is involved.
Check that you are in test mode, that your API keys are the test pair, and that the number matches a documented success case. A mismatch between key type and card type is the most common cause.
Clear test transactions from reporting views so live analytics are not skewed, and remove any test credentials from configuration files.