AVS CVV Test Validation Buying Guide
Discover how to validate AVS CVV for secure transactions, understand key features, and avoid common pitfalls.
Choose from any of our gift cards to give to your loved ones
Understanding AVS CVV Test Results
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 test card for AVS and CVV is a sandbox card number that a payment gateway maps to preset address and security-code results. Developers use it to check how a checkout reacts when the billing ZIP is wrong or the CVV fails, without touching a live account. The number never charges anyone and works only in test mode.
AVS compares the billing address a shopper types (street number and ZIP in the US) with what the card issuer has on file. The issuer sends back a single-letter code, and the gateway decides whether to approve, decline, or flag the order.
CVV checks the 3-digit code on the back of a Visa, Mastercard, or Discover card, or the 4-digit code on the front of an American Express card. That code is not stored after authorization, so a mismatch points to a stolen card number.
Both checks feed the same decision. A merchant can accept a ZIP mismatch and still block a bad CVV, or the reverse, based on rules set in the gateway dashboard.
Gateways pass through the issuer letter. Sandbox testing lets you force each branch on purpose.
Your gateway rules decide the outcome. Many merchants accept Y and Z, decline N, and review A or U by hand.
Card networks push merchants to check CVV on card-not-present orders, and some acquirers make it a condition of the account. That makes the mismatch path worth testing before launch.
Test numbers follow the normal card format and pass the Luhn check, so they look like real cards to your code. Brand prefixes stay in known test ranges.
Each major gateway publishes its own test cards with the AVS and CVV behavior tied to each one. Stripe lists 4242 4242 4242 4242 as the baseline Visa card that returns a match on both checks.
Adyen, Braintree, Authorize.Net, and Checkout.com keep similar tables in their developer docs. Numbers do not transfer between gateways. A card that returns CVV code N in one sandbox may return M in another, so test against the processor you plan to ship with.
Test numbers are fake, but the data around them is not. Use invented names, addresses, and emails in sandbox so real customer records never mix with test orders. Keep sandbox and live keys in separate environments, and never paste a live card number into a test form.
If your systems store card data, even test data, PCI DSS still applies to them. Most teams avoid the problem by letting the gateway host the payment form and keeping card fields out of their own servers.
Run AVS and CVV cases as part of your checkout regression suite, next to refunds and partial captures. A rule change in the gateway dashboard can flip a decline to an approve, so re-run the suite after any config edit.
Keep one test order per response code and assert on the raw code, not the message string. Message text changes between gateway versions, and brittle tests waste release time.
No. A test number fails when you point it at a live endpoint. Live mode hits real issuer networks, so a fake number returns a no-such-card response.
No. Test cards are simulated and tied to sandbox accounts. Any site that claims to sell goods through test card numbers is not running a real charge.
Sandbox skips the issuer, velocity checks, fraud scoring, and 3D Secure. A card that returns Y and M in test mode can still fail live because of those systems.
AVS started in the US, UK, and Canada. Many issuers elsewhere return U or G, so a decline rule based only on AVS will block good orders.