CVV Test Failure Issue Guide
Learn about CVV test failure issues and how to resolve them when trying to buy CVV codes.
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 CVV test that fails almost always points to one of three causes: the account is in live mode, the test card and CVV do not match the values your gateway expects, or the card brand needs a different CVV length. Confirm the test mode setting and the gateway's own test card list before you change anything else.
Most sandbox failures come from setup, not from the card itself. Work through the common causes below in order and you will find the fault fast.
With Stripe-style sandboxes, any 3-digit CVC works on standard test cards, and any 4 digits work on Amex. Values like 123, 456, or 000 all pass. Other gateways publish fixed card and CVV pairs, so a random number fails there.
Read the test data page for your own gateway. Do not copy values from a blog post, because gateway rules change and old posts stay online for years.
Check three things. First, the API key prefix: Stripe test keys start with sk_test_ and pk_test_. Second, the request host: sandbox endpoints differ from production ones. Third, the dashboard toggle that switches the whole account between test and live.
If a live key signs the request, every test card returns a decline no matter what CVV you send. This is the most common single cause of a CVV test that will not pass.
Error strings differ by gateway. Read the raw API response, not the message shown in the checkout UI, because the UI often collapses several codes into one generic text.
No. Stripe and several similar processors accept any 3-digit value on standard test cards. Others check against fixed values and return a mismatch when you send something else. A few ignore CVV checks in sandbox and never produce a CVV error at all.
American Express is the exception that catches most people. Its test cards need 4 digits, and a 3-digit value fails the format check before any authorization happens.
Compare API keys and account mode first. A teammate on a test key and you on a live key will see different results from the same card values. After that, compare the card brand, expiry, and CVV length, then the full request payload.
One more check: some gateways tie test behavior to the merchant account country or currency. A card that passes in USD can fail in EUR on the same sandbox.
Contact support after you have tested with the official card list, a valid test key, a future expiry, and a correct CVV length, and you still get a CVV error. Include the request ID, the timestamp, the card brand, the CVV length you sent, and the raw decline code.
Those details cut the back-and-forth. Support can trace the request and tell you whether the value hit a format rule or an issuer simulation.