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.
CVV test tokenization means running a tokenization setup in a sandbox with network-issued test card numbers, where the CVV is a published test value or left out where the processor allows it. You are checking three things: that your code creates a token, that you get a clear authorization response back, and that nothing sensitive lands in your logs or database. A real CVV never turns into a token. No test pass tells you whether a live card is valid.
Tokenization replaces the card number with a surrogate value that is useless outside its defined domain. The CVV works differently. It exists to prove the card was present at the moment of authorization, and the card networks and PCI DSS classify it as sensitive authentication data. It must not be stored after authorization, not even encrypted. There is nothing left to tokenize. The CVV travels to the issuer inside the authorization request and is discarded.
That rule explains most of the confusion around the phrase. A service that advertises stored or "tokenized" CVVs is either describing a test fixture or ignoring the standard.
Processors publish fixed test card numbers with fixed CVV values. Visa, Mastercard and American Express all issue test BINs for this purpose, and gateways like Stripe and Adyen document their own sets along with decline triggers. In sandbox mode the CVV field is usually validated against that fixed value, or skipped entirely for card types that do not require it. Either way the number never leaves the test boundary.
I look for one thing when reviewing a tokenization integration: whether the team understands that the sandbox is a simulation. A test CVV validates your plumbing, not a card. There is no legitimate endpoint that checks whether a real card and CVV pair is live without a full authorization, and running real card numbers through a test environment breaks card network rules and your merchant agreement.
