Choose from any of our gift cards to give to your loved ones
AVS CVV Test Results: How to Interpret and Use Them
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 AVS test card is a card number that a payment processor publishes for use in its sandbox environment, so developers can test card verification value (CVV) checks and address verification system (AVS) responses without touching a real account. It carries no value, belongs to no cardholder, and only works against test API keys. A test card is not a real card, and no legitimate processor sells one.
Both mechanisms are fraud screens that a merchant sends along with an authorization request. Neither one moves money on its own.
Common AVS response codes include Y for a full match, A for street match only, Z for ZIP match only, N for no match, and U for address information unavailable. CVV returns a similar small set, typically M for match, N for no match, and U for unavailable.
Every major gateway ships a documentation page of sandbox card numbers. Stripe, Adyen, Braintree, and similar providers each publish a set tied to specific outcomes: an approval, a decline, a CVV mismatch, a ZIP mismatch. Testers pick the number that produces the result they need to handle in code.
These numbers only validate in test mode. Run one against a live API key and it declines, because the number fails the Luhn check or is blocked outright. That separation is the whole point of the design.
Dropping a live card number into a sandbox, a spreadsheet, or a chat thread turns a routine test into a data handling problem. Card verification values are sensitive authentication data under PCI DSS, and storing them after authorization is prohibited. Test data removes that risk entirely, which is why processors make it easy to get.
If you need realistic test scenarios, generate the numbers once in the sandbox and keep them in a fixtures file alongside the rest of your test data.
Search results for CVV terms are crowded with vendors offering to sell card data. That activity is card fraud. Possessing or trading another person's card details is a crime in the US and most other jurisdictions, and the card networks actively monitor for it. A test card costs nothing, comes from your own gateway, and keeps you inside the rules. Anyone charging money for a CVV is selling stolen data, not a testing tool.
