CVV Verification Guide: How to Safely Buy CVV
Learn how to verify CVV codes safely when buying CVV online. This guide provides essential steps and tips for secure transactions.
Our Cards
Choose from any of our gift cards to give to your loved ones
Choose from any of our gift cards to give to your loved ones
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.
A CVV test with 3D Secure is a sandbox transaction that pairs a published test card number with its matching test CVV and pushes it through a simulated 3D Secure challenge. It confirms that your checkout reads the CVV field and that your code handles the 3DS authentication step before any real card is charged. Every major processor publishes the values you need, so no live card data is involved.
Two systems talk during a card payment: the CVV check and the 3D Secure authentication. A sandbox test exercises both so you can see which one fails when a payment is declined.
The CVV check compares the code on the card with the value the issuer holds. 3D Secure adds a cardholder authentication step on top, and both results travel back to your code as separate fields.
Test cards make this repeatable. Each published test number comes with a fixed CVV and a fixed 3DS outcome, so the same input produces the same result on every run.
Payment providers publish test card numbers with the CVV, expiry, and 3DS behavior printed next to them. Treat your own processor's page as the source of truth, since the mapping changes.
Any future expiry works for most test cards, and the CVV field accepts the test value only in sandbox mode.
Without 3DS, a test card submission returns one result: approved or declined. With 3DS, the authorization pauses while the cardholder authenticates, then resumes.
Sandbox environments simulate that pause with a challenge page or a mobile SDK window. Your integration must hand control to that window and read the callback before it can read the final authorization.
3DS returns an authentication value that maps to three outcomes: authenticated, attempted, or failed. Test cards exist for each outcome, which is how you cover all three branches of your error handling.
3DS2 moves much of the authentication into the background, so many sandbox tests never show a challenge page. The CVV is still submitted with the authorization, and the authentication result still arrives as a separate value.
Frictionless flows in test mode return an authenticated result with no cardholder step. A test that shows no prompt can still be a correct 3DS2 test.
A sandbox account with your processor, a test API key, a return URL registered in the dashboard, and your processor's test card page open in a second tab.
Turn request logging on. A 3DS test produces at least two server responses, and the gap between them is where the bug hides.
Card networks ban live card numbers in test environments, and a test that uses someone else's card is card fraud, not testing. There is no legitimate source for live CVV data outside the cardholder and the issuer.
PCI DSS also forbids storing the CVV or CID after an authorization completes. That rule exists so a leaked database cannot be used to run card-not-present transactions.
Sandbox test values exist so this never becomes necessary. A tool that offers to sell you CVV data is selling stolen card records, and using one exposes you to criminal liability in every US state.
Yes. Sandbox 3DS flows use published test cards and a simulated challenge window. No live card or real issuer is involved.
It matters for format and for the CVV check step. The sandbox compares your input against the value the test card expects, then runs the 3DS step as a separate test.
Authentication and authorization are separate stages. 3DS proves the cardholder approved the payment; the authorization then checks funds, card status, and risk rules. A test card set to decline can pass 3DS and still fail the charge.
Sandbox responses arrive in seconds. If a test hangs, the callback URL or the challenge window is the usual cause.