Choose from any of our gift cards to give to your loved ones
CVV Test Cases for Testing: Sandbox Numbers Only
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.
CVV test case design is the work of mapping every way a customer can reach the card security code field and proving your payment form handles each one correctly. You are not testing the code itself. You are testing your validation, your formatting, your error messages, and what your system does with that value after the authorization call. Get those right and you prevent a whole class of failed transactions and support tickets.
The CVV is a 3-digit code on the back of most cards. American Express prints a 4-digit code on the front and calls it CID. That one difference drives most of your test matrix, so settle it before you write any cases. Ask whether your gateway tokenizes the value, whether your form swaps length rules by card brand, and whether the field is even required for every card type you accept.
Brand detection switching mid-entry. Someone types a 15-digit Amex prefix, sees a 4-digit field, then edits the number into a Visa. Your form has to reset the length rule. Test that explicitly, because it is the case QA teams skip.
Paste and whitespace. Copying " 123 " out of a notes app is common. Trim it instead of rejecting it.
Unicode digits. Arabic-Indic or full-width numerals look like digits to a human and not to a regex. Decide whether you normalize or reject, then test both paths.
Wrong code on a valid card. The issuer declines it. Your UI should show a decline, not a field validation error. Those are different states and users get confused the moment you merge them.
Autofill. Browsers and password managers fill security codes inconsistently. Confirm a filled value lands in the right field and triggers the same validation as a typed one.
Never test with a real card. Use the sandbox numbers your processor publishes and rotate them per run so a stale token does not hide a failure. If the team keeps a shared sheet of test cards, give brand, code length, and expected result their own columns. A large share of the flaky results I have seen trace back to someone firing a 4-digit code at a card number that was never Amex.
Digit count and character class checks belong in a parameterized unit test. Error copy and layout shifts do not. Keep those manual or visual, since the failure mode is a message that is technically correct and unreadable on a phone.
One last rule: log the outcome, never the value. The code should not sit in application logs, analytics, or test fixtures. That is a compliance requirement, not a style preference.
