CVV Test for Security: How to Validate Card Verification Correctly
A CVV test checks that your payment stack validates the card verification value at authorization and never stores it. Run it in a sandbox, not with live cards.
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 BIN lookup test checks whether the first six to eight digits of a card number resolve to the correct issuing bank, card brand, funding type, and country. Payment teams run it to catch stale or mismatched BIN table data before that data reaches the authorization stream. It is a data quality check on static range records, not a way to test whether a card is live, funded, or safe to charge.
A BIN lookup returns the attributes tied to a registered issuer range: brand, issuer name, card type (credit, debit, prepaid), issuer country, and sometimes currency. The test compares those returned values against what your own systems recorded at capture.
Since the shift to eight-digit issuer identification numbers, legacy six-digit tables return fewer matches. A test that uses six-digit lookups against modern ranges will report false mismatches.
Issuer portfolios migrate between banks, prepaid programs open and close ranges, and brands assign new eight-digit blocks. Issuer names also change after mergers, which breaks exact-match string comparisons.
Most teams refresh BIN tables monthly and after every brand range release. Anything older than a quarter will drift on prepaid and debit ranges first.
CVV and address verification checks happen at authorization, when the issuer responds to a live request. A BIN lookup reads static range data and cannot confirm that a card is active, has funds, or belongs to the person presenting it.
Using BIN lookups to screen or rank card numbers you do not own is card fraud, and it is prosecuted as such in the US. Legitimate uses are merchant routing, fraud scoring, and reconciliation on transactions you processed.
No. A zero-dollar or account verification request goes to the issuer and returns a live response. A BIN lookup never contacts the issuer.
Monthly is the practical baseline. Refresh immediately when a brand announces new ranges or when your decline patterns shift on a specific portfolio.
BIN data alone is not cardholder data, but the systems around it often are. Keep test datasets masked, restrict access, and never store sensitive authentication data alongside BIN records.