Steps to Locate a Genuine CVV Merchant
Discover the essential steps to identify a reliable CVV merchant for secure transactions.
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 sends the first six to eight digits of a card number to a reference database and checks whether the returned issuer data matches what your system holds. It confirms card brand, issuing bank, card type, and country of issue. It does not prove that a card is open, funded, or chargeable.
The Bank Identification Number is the leading segment of a payment card number. Those digits identify the institution that issued the card, not the person holding it. Under the ISO/IEC 7812 numbering scheme, the first digit marks the major industry and the next digits narrow down to the issuer.
A lookup test compares your stored value against a reference file that the card networks publish to processors and merchants. Results land in one of three states: match, mismatch, or no record. A mismatch on brand or card length points to dirty data in your own system. No record means the BIN sits outside the file you licensed, which happens with new or niche card programs.
Some providers add a prepaid flag, a reloadable flag, and an issuer contact block for chargeback work. The field set depends on the vendor and the network file behind it.
A typical response is a small JSON object. Fields include the BIN, scheme, type, brand, bank, country code, and a status value such as match or not found. Some vendors add a confidence score and a reason code for the lookup decision.
Your test should assert on the fields you act on and ignore the rest. Vendor extras change without notice, and a test that breaks when a field gets renamed wastes engineering time.
A test set built from live traffic finds real problems. Random numbers find nothing.
People mix these up, and the mix-up causes chargebacks. A BIN lookup reads public issuer data. A Luhn check proves the number passes a checksum, nothing more. An authorization request is the only step that tells you whether funds are available.
An authorization for one dollar, sometimes called a pre-auth, reaches the issuer and returns an approval code or a decline reason. That is the test that answers whether a card is live. A BIN lookup answers what kind of card it is, which is a different question with a different use.
BIN data feeds risk rules, not verdicts. A risk engine might score a transaction higher when the card country differs from the billing country, or when a prepaid card ships to an address that changed last week. Those signals stack with device data, velocity checks, and address verification.
At checkout, a BIN lookup also drives routing. Debit and prepaid cards often cost less to process than corporate charge cards, and some networks require different message formats. Reading the BIN at the top of the flow lets you pick the right path before you send the auth.
No. It confirms the issuer and the card type. Only an authorization request can tell you whether the account is open and funded.
Six is the traditional minimum. Eight digit BINs exist and carry more detail, so check what your provider indexes before you send anything.
Looking up public issuer data is legal in most markets. Rules on storing card numbers and running test authorizations come from your acquirer, the card networks, and local law. Read those before you build.
Match the schedule your provider publishes, which often means a refresh each month. Add one after any network bulletin that announces new or retired ranges.
The first six digits are not a full card number, but they are cardholder data when stored next to other fields. Keep them inside your PCI scope and follow the standard for encryption and access control.