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.
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 card testing means running payments through Razorpay Test Mode, a sandbox that accepts fake card numbers and a separate key pair while no real money moves. Developers use it to check checkout, authorization, capture, refunds, and webhooks before launch day. Test keys start with rzp_test_ and fail as soon as you switch to a live key.
The sandbox is separate at every layer: keys, dashboard data, card list, and webhook secret. A test payment never reaches a card network, so the test card you type decides the result.
The toggle matters. A test key sent while the dashboard sits in Live Mode creates confusion, and a live key sent from a test build charges real customers.
Razorpay ships a card list where each number maps to one outcome, and the current list lives in the official docs because it changes. The Visa number 4111 1111 1111 1111 is the common success card across gateway sandboxes, and most test cards accept any future expiry date with any CVV.
Card networks do not matter much inside the sandbox, but you should test at least one card from each family your customers use.
Pick a failure card from the docs and complete the checkout as normal. The response carries an error code and description, which your frontend should map to a readable message. Log both values, because one code can cover several decline reasons.
A 3DS test card sends the user to an authentication page before the payment finishes. Enter the test OTP from the docs, then confirm your server handles the success callback and an abandoned challenge. Skip this step and your live 3DS flow breaks in ways your test suite never saw.
The flow logic stays identical, which is the point. Code that works against the test key should work against the live key once you fix the config.
Webhook events fire in test mode with the same names as production: payment.captured, payment.failed, refund.processed, and others. You point the test webhook at a staging URL, verify the signature with the test secret, and inspect the payload.
Two habits save time. First, verify signatures from the raw request body rather than a parsed object, since frameworks can reorder fields. Second, store the event ID and skip repeats, because Razorpay retries a delivery when your endpoint does not answer with a 2xx status.
Test Mode answers only to its own card list, so a genuine card number, CVV, and billing address return a decline. That design keeps production card data off developer machines, which PCI DSS demands: sensitive authentication data such as the CVV must never be stored after authorization.
If you need a card that charges, use a provider sandbox or a tokenized test card from the issuer. Never paste live card data into a staging database or a shared spreadsheet.
No. No money moves, no settlement happens, and no fee applies. The sandbox runs outside the card networks.
4111 1111 1111 1111 is the common success number. Razorpay's docs hold the full list, and it changes, so copy numbers from there rather than a blog post.
Yes. Razorpay provides test UPI IDs and test bank options that simulate success, failure, and pending states.
Generate a live key pair, swap the keys in your environment, point webhooks at your production URL, and run one low-value live payment before you announce the launch.