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 Worldpay test CVV is a fake security code that pairs with a Worldpay test card number in the sandbox. Sandbox payments never reach a real bank, so the CVV is a placeholder that lets you submit the form and read the gateway response. Most Worldpay test cards accept 123 for Visa, Mastercard, and Discover, and 1234 for American Express.
Test values are public. They exist so developers can build checkout flows without touching live card data.
Worldpay publishes test card numbers on its developer documentation site, and each card notes the CVV that goes with it. The list covers the major brands plus a few cards built to return declines. You do not need to buy anything to get these values.
Common pairings look like this:
Card numbers and CVV values differ between Worldpay products. Access Worldpay (JSON), Hosted Payment Pages, and the older Worldpay Gateway each ship their own test data page, so use the one that matches your integration. Copy values from that page instead of a blog post. Old tables sit online for years and go stale.
In most Worldpay sandbox setups, the CVV response comes from the test card number, not from the digits in the field. That design lets you exercise each result code without hunting for a special value. As long as the field holds the right number of digits, the payment proceeds and the response reports what the issuer decided.
These codes appear in the response next to the authorization result. Log both values. A mismatch paired with an approval still needs a rule in your order flow.
If no test card returns a mismatch, your integration may not expose CVV checks at all. Some Worldpay configurations leave card verification to the acquirer, and the sandbox skips that step.
The sandbox enforces field length, and the same rule applies when you go live. Visa, Mastercard, and Discover use three digits. American Express uses four, and some debit brands vary by region.
A form that allows 12 digits for CVV will fail a live payment even if the sandbox let it pass. Set the max length by brand and mask the input in the UI.
No. Test environments exist to keep real card data out of the build and QA process. Typing live card numbers and CVVs into a sandbox can breach your merchant agreement and your PCI obligations.
PCI DSS bans storage of the CVV after authorization, in any environment. A spreadsheet of real security codes on a laptop is an incident waiting to happen. Use the published test values instead.
Buying or selling real CVV data is a crime in the US and most other countries. Test CVVs are free, public, and legal. There is no product to purchase here.
Use 123 for Visa, Mastercard, and Discover test cards, and 1234 for American Express. Check the test data page for your Worldpay product, since that list is the source of truth.
No. Test values stay valid while the sandbox runs, though Worldpay can retire or swap a test card. Recheck the docs after a major integration upgrade.
Result code U means the brand or the acquirer does not run CVV checks for that transaction type. Recurring and merchant-initiated flows skip CVV by design, and the sandbox copies that behavior.
Yes. Worldpay test data includes cards built to return a range of address and security code outcomes, so you can cover both-matching, both-failing, and the two mixed cases.