CVV Test Validation Response Guide
Learn about CVV test validation response and how to interpret it when buying CVV.
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 CVV validation error means the security code a customer typed did not match what the card issuer has on file, or the checkout field itself rejected the input before it ever reached the issuer. This guide explains where those failures come from, how to reproduce them safely in a sandbox, and what the numbers behind a decline actually tell you. It is written for merchants, developers, and support teams who need to tell a customer typo apart from a genuine gateway problem.
Most errors fall into three buckets: a formatting failure in your own form, a mismatch returned by the issuer, or a decline triggered by risk rules. Formatting failures happen when the field accepts letters, spaces, or the wrong digit count. Issuer mismatches come back as a specific response code, typically a CVV/CVC non-match, and often pair with an address verification result. Risk-rule declines are your processor blocking the attempt before the issuer is even asked.
Always test against your processor's sandbox using its published test card numbers, never a live card. Sandboxes return deterministic responses, so you can force a CVV mismatch, an expired card, or a do-not-honor decline on demand and confirm your error messaging is accurate. Log the response code and the decision path, but never log the code itself. Retry logic should cap attempts and fall back to a clear message rather than a generic failure.
On the technical side, acceptance rules are narrow. Most networks use a three-digit value printed on the signature panel; one major network uses four digits printed on the front. The field should accept digits only, strip spaces and dashes automatically, and validate length by detected card type. Under PCI DSS, the code may be used to authorize a transaction but must not be stored after authorization, which is why tokenization exists for recurring billing.
Access is delivered digitally and immediately after checkout, so there is nothing to ship. If the material does not answer your question, contact support within the stated window for a full refund — no return required.
Usually yes. Ask them to re-enter the code exactly as printed, without spaces, and to confirm they are reading the code and not the card number. If it fails twice more, the safest path is a different payment method rather than repeated attempts.