Sell CVV and Get Paid Quickly
Discover how to sell CVV codes and receive fast payments with our secure platform.
Our Cards
Choose from any of our gift cards to give to your loved ones
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 test payment card is a card number a payment processor publishes for use in its sandbox. It behaves like a real card inside test mode and does nothing outside it. No funds move, no bank is contacted, and the same number will fail if you send it to a live endpoint.
Every checkout flow has branches that are hard to trigger on demand: a declined authorization, an expired card, a 3D Secure challenge, a currency mismatch. Waiting for a real customer to hit each one is not a plan. Test cards let you force those branches on purpose, in a repeatable way, before you take a single live transaction.
I treat them the same way I treat fixtures in a test suite. Same input, same expected output, every run.
Most published test numbers are structurally valid. They pass the Luhn checksum, they carry a real issuer identification number prefix (4 for Visa, 51 through 55 and 2221 through 2720 for Mastercard, 34 and 37 for American Express), and they have a plausible length. What they do not have is a funding account behind them. Your processor recognizes the number in test mode and returns a scripted response.
Those four cover most smoke tests. Beyond them, each processor adds its own set for specific decline codes and authentication outcomes, and the list changes over time. Pull the current set from your processor's testing docs before you wire anything into a build pipeline.
This trips people up more than anything else. A test card number is not a magic key. It only produces the scripted result when the request goes to the test environment with test API keys. Send 4242 4242 4242 4242 through a live endpoint and you get a real decline, often with a message about an invalid account.
Approvals are the easy part. The value sits in the failure paths.
They confirm your integration logic. They do not confirm that your live account is fully activated, that your settlement and payout timing matches expectations, or that your fraud rules behave the way you think. Issuer behavior varies, dispute flows involve real money, and a clean sandbox run says nothing about those. Plan a small live launch with real amounts and someone watching the dashboard.
Two rules I follow. Never let a test number reach a live endpoint, and never let a card number of any kind land in a log, an error tracker, or a database column that was not designed for it. Even a sandbox PAN is worth keeping out of your log pipeline, because the habit is what protects you when the values are real.