Choose from any of our gift cards to give to your loved ones
Razorpay Test Card CVV: What to Enter in Test Mode
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.
The Razorpay sandbox test card is 4111 1111 1111 1111. Use any future expiry date, any three digit CVV, and OTP 1234 if the simulated bank asks for one. It works only with test keys, the ones that start with rzp_test_, and only while your account is in test mode.
Test mode does not touch a real network. Razorpay hands the payment to a simulated acquirer that approves the 4111 number by default and skips the actual authorization. That means no money moves, no settlement happens, and the payment shows up in your dashboard as a test payment you can refund, capture, or fail on purpose. I keep one test order open in a browser tab while building checkout flows, because the fastest way to spot a broken integration is to run the same card twice and compare what the dashboard records.
Expiry and CVV fields accept any valid-looking value, so 12/34 and 123 both pass. Amex is the exception: the CVV field wants four digits, and a three digit entry fails validation before the request ever leaves the browser. If you test card saving or tokenization, run the same number twice and confirm the saved card shows up with the right last four digits.
When 3D Secure is enabled on the test flow, Razorpay shows an OTP screen. Enter 1234. Some test configurations auto-submit the OTP and never show the screen, which is normal and depends on the payment method settings on your account. If you build an automated test suite, pause for the OTP frame instead of assuming the success page loads straight away.
UPI uses a different set of placeholders. success@razorpay simulates a successful collect request and failure@razorpay simulates a declined one. Netbanking in test mode lets you pick any listed bank and returns success without a real login.
Test card numbers are public placeholders. They have no linked account, no balance, and no use outside a sandbox. A real card number and its CVV are issued by a bank to one person and cannot be stored after authorization under PCI rules, so treat any source that offers to sell them as fraud rather than a shortcut. Keep test keys out of client side bundles and commit history, and rotate them if they leak.
