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 card test environment is a sandboxed copy of a payment gateway that processes transactions using fake, gateway-issued test card numbers. It mimics real authorization, capture, decline, and refund flows so developers can build and debug checkout code without touching live card data or moving real money. No test card number in a sandbox can be used to buy anything.
Engineering teams use sandboxes to validate payment integrations before launch and after every code change. The environment returns deterministic results, so a given test number always produces the same approval or decline response.
The gateway routes test numbers to an internal simulator instead of the card networks. The simulator reads the number and returns a scripted response.
Payment processors publish their own test card numbers in developer documentation, along with numbers that trigger specific decline codes. These cards use reserved ranges and are rejected by the live network if anyone tries to run them outside test mode. You should never need to source card data from anywhere else to test a payment integration.
Credentials, endpoints, and webhook signing secrets all differ between the two environments. Sandbox limits and rate caps are also looser, which is why load and latency testing results do not carry over directly. Real cardholder data must never be copied into a sandbox, because that widens your PCI DSS scope and violates card network rules.
Fraudsters abuse live checkout pages by scripting thousands of small authorization attempts with stolen card numbers to learn which ones still work. Merchants see the damage as spikes in declines, authorization fees, and chargebacks, plus support tickets from confused cardholders. This attack pattern is why a real checkout page behaves nothing like a controlled test environment.
Defenses combine rate limiting, bot detection, and tighter authorization rules.
Using gateway-issued test numbers inside a sandbox is legal and routine. Entering real card numbers that belong to someone else, including through a checker or validation tool, is not: in the United States it can violate the Computer Fraud and Abuse Act, wire fraud statutes, and state identity theft laws. PCI DSS also forbids storing sensitive authentication data such as the CVV after authorization.
No. Test numbers are recognized only by the sandbox and are declined by the live network.
No. A sandbox never contacts an issuer, so it cannot confirm anything about a real account.