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 test validation message is the response a payment processor returns when it checks the 3- or 4-digit card verification value on a transaction. It reports one of four states: match, mismatch, not processed, or not supplied. You see it in sandbox runs while building checkout code, and in live authorization responses while running a store.
Card networks use single-letter result codes for the CVV check. Processors pass them through under different field names, so match on the letter, not the label.
American Express codes are 4 digits. Visa, Mastercard, and Discover use 3. A wrong digit count sends a bad value before the issuer ever sees it.
Read the gateway's request log first. Most sandbox failures trace back to the request body, not to the gateway.
Most sandbox gateways ignore the CVV digits when you use their published test card numbers. Any 3 digits work, and any 4 digits work for Amex cases. A few processors ship fixed test values that force a result, such as a mismatch, so you can exercise your error handling.
Read the processor's test data page before you debug your own code. Test card lists change, and a number that worked last year can be retired.
A CVV result is one field in a larger payload. Look at all of it:
A CVV mismatch can still approve. Many issuers send the N code as data and let the merchant's fraud rules make the call. Check your gateway settings to see whether a mismatch blocks the charge or flags it.
A timeout returns no CVV result at all. Treat that as unknown, never as a match, and log it for review.
No. A decline is a decision. A CVV result is evidence, and the issuer or your rule set weighs it with other data.
Some gateways turn an N result into an automatic decline for card-not-present orders. Others pass it through. Know which mode your account uses before you tell a buyer that a retry will fix the charge.
PCI DSS Requirement 3 bans storing the CVV after authorization in any form, hashed or encrypted included. If your database holds that field, delete it and fix the code path that writes it.
They do not. A working CVV tied to a live card number is stolen card data, and buying or selling it is card fraud. Legitimate CVV testing uses sandbox numbers a processor gives you, not a list sold on a forum. If a tool asks for a real card's CVV to "verify" it, that is a phishing pattern.
No. Card-present transactions with a chip or a contactless tap skip the check, since the chip handles authentication. Card-not-present orders return the code when the issuer takes part. Wallets and network tokens can return U when the card check is not exposed to you.