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.
Do not pay for a test card number. Every major payment processor publishes its sandbox card numbers free in official developer documentation, and a paid list is almost always a copy of that documentation, a stale scrape, or numbers that were never test cards at all. The only real decision is which processor sandbox you build against, because a test card number is tied to one environment and returns nothing useful anywhere else.
A test card number is a payment card number reserved for sandbox use. It belongs to no account and no cardholder. It passes the same format checks as a live card, including the brand prefix and the Luhn check digit, and the processor's test environment returns a scripted result when it sees that number. Valid format plus no real account equals a safe input for development and quality assurance work.
Card numbers run 12 to 19 digits, with 16 as the common length. Every number must pass the Luhn check. Security codes are 3 digits, except American Express at 4. The expiry date has to sit in the future at the time you run the test, so a set copied from an old blog post will fail for the wrong reason. Test amounts usually sit in a narrow window, often a small fixed value, and some sandboxes trigger special outcomes on exact amounts. Card brand prefixes follow the ISO/IEC 7812 scheme, so a number starting with 4 behaves as Visa and one starting with 5 behaves as Mastercard inside the sandbox, matching what you see in production.
Yes. Processors publish them as part of their developer documentation at no cost. Anyone charging for a test card number is selling something you can get directly from the source.
No. Live systems reject them, and attempting to push one through a live payment path you do not control is fraud, not testing. Use them only against a sandbox you are authorized to access.
Do not. Sandboxes are built to reject live card data, and entering real cardholder data into a development system creates a compliance problem with no upside.
Check three things in order: the expiry date is still in the future, you are pointed at the sandbox endpoint rather than the live one, and the security code and postal code match what the documentation specifies for that number.
Enough to cover each branch your integration handles. A typical checkout flow needs one approval, two or three distinct declines, one authentication challenge, and one card that the sandbox treats as expired.
