BIN Lookup: Identify Card Network from IIN Digits

How to use the credit card bin lookup

1. Enter the first six to eight digits of the payment card into the input field.
2. The tool strips spaces and hyphens automatically.
3. Review the identified card network, expected card length and Luhn validity.
4. Use the result for development, testing or routing logic.

How IIN ranges work

The Issuer Identification Number (IIN), also called the Bank Identification Number (BIN), occupies the first six to eight digits of a payment card. ISO/IEC 7812 defines this structure. Each card network is assigned specific leading digit ranges. For example, Visa cards always start with 4, while Mastercard uses 51 through 55 and 2221 through 2720.

This bin lookup matches your input against those published ranges. It does not query a database of real issuers, so it cannot tell you which bank issued the card. It only identifies the network level.

The Luhn algorithm explained

The Luhn algorithm is a simple checksum formula used to validate identification numbers. To compute it, start from the rightmost digit (the check digit) and move left, doubling every second digit. If doubling produces a number greater than 9, subtract 9. Sum all the digits. If the total modulo 10 equals zero, the number passes the check.

For example, take 79927398713. Working right to left, the digits are 3, 1, 7, 8, 9, 3, 7, 2, 9, 9, 7. Double every second one (1, 8, 3, 2, 9) to get 2, 16, 6, 4, 18, and subtract 9 from those above 9 to get 7 and 9. The digits to add are then 3, 2, 7, 7, 9, 6, 7, 4, 9, 9, 7, which sum to 70. Since 70 mod 10 is 0, the number passes.

A Luhn check only makes sense for a complete card number. When you enter fewer than 12 digits, this tool shows "Not checked" for the Luhn row because the remaining digits, including the check digit, decide the final result. A passing Luhn check also does not mean the account exists or has funds.

Published network ranges

The following table lists the IIN ranges this tool checks. They are the commonly published prefixes for each network, and issuers can change or add ranges over time.

The ranges above do not overlap, so the order of the checks does not change the result. Other networks, such as RuPay, Elo, Troy, Verve, Dankort and UATP, are not covered and show as Unknown. Co-branded ranges can also be shared between networks: for example, Discover cards are also issued in the UnionPay 62 range.

Practical use cases for bin lookup

Developers building checkout flows use bin lookup to display the correct card logo before the user finishes typing. This improves the user experience and reduces form errors. Payment gateways also route transactions based on the network identified by the IIN.

Testing environments rely on known test card numbers. By checking the IIN, you can confirm that your test suite covers all required networks. If you work with physical product identifiers rather than payment cards, tools like the VIN decoder or GTIN validator serve a similar validation purpose for different numbering systems.

Common mistakes and edge cases

Entering fewer than six digits will not produce a reliable match because most networks require at least six digits for identification. Some newer assignments use eight-digit IINs per the updated ISO 7812 standard, so an eight-digit input gives the most accurate result.

Do not confuse this tool with a credit card validator. A valid Luhn check on a full number does not mean the account exists or has funds. Similarly, passing a complete card number into this tool works, but only the leading digits matter for network identification. Never enter real card numbers into any online tool during production work.

Worked examples