Course – LS – All

Get started with Spring and Spring Boot, through the Learn Spring course:


1. Introduction

In this article, we’ll learn how to identify a credit card type from a credit card number using regex.

Then, we’ll learn about the Luhn algorithm and how we can use this to check whether a credit card number is valid.

2. What Do the Leading Digits of a Card Number Tell Us?

The Primary Account Number (PAN) is another name for a credit card number.

The PAN is typically 16 digits long, although the number of digits can vary depending on the card issuer.

Currently, the Issuer Identification Number (IIN) is the first six digits of a PAN. It’s made up of one leading digit, followed by five digits.

It’s important to emphasize that this is the current situation because it’s likely to change in the future. Work began as early as 2015 to increase the IIN to the first eight digits.

Let’s see how we can determine the type of credit card just by looking at the IIN.

2.1. What Does the Leading Digit Tell Us?

The Major Industry Identifier is the first digit of a card number.

As the name suggests, we can look at the first digit of the card number to determine the industry to which the card belongs:

  • 1, 2 – Airlines (among others)
  • 3 – Travel and Entertainment
  • 4, 5 – Banking
  • 6 – Retail and Banking
  • 7 – Fuel Industry
  • 8 – Healthcare and Telecommunications
  • 9 – National Authorities
  • 0 – Other, Reserved for the future

Now, let’s take a look at how we’d identify the card issuer using the IIN.

2.2. How Do We Determine the Card Type From the IIN?

Since 1989, there has been an international standard defining how PANs should be allocated. The official register of IINs is not publicly available.

Fortunately, the majority of leading card issuers have widely known IIN ranges, so we can use regex to match the IIN to a card issuer.

Before we look at the regex, let’s remember that the list of IIN ranges is constantly changing.

If we’re writing an application to do this, we’ll need to consider how we plan to keep it up-to-date.

Alternatively, we could choose to import one of several available open source libraries, which contain more card types and are more thoroughly tested than we are likely to be able to manage ourselves. For example, using the Stripe API would mean card processing is managed for us.

2.3. Identifying the Card Issuer by Using Regex

Let’s try and identify a Visa card.

Visa card numbers start with a 4, so a simple regex to identify a Visa card would be ^4[0-9]{0,}$.

Note that in our example, we’ve not checked the length of the number. So far, we’ve assumed that the card number is valid, so the length is not something we’re validating here.

A similar pattern can be applied to identify other card issuers. For example, American Express cards begin with a 34 or a 37, so we can detect them using ^3[47][0-9]{0,}$.

Some card issuers have wider IIN ranges.

We find that Mastercard’s cards typically start with 51-55, however, within the last decade, they’ve introduced cards within the BIN range 222100-272099.

This gives us a regex of ^(5[1-5]|222[1-9]|22[3-9]|2[3-6]|27[01]|2720)[0-9]{0,}$.

We can use a similar pattern to identify cards from any card issuer whose range of IINs is known.

3. What Do the Middle Digits of a Card Number Tell Us?

The full PAN consists of 3 parts: the Issue Identification Number (IIN), an Individual Account Identification Number, and a checksum digit.

Between the IIN and the final digit, we have the Individual Account Identification Number.

The issuer defines what these middle digits mean, so they’ll have different meanings across different issuers.

They indicate information like the type of account linked to the card number.

4. What Does the Final Digit of a Card Number Tell Us?

The checksum digit is the final digit of a card number.

Helpfully, the checksum digit allows us to use the Luhn algorithm to quickly identify an invalid card number.

Hans Peter Luhn developed the Luhn algorithm in the late 1950s.

It’s used to generate every modern credit card number that we use today, ensuring that every card number shares a particular property.

The Luhn algorithm uses every digit in a card number, meaning we can use it to easily determine when a given card number is invalid – even if just a single digit was entered incorrectly.

Doing this means we can limit the number of unnecessary card processing functions. This is particularly important if we are charged per transaction we request!

Let’s see how we can use the Luhn algorithm in a Java application.

4.1. How Can We Use the Luhn Algorithm to Validate a Card Number?

Let’s run through the steps involved in using the Luhn algorithm to validate a given card number.

We’ll need to take the full credit card number, including the IIN.

Starting from the rightmost digit, we’ll add all the digits together, performing a special step for every second digit.

As we’re starting from the right, we’ll need to cycle backward through the card number, identifying every second digit:

for (int i = cardNumber.length() - 1; i >= 0; i--) {
    int digit = Integer.parseInt(cardNumber.substring(i, i + 1));

    if ((cardNumber.length() - i) % 2 == 0) {
        digit = doubleAndSumDigits(digit);

    sum += digit;

For every second digit, we must double it, and then sum the remaining digits.

Let’s see how this works for a short example of 4 digits (instead of the usual 16 digits) – let’s check whether the number 8642 would be a valid card number.

Starting with the rightmost digit, we’re going to double every second digit:

  • So for 2 (the first digit from the right), there is no change.
  • Next, we double the second digit, 4, to get 8.
  • After that, the third digit, 6, for which there is no change.
  • Lastly, we double the fourth digit, 8, to get 16.

If doubling the digit results in a two-digit number, then we need to do an extra step to get back down to a single digit – we’re going to add those digits together to produce a single-digit number, so for 16, this would be 1+6=7.

This step is the same as subtracting 9, so we can implement it in the code as:

private static int doubleAndSumDigits(int digit) {
    int ret = digit * 2;

    if (ret > 9) {
        ret = digit - 9;

    return ret;

Finally, to complete our example, let’s add each number together: 2 + 8 + 6 + 7 = 23.

If the result of the Luhn algorithm is divisible by 10, then the card number is possibly valid.

We’ll return this as the result of our check:

return sum % 10 == 0;

In our case, 23 is not divisible by 10, so 8642 is not a valid card number.

In our example, the final digit, 2, would be the checksum digit.

For real card numbers, the checksum digit is calculated using the Luhn algorithm.

For example, if we change the checksum digit to a 9 to give 8649, then the result of the Luhn algorithm is 30, which is divisible by 10, so 8649 would pass our Luhn check above.

4.2. Are There Any Limitations of the Luhn Algorithm?

Of course, our check does not imply that 8649 is definitely a valid card number. Although it passes our check, it may not have been issued as an actual card by the relevant card issuer.

The only way we can definitively confirm a card number is real is by asking the card issuer.

The Luhn algorithm still provides us with a useful way to confirm when a given card number is definitely not valid.

However, there are a few edge cases where our Luhn check would fail to detect a typo in a card number.

Fortunately, these edge cases are rare enough that we’re unlikely to ever come across one in real life.

Finally, the Luhn algorithm does not consider the length of the card number.

In reality, we know that even though 8649 passes our Luhn check, it is too short to be a real credit card number.

We can implement an extra check on the length of the card number but must remember that each card issuer’s numbers can vary in length.

5. Conclusion

In this article, we looked at what each part of the card number can tell us about a credit card account.

Firstly, we learned how to identify card issuers by matching regex patterns on the leading digits. Next, we saw that we would need issuer-specific information to understand what the middle of a card number tells us about the account. Finally, we looked at how the Luhn algorithm works and implemented some code to validate a given card number.

As always, the example project is available over on GitHub.

Course – LS – All

Get started with Spring and Spring Boot, through the Learn Spring course:

res – REST with Spring (eBook) (everywhere)
Inline Feedbacks
View all comments
Comments are open for 30 days after publishing a post. For any issues past this date, use the Contact form on the site.