BIN Lookup: Free BIN & IIN Checker

Enter the first 6 to 8 digits of a payment card, the Bank Identification Number (BIN or IIN), to see its card network, type and level, issuing bank and country. SlayerChk checks them against 374,688 known BIN ranges, and the same BIN database is available as a free JSON API.

BIN ranges374,688
Data updated27 Sept 2025
APIFree, no key

Check a BIN or IIN

Six digits are enough to identify an issuer. A full card number adds a Luhn and length check, and is never stored.

Luhn checksumNot applicable
LengthNot applicable
On fileNot applicable

A bare 6-digit BIN carries no check digit, so Luhn and length read as not applicable until you paste a full number. Full numbers are sent in the request body, never in a URL, and are never stored or logged.

Enter at least 6 digits to resolve an issuer.
BIN ranges374,688
Data updated27 Sept 2025
APIFree, no key
curl -s "https://slayerchk.com/v1/bins/414720" | jq
Resolve a BIN with a known issuer to map its other ranges.

Browse the BIN list by country, bank and scheme

Combine any filters; matching ignores case. Country takes alpha-2 or alpha-3, bank matches part of a name. Select a row to load it above, or open its BIN, bank or country page.

BIN database coverage

Exact counts from the full dataset.

About the data

The SlayerChk BIN database holds 374,688 BIN ranges, one record per 6-digit prefix, last updated 27 Sept 2025. It is compiled from publicly available BIN lists, not supplied by the card networks or issuers.

Banks merge, rebrand and reissue cards, so some records are incomplete or out of date. Treat a result as informational and confirm anything important with the issuer.

Spotted a wrong record? Email [email protected] with the BIN and the correct issuer, scheme or country.

Free BIN lookup API (JSON, no key)

JSON over HTTPS, no key required. Drop-in compatible response formats are included alongside the native one.

GET/v1/bins/{bin}Native format. Adds every valid length, the detected scheme and a validation block.
POST/v1/bins/batchUp to 100 BINs per call. Order is preserved, duplicates are resolved once.
GET/lookup/{bin}Drop-in compatible format. Always 200, with success false on a miss.
GET/compat/{bin}Strict drop-in compatible format. Returns a real 404 on a miss.
GET/v1/searchFilter by country, scheme, type, bank and category, with sorting and pages.
GET/v1/statsDataset totals plus the largest schemes, countries and issuers.
GET/v1/countriesEvery country code in the dataset, with a range count.
GET/v1/schemesEvery card scheme in the dataset, with a range count.
GET/v1/categoriesEvery product tier in the dataset, with a range count.
GET/healthService status and record count.

How BIN lookup works

The first digit of a card number is the Major Industry Identifier: 3 for travel and entertainment cards, 4 and 5 for banking and finance, 6 for merchandising and banking. The first 6 to 8 digits form the BIN, called the Issuer Identification Number (IIN) in ISO/IEC 7812. A BIN lookup matches those digits against a table of known ranges to find the network, issuer, card type and country. The digits after the BIN identify the account, and the last one is a Luhn check digit.

Card network prefixes

NetworkStarts withCard length
Visa413, 16, 19
Mastercard51–55, 2221–272016
American Express34, 3715
Discover6011, 644–649, 6516–19
JCB3528–358916–19
UnionPay6216–19
Diners Club International300–305, 3095, 36, 38, 3914–19
Maestro5018, 5020, 5038, 5893, 6304, 6759, 6761–676312–19
Mir2200–220416–19
RuPay60, 6521–6522, 81, 82, 50816

The move to 8-digit BINs

ISO/IEC 7812-1:2017 lengthened the IIN from 6 to 8 digits because the 6-digit space was running out. Visa and Mastercard required issuers and processors to support 8-digit BINs by April 2022. Card numbers did not get longer, so one 6-digit prefix can now be split between several issuers. SlayerChk accepts 6 to 8 digits and matches on the first 6, the width of its source data.

What the fields mean

Scheme
The card network that routes the payment: Visa, Mastercard, American Express and so on.
Type
Debit, credit or charge card. A charge card has to be paid off in full each month.
Category
The product tier the issuer sells the card as, such as Classic, Gold, Platinum, Business or Prepaid.
Issuer
The bank or institution that issued the card, with its phone number and website where the source lists them.
Country
Where the card was issued, as ISO 3166-1 alpha-2 and alpha-3 codes, with that country's currency.
Valid lengths
The card number lengths the network allows for this prefix.
Luhn check
The checksum in the last digit of a full card number. It catches typos; it says nothing about whether a card exists.

Typical uses: routing a payment, flagging a card whose issuing country differs from the buyer's, applying surcharge rules by card type, and showing the right card logo at checkout.

BIN lookup FAQ

What is a BIN or IIN?

A Bank Identification Number (BIN), also called an Issuer Identification Number (IIN), is the first 6 to 8 digits of a payment card number. It identifies the card network, the issuing bank, the card type and the country where the card was issued.

How accurate is the BIN data?

Results come from a compiled table of issuer ranges. BIN assignments change over time as banks merge, rebrand and reissue cards, so some entries may be incomplete or out of date. Treat results as informational and confirm anything important with the card issuer.

Is SlayerChk free to use?

Yes. The lookup on this page and the JSON API are free to use, with no account or API key required. Fair-use rate limits apply.

Do you store the card numbers I enter?

No. Lookups are processed in memory and card numbers are not stored. A full card number is sent in the request body rather than the URL, and is masked before anything is written to a log. Only the first 6 to 8 digits are needed for a lookup.

Does the API have rate limits?

Yes. Requests are rate limited per IP address to keep the service fast for everyone. If you exceed the limit, the API responds with HTTP 429 Too Many Requests; wait a moment and try again.

How do I use the BIN lookup API?

Send a GET request to https://slayerchk.com/v1/bins/{bin} with the first 6 to 8 digits of a card, for example https://slayerchk.com/v1/bins/414720. The response is JSON with the scheme, type, category, issuing bank and country. Full documentation is available at https://slayerchk.com/docs.