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.
The number to reach for first is 4242 4242 4242 4242, a Visa test card that approves any charge in Stripe test mode. It wins on three criteria that matter for payment testing: it works with any future expiry date, it accepts any three-digit CVC, and it behaves the same across Checkout, Elements, Payment Intents, and the CLI. Around it sits a small set of numbers that exist to break things on purpose, so you can watch your error handling run without touching a real account.
Stripe test cards are ordinary card numbers that Stripe routes to its sandbox instead of a card network. They only work when you authenticate with a test mode API key, a key that starts with pk_test_ or sk_test_. Pair one with a live key and the charge fails or gets declined. Nothing about these numbers is secret; they are published so developers can build and demo checkouts.
Use this for happy-path tests, screenshots, and demos. It returns a successful charge with no authentication step, which makes it the fastest way to confirm that your form posts, your webhook fires, and your order shows up in the dashboard. If you need a charge that succeeds and then settles normally, this is the one.
When you need to prove that your brand detection, card icon, or surcharge logic works, swap in a card from another network.
Error handling is where most checkouts break, and you cannot test it with a card that always approves. These numbers trigger specific decline codes.
Each one maps to a code in the error object your code reads. Log the raw code, show a human message, and keep the two separate.
Authentication flows are the hardest part of a checkout to test, because the outcome depends on a redirect or a modal. Stripe publishes a separate set of cards for this, including 4000 0025 0000 3155 for a charge that requires authentication, and 4000 0000 0000 3220 for a 3D Secure 2 challenge. The exact list shifts as card network rules change, so confirm the current numbers in Stripe's testing documentation before you script a regression suite around them. Test the failure branch too: a customer who abandons the authentication step should leave your order in a pending state, not a paid one.
If you are writing server-side tests, you can skip raw numbers and pass a token instead, for example tok_visa or tok_mastercard. Tokens create a card source without a form submission, which keeps fixture setup short. For mobile wallets and bank debits, Stripe also has test payment method IDs that follow the same idea.
Test cards exist so that a decline in production is a scenario you already rehearsed. Pick 4242 4242 4242 4242 as your baseline, keep a decline card and a 3DS card next to it, and your checkout will handle real traffic with far fewer surprises.
