A BIN lookup test checks if a tool or API returns the right bank identification number data for the first six to eight digits of a card. You send a set of known BINs through the tool and compare issuer, brand, country, and card type against a trusted reference file. Tools that fail these checks mislabel cards, which breaks routing rules and fraud scoring.
What Is a BIN Lookup Test?
A bank identification number, or BIN, is the leading part of a card number that points to the issuing bank and card brand. A BIN lookup test measures how well a lookup service maps those digits to accurate issuer details.
The test is a data quality check on the lookup layer itself. It is not a transaction and not an authorization.
What Should a BIN Lookup Return?
A solid response covers brand, issuer name, issuer country, card type, and card category.
- Card brand: Visa, Mastercard, American Express, Discover
- Issuing bank, plus the issuer's country when available
- Card type: credit, debit, or prepaid
- Card category: consumer, commercial, or government
- Currency tied to the issuing country
Missing fields matter as much as wrong fields. A tool that leaves card type blank forces your risk rules to guess.
How to Run a BIN Lookup Test
- Build a test set of 100 to 500 BINs. Cover major brands, several countries, and a mix of credit, debit, and prepaid ranges.
- Pull expected values from a source you trust, such as a brand-supplied range file.
- Send each BIN to the tool and record the full response.
- Compare field by field. Score matches on brand, country, card type, and issuer name.
- Log every failure with the BIN, the returned value, and the expected value.
- Re-run the same set after each vendor update or data refresh.
Run the set twice in a row at first. Unstable answers for the same BIN point to a caching or data version problem.
Test Cases That Expose Weak BIN Databases
- Prepaid ranges: many databases tag these as debit or leave them blank.
- Co-branded cards: a retail card riding a bank's BIN can confuse issuer matching.
- Newly issued ranges: brand and issuer updates reach vendors at different speeds.
- Bank mergers: old BINs keep working while the issuer name changes.
- Non-US issuers: country and currency fields fail most often here.
- Eight-digit BINs: some tools still read only the first six digits.
A tool that scores well on US credit cards can still fail on prepaid and non-US ranges. Weight your test set toward the traffic you process.
How to Score BIN Lookup Results
Score each field on its own, then combine the fields into a single match rate. A brand match carries more weight than an issuer name match, since issuer names vary in spelling across sources.
- 95% or higher on brand and card type: usable for routing rules
- 90% or higher on country and currency: usable for regional rules
- Below 85% on issuer name: expect manual review work
Treat those numbers as working targets, not vendor benchmarks. Set your own thresholds against the ranges you handle.
Where BIN Data Comes From
ISO/IEC 7812 sets the structure of the primary account number and the issuer identification number. Card brands publish range files that map those numbers to issuers, and aggregators combine those files with issuer records.
No single file stays current for long. Ranges get added, retired, and reassigned every month, so accuracy is a moving target.
What a BIN Lookup Cannot Do
A BIN identifies an issuing range. It says nothing about the person holding the card or the state of that account.
A BIN lookup cannot confirm that a card is open, funded, or valid. Only an authorization request through the payment network answers that, and it requires a merchant account and a legitimate transaction.
Anyone claiming a lookup tool can verify a live card account is describing something the data cannot support.
Compliance Notes for BIN Data
BIN data on its own sits outside most cardholder data rules because it is not a full account number. Once you store a full PAN, PCI DSS requirements apply to that system.
Keep test sets free of real account numbers. Use published range data, not card numbers pulled from production logs.
FAQ
How many digits does a BIN lookup need?
Six digits is the traditional minimum and eight digits is the modern standard. Eight digits give a sharper issuer match, but only if the tool supports them.
Is a BIN lookup test free?
Many vendors offer a free tier with rate limits and no bulk option. Paid plans add batch lookups and range files, which is what a real test set needs.
How often should you test a BIN lookup tool?
Test when you onboard the tool, after every data refresh, and once a quarter at minimum. Track the match rate over time to spot slow decay.
Can a BIN lookup tell you if a card is active?
No. BIN data describes the issuing range, not the account. Account status comes from an authorization response.