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 Stripe test card is a card number that Stripe accepts only when your account is in test mode. It moves no money, reaches no bank, and touches no real card network. The number you will use for most of your work is 4242 4242 4242 4242, paired with any future expiration date, any three digit CVC, and any postal code. If you can remember one thing about testing payments, remember that one.
Stripe publishes a set of numbers where each one is rigged to produce a specific outcome. That is the whole point. You are not testing whether the number is valid, you are testing how your code responds to the answer Stripe sends back.
Brand behavior differs in ways that matter. Amex uses four digit CVCs and a different number format. Discover, JCB, UnionPay, and Diners Club each have a test number, and if your checkout renders brand logos or enforces length rules per brand, you want to run one charge through each. Visa 4242 is not a substitute for 3782 822463 10005.
They only work with your test API keys. Pair a test number with a live key and Stripe rejects it, which is why a strange decline in production sometimes means somebody pasted a test number into a real order. Test mode also keeps its own customers, subscriptions, invoices, and webhooks, so nothing you build there appears in your live dashboard.
Radar and your own risk rules still apply in test mode. A card that is supposed to succeed can come back blocked if your rules are strict, and that is usually a configuration problem rather than a bug in your integration.
You rarely need to type a number into a form to test server side logic. Stripe exposes test payment methods with names like pm_card_visa, pm_card_mastercard, pm_card_amex, and pm_card_visa_chargeDeclined. The CLI goes further and can fire whole events, such as stripe trigger payment_intent.succeeded, so you can exercise your webhook handler without touching a browser.
The human readable message is for your customers. Your code should branch on the decline code, because that is what tells you whether to ask for a different card, retry, or stop. Testing each decline number against your error handling is the fastest way to find the place where you swallow a failure and show a blank screen.
Recurring billing is where test cards alone fall short, since you cannot wait a month for the second invoice. Test clocks let you advance time and watch renewals, dunning, and proration play out. Combine a clock with 4000 0000 0000 0341 and you can rehearse the exact moment a signup succeeds and the first charge fails.
