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 payment is a transaction sent through a payment gateway sandbox using a published test card number and its matching test CVV code. The gateway runs the request through its normal authorization logic and returns a simulated response, so a developer can confirm the checkout form, the token vault, and the decline path all behave as designed. No money moves and no real cardholder is involved.
The CVV (card verification value) is the 3-digit code on the back of most cards, or the 4-digit code on the front of American Express cards. The issuer compares that code against its own records during authorization. That one check decides whether the transaction approves or comes back as a CVV mismatch.
Sandbox card numbers look like live card numbers, and the gateway validates them the same way it validates live traffic. Test CVV codes let you trigger a specific result on purpose instead of hoping for one.
Most providers publish at least one card that always fails verification, alongside cards that always pass. Stripe and Authorize.net both document these pairs, and the failure card is the one most developers forget to test.
Both use the same field, the same length rules, and the same gateway endpoint. The difference sits behind the endpoint.
Card networks define verification outcomes in the authorization response, and gateways translate them into readable strings. You will see them in your sandbox responses and in production.
Build your UI to handle each one. A shopper who sees "no match" needs a different prompt than a shopper who sees a system error.
PCI DSS bans storing the CVV after authorization, in any form, including encrypted. If your code writes the code to a database, a log file, or an analytics event, you are out of compliance and you carry the breach risk.
Send the value straight to a tokenizing endpoint or a hosted field so it never touches your servers. Add a unit test that posts a fake CVV and asserts the string appears nowhere in your output.
Test card numbers work only inside a sandbox. Outside it, they fail at the gateway before they reach any issuer, so a test number cannot buy anything.
Using another person's card details is payment fraud, whether or not a code check passes. Card verification values are issued with the card and belong to the account holder, and no legitimate business sells them. Anyone offering CVV data for sale is describing a crime, and the buyers and sellers both face criminal charges.
No. Sandbox transactions run against fake card numbers tied to test profiles, so no account is debited and no statement entry appears.
Not always. Some providers accept any 3-digit value in test mode, while others tie the code to a specific test card. Read the docs for the gateway you use.
Many gateways skip verification in test mode by default. You need the special failure card or a dashboard toggle to force the decline.
If you handle real card data anywhere, yes. Sandbox credentials and test numbers carry no cardholder data, but the code path you build during testing is the one you ship.
A sandbox request usually returns in under a second. If it hangs, the problem sits in your keys, your endpoint URL, or your network setup, not the gateway.
