CVV Test Mode: What It Means and How to Test Card Flows Safely
CVV test mode lets you run card checkout tests with fake card numbers and fake CVV values in a payment sandbox. Here is how it works and where it stops.
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.
In the Braintree sandbox, pick one of the published test card numbers and put any three digits in the CVV field. 123 is the usual choice. American Express test cards take four digits, so 1234. The sandbox checks the format, not a real card, so the CVV value itself doesn't decide whether the test charge succeeds.
That trips people up. They search for "the" Braintree test CVV expecting a magic code, get a decline, and assume the CVV was wrong. Most of the time the problem is the card number, the expiration date, or CVV rules switched on in the account.
A CVV is generated by the issuer and tied to a real card. Sandbox card numbers aren't real cards, so no issuer generates anything. Braintree's test gateway accepts syntactically valid input and returns a simulated response.
Braintree's Testing reference includes a short set of CVV values that trigger specific responses, such as a mismatch or a "not verified" result. Those values only work when paired with the test card number listed next to them. Copy them from the docs rather than guessing.
Also check your account's CVV rules. If you turned on "CVV must match" in the control panel, a sandbox transaction with a mismatched CVV will decline even though it's test data. When an integration works on one merchant account and fails on another, look there first.
Never paste a live card number into the sandbox to "test" it. That's a compliance problem and a terms violation, and it gains you nothing. Test data only. And don't store a CVV after authorization in any environment.
Production works differently: the CVV goes to the issuer and the response depends on your rules. If you need to prove that path works end to end, run a small real transaction and void it the same day.