A BIN lookup test checks whether a bank identification number resolves to the correct card brand, issuing bank, country, and card type. It is a validation step, not proof that a card is valid or authorized for a transaction.
What a BIN lookup test verifies
A BIN, also called an issuer identification number, is the first six to eight digits of a payment card number. A lookup test sends those digits to a BIN database or an issuer API and compares the returned attributes against what you expect.
- Card brand, such as Visa, Mastercard, or American Express
- Issuing bank or financial institution
- Issuer country and, sometimes, region
- Card type: credit, debit, prepaid, or charge
- Product level, such as classic, gold, platinum, or commercial
Why merchants and fraud teams run BIN lookup tests
Testing helps you confirm that your BIN data source is accurate before you rely on it for routing, risk scoring, or checkout rules. A mismatch can cause false declines, incorrect interchange assumptions, or poor risk decisions. Regular tests also reveal when an issuer has changed its BIN ranges or when a database has stale records.
How to run a basic BIN lookup test
- Choose several known test BINs published by card networks or your acquirer.
- Send each BIN to your lookup provider and record the returned fields.
- Compare the results against the expected values for brand, issuer, and country.
- Test edge cases, including prepaid BINs, co-branded cards, and newly issued ranges.
- Document pass and fail results, then repeat the test on a schedule.
Common reasons a BIN lookup test fails
Failures usually come from data, not from the test itself. Shared BIN ranges can return a different issuer than expected. Co-branded cards may report one brand in the BIN and another on the card face. Prepaid programs often use ranges that change without notice. Formatting errors, such as leading spaces or truncated digits, also cause lookup failures.
Limits of BIN lookup testing
A BIN lookup test does not verify that a card is open, funded, or stolen. It does not replace address verification, CVV validation, or a real-time authorization request. BIN data can be outdated, and fraudsters can use valid BIN ranges on fabricated cards. Treat the test as one data quality check among several.
Good practices
- Use at least two BIN data sources and compare results.
- Refresh BIN tables regularly and log changes.
- Combine BIN checks with AVS, CVV validation, and issuer authentication.
- Never use BIN data as the only signal in a fraud decision.