Card Number Validation Platform: What It Checks and What It Cannot
A card number validation platform checks length, BIN/IIN prefix, and the Luhn check digit. It cannot confirm the card is open, funded, or authorized.
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.
Card number validation tools check whether a card number is well formed. They run the Luhn checksum, confirm the digit count, and match the leading digits to a card network. They do not confirm that the card exists, is active, or holds funds.
A validation tool treats a card number as data, not as an account. It tests format rules set by ISO/IEC 7812 and the card networks. If the number fails a rule, the tool flags it before a request reaches a payment processor.
Luhn, also called the modulus 10 algorithm, catches typos and single-digit errors. The last digit of every card number is a check digit computed from the digits before it. A tool running Luhn rejects 4111 1111 1111 1112 and accepts 4111 1111 1111 1111.
Card numbers run 12 to 19 digits, and most consumer cards use 16. The first six to eight digits form the issuer identification number, known in the industry as the BIN. That prefix tells the tool which network the number belongs to.
Expiry checks confirm that the month falls between 01 and 12 and that the year has not passed. Security code checks confirm 3 digits, or 4 digits for American Express. Both are format tests, not proof of anything.
A passing check says nothing about whether a card is open, funded, or approved for a given transaction. Only an authorization request through a payment processor answers those questions. Validation tools filter bad input. They are not fraud detection.
JavaScript libraries such as credit-card-type and the validator.js creditCard function run in the browser. They block typos before submit and return a true or false result plus a detected card type. Most are a few kilobytes and need no network call.
BIN services accept the first six to eight digits and return the network, card type (credit, debit, prepaid), issuing country, and sometimes the bank name. Pricing runs per lookup, and accuracy varies by region. Ranges shift as banks merge and launch new products.
Most payment processors publish test numbers that pass validation and trigger set responses, such as approve, decline, or insufficient funds. Use these in staging instead of live numbers. Test sets cover each network and each error path you need to handle.
A Luhn check is about ten lines of code in any language. Teams with tight latency budgets ship their own version and skip third-party calls. The algorithm is public domain, so there is no license issue.
Steps one through five run offline in milliseconds. Step six is the only one that touches the issuer, and it is the only one that confirms the card works.
Bad input costs money. A malformed number triggers a failed authorization, a support ticket, and a lost sale. Format checks cut that noise at the point of entry.
Validation also keeps junk out of logs and databases. PCI DSS does not require a Luhn check, but its scoping rules reward systems that hold less card data. Catching errors at the form means fewer bad records land in storage.
No. Validation is an offline format check that runs on your own systems. Authorization sends the number, expiry, and security code to the issuer through a processor and returns an approve or decline code.
Yes. The checksum follows a published formula, so matching digits prove nothing about the account. Luhn catches typos, and that is the extent of its job.
Most are not. Typing a live card number into a random website hands that number to an unknown operator. Use a library, or your processor's sandbox, instead.
Nothing. IIN is the ISO term and BIN is the industry term. Both describe the leading digits that identify the issuer and network.
They check the CVV format, which means 3 or 4 digits. Whether the code matches the card is a question only the issuer can answer during authorization.