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.
You cannot buy a Braintree test card, and you should not pay anyone for one. Braintree publishes its sandbox card numbers, CVV strings and AVS values for free in its developer documentation, and they work only inside a sandbox account. What you really need is a sandbox merchant account, a tokenization key or client token, and the current published test values. Anything sold as a "Braintree test card" is either a recycled copy of that free list or a real card number that will put you in PCI trouble.
A test card is a card number that passes the Luhn check and is routed by the sandbox to a simulated response instead of an issuer. Braintree's sandbox returns approvals, declines, CVV results and AVS results based on the number, the CVV, the postal code, and sometimes the amount. No money moves and no bank is contacted. You can reuse the same number as often as you like, which makes it practical for automated test suites and manual QA runs.
Stay inside the reserved test ranges. The set published by Braintree and the card brands includes Visa 4111111111111111, Mastercard 5555555555554444, American Express 378282246310005 and Discover 6011111111111117. These have no value, belong to no one, and are rejected by live gateways. Treat them as fixtures, not as credentials.
Any future date is accepted in the sandbox. Pick a fixed date several years out and store it in a fixture file, so your test suite does not start failing on a calendar boundary you forgot about.
Three digits for Visa, Mastercard and Discover, four for American Express. Braintree documents specific CVV and postal code values that force match, no match and not verified responses. Random digits often return a match in the default sandbox, but if your code branches on the response code, drive that branch with the documented values instead of hoping.
Some sandbox amounts trigger specific decline responses, and refund and settlement flows depend on what you authorize. Use small round numbers in the currency your merchant account is set up for, and verify amount-based triggers in the docs before you write assertions around them.
Test cards generate payment method nonces the same way live cards do. Vault a test card to exercise repeat transactions, and remember that sandbox vault records are separate from production and can be deleted freely.
No. They are published documentation, not a product. Anyone charging for them is reselling public information.
Usually the wrong environment, a missing or invalid tokenization key, an amount that triggers a decline, or a number that belongs to a different processor profile.
No. Live gateways reject test numbers immediately, and attempting it can flag the account.
Yes, and you should. Keep the numbers in environment variables or a fixture file so a documentation update is a one line change.
Budget nothing for test cards and spend your effort on coverage instead. Pull the current values from Braintree's developer documentation, build fixtures for approval, decline, CVV mismatch and AVS mismatch, and keep the whole set in the sandbox where it belongs.