A credit card includes many items of metadata. Most important ones are card holder name, account number, security code CVV, and expiration date. The algorithms for confirming the combination of metadata are only known to the issuing firm and should be confirmed with them for the aim of a good payment. Anyway, it is helpful to understand whether a card number is actually valid prior to performing such further confirmation with the bank.

What does this app check?

It would perform SIX (6) different checks on the entered credit card number. The validity checks are Personal Account Number Check, Luhn Algorithm Check, Major Industry Identifier Check, Issuer Identification Number Check, Card Number Length Check, and Bank Identification Number (BIN) Check. The result would one by one show which test the credit card number passed if not all. Most of the official banks or online credit card generator sites have few to all of these rules in place, making sure the given credit card numbers are valid. Below explains each check:

Personal Account Number Check

The personal account is a group of digits starting with the 7th digit all the way to the one next to the last. The checksum is the last number. For example: a credit card of 371459635398431 has the personal account of 63539843 and the checksum of 1. The goal of this check is to extract out the account part and checksum digit. When facing a typical 16-digt CC number, system designers would input the first 15 digits into the Luhn algorithm. This would produce a single number result. This result should match the 16th digit of the provided card.

Luhn Algorithm Check

The validator is to confirm that the credit card number solves the Luhn algorithm

This algorithm was made by Hans Peter Luhn who is an IBM expert and is explained in the American patient no 2,950,048. It was filed on the 6th of January in 1954 and was settled on the 23rd of August in 1960. The Luhn Algorithm is also called Modulus 10, Mod 10

If you are a developer working with credit numbers, you can apply the Luhn formula to validate credit cards client-side or server-side using a big range of freely accessible code libraries and snippets. However, client-side validation is better in this case. Because catching a typo in a credit card checking with JavaScript Luhn algorithm is much quicker and more user-friendly. The wait to get rejected from the payment gateway as in server-side check may frustrate users.

How Luhn Algorithm validate a credit card number?

1. Drop the final digit from the input number.
2. Reverse the digits
3. Multiply the odd numbers by two. Each operation would produce a result. Subtract the result by nine if it is higher than nine.
4. Add up all the digits of old and new to get a final sum
5. Now perform Mod 10 on the above sum to get the checksum output. This output must match the last digit of the credit card number for the card itself to pass this check

As an example,

Major Industry Identifier Check

The first primary number of your credit card is the MII or Major Industry Identifier. It shows the category of the unit which released your credit card. Different MII numbers represent the following issuer categories.

Issuer Identification Number Check

The Issuer Identification Number Check (IIN), also called as the Bank Identification Number (BIN) requires to look at the first six, or more freshly with changes declared by the governing body, eight digits of the Primary Account Number (PAN). The PAN is the debit card or credit card number printed on the front of credit cards. 16 numbers but can be 10-19 numbers.

This check would verfiy which issuing brand the card belongs to. Each issuing network has certain prefix numbers as listed below in alphabetical order

** Mastercard prefixes have been in the range of 51-55 for a long time. The new range 2221-2720 have become effective since 2017. Many Mastercard payment cards starting with this new range have appeared in the market, expecting to see more of those in the coming years.

Card Number Length Check

Each issuer has different number length for their credit cards as below:

Bank Identification Number (BIN) Check

For this check, our app would look at the all first 6 to 8 digits. Then it would look up with a latest BIN database to produce any hidden information underneath, such as: Bank Name, Bank Address, Website, Contact, Issuer Details…

How to check it ?

By definitions above, examples of some GOOD inputs:

• 414301589470634 (16 digit VISA number)
• 4413 3015 8947 0634 (with spaces are ok)
• 512968489623125 (16 digit MASTERCARD number)

Examples of some BAD inputs with explanation:

• VISA Card (not a credit card number)
• 414301589474 (only 14 digit VISA)
• Toto tata (eeelll not a CC number, just some text)

Is This Credit Card Validator Secure to Use?

This service is free, secure, and 100% safe to check. The only danger is if any person is looking over your shoulders while you are on with it.

We cannot and would not access any data you add in the site, including your credit card numbers. All the computations are done in the discreet manner that your credit card number would remain in safety with you.

You can also contact us for details over how the validation works behind the scene. We can ensure that there is not any kind of saving data here. The server communication is 100% secure.

If you are still not sure, feel free to consult an expert about the safety of this so-good online credit card validator.

An Output Example of the CC Validator

Credit Card Number Input: 3725 489037 21007

Personal Account Number Check

The account number is 90372100. The checksum is 7

Luhn Algorithm Check

The input card number satified the legendary Luhn Algorithm

Major Industry Identifier Check

The primary number is 5. The card is under Financial and banking

Issuer Identification Number Check

The provided card number belongs to MasterCard

Card Number Length Check

The provided card number satisfied MasterCard 15 digits in length

BIN Check

If there is any BIN information. It will show