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 3D Secure test card is a sandbox card number that a payment processor publishes so you can trigger a simulated 3DS challenge. You type it into a test checkout, the issuer simulator asks for authentication, and you choose the outcome you want: pass, fail, or no challenge at all. No real card is involved and nothing settles.
3DS adds a redirect or an in-app challenge between checkout and authorization. That step has more branches than a plain card charge, and each branch produces a different response. Testing every branch with a live card would be slow, expensive, and impossible to repeat. Test cards give you one deterministic number per branch, so the same input produces the same result on every run.
Stripe documents 4000000000003220 for a 3DS2 challenge and 4000000000003063 for a 3DS required flow. Adyen and Checkout.com publish their own lists. I keep the table for the processor I am integrating with bookmarked, because these numbers are not interchangeable across gateways. A number that challenges on one provider may pass straight through on another.
Most sandboxes follow the same sequence. You create a payment intent, submit the test card, the 3DS method URL fires, a challenge is shown or skipped, an authentication result is posted back, and only then does the authorization happen. Sandbox environments often let you pick the authentication result directly from a modal instead of typing a one-time code, which is faster when you are running a suite of automated checks.
Test numbers work only in test mode. Live PANs, CVVs, and expiration dates belong in a PCI DSS compliant environment and never in a test account, a log file, or a spreadsheet. If you need volume for load testing, generate synthetic values or use the processor's own test cards.
Run each authentication outcome at least once, confirm your webhook handler reacts to the authentication result and not just the charge, and test the case where the customer closes the challenge window mid-flow. That last one is where most integrations break, and it is the one you cannot reproduce with a plain card number.
