How the BINSearchLookup Database Works

Where our BIN data comes from

The BIN/IIN standard is defined by ISO/IEC 7812, which governs how card networks assign identification numbers to issuing financial institutions. All BIN ranges trace back to official card network registrations.

Our database is built from multiple primary sources:

• Official card network BIN registration data from Visa, Mastercard, American Express, and Discover
• Direct issuer submissions and corrections submitted via [email protected]
• Automated reconciliation against public BIN registration records

Every BIN range in our database traces to a named issuing institution. We do not include inferred, estimated, or reverse-engineered data — only registered records from authoritative sources.

How we handle the 6-digit to 8-digit transition

In April 2022, the major card networks mandated a transition from 6-digit BINs to 8-digit IINs, driven by ISO/IEC 7812 revision. The reason: 6-digit BINs provided only ~64,000 unique combinations — insufficient for the volume of new card programs globally. 8-digit IINs support 16 million+ unique ranges.

Our API accepts both 6-digit and 8-digit inputs and returns the most precise match available. When you submit 8 digits, you receive the most granular result. When you submit 6 digits, we return the best match at that precision level.

Recommendation: always submit 8 digits when available for maximum accuracy.

How accuracy is measured

Our stated 99% accuracy figure reflects the percentage of BIN lookups that return the correct issuer, card brand, card type, and country — verified against official card network registration data.

Measurement methodology:

• Monthly automated audits of a random sample of active BIN ranges
• Cross-referenced against current source data from card networks
• A result is counted as accurate only if all four core fields match: issuer name, card brand, card type (credit/debit/prepaid), and issuing country
• Partial matches are not counted as accurate

This figure covers the active, in-use BIN ranges in our database. Newly issued BIN ranges not yet in a source feed are not included in the sample.

How the database is updated

Our database is updated daily through the following process:

1. Automated ingestion from official card network sources runs nightly
2. Changes are validated before deployment to production
3. Critical updates (e.g., large issuer launches, rebrands) are processed out-of-cycle within 24–48 hours
4. User-reported corrections are reviewed and deployed within 48 hours of verification

Typical lag time between a real-world BIN change and appearance in our API: 24 hours for scheduled updates, up to 48 hours for out-of-cycle events.

How to report an error

If you receive an incorrect result for a specific BIN, please send the BIN and the expected correct information to:

[email protected]

We verify all submissions against official source data. Confirmed corrections are deployed within 48 hours.

Known limitations

BIN lookup is a powerful tool for fraud prevention, but it has inherent constraints:

• Cannot identify stolen or compromised cards. The BIN tells you about the card program, not the individual card's fraud status.
• Cannot verify available balance. BIN lookup has no connection to the issuer's account system.
• Reflects card program at registration. If an issuer is acquired or rebrands after a card is issued, the BIN may temporarily reflect the old issuer until the next update cycle.
• Prepaid detection is probabilistic on some programs. Some card programs are classified as both debit and prepaid by the issuer. When the distinction is critical, apply additional verification.
• New BIN ranges have an ingestion lag. Brand-new ranges may not appear in the database until the next scheduled update cycle (typically within 24 hours).
• 6-digit submissions are less precise. Multiple 8-digit IIN ranges can share the same first 6 digits. Always submit 8 digits when available.