FAQ

We cover all countries globally, no exceptions.

We work on the data every day, and send out updates on a monthly basis.

Initial delivery will be done via email containing your unique https:// download links. By default, all subsequent updates will be done the same way. Alternative options are: FTP/SFTP upload to your location, JSON file output, customizable API link for the whole CSV file retrieval.

Every time you will get a full updated file, and will need to replace the old file with a new one.

Yes, sure. You can view both standard and extended structures here.

We work with major banks, online merchants and private contributors to ensure high data accuracy. Each record is cross-checked against multiple sources to ensure the data quality.

We don’t publish the client list to protect their privacy. We can provide client references to reputable parties. To obtain this information, specify the country and/or industry you are interested in.

We offer:

1) The Commercial License at $1500 with 12 months of updates included. You will get access to a full featured 6 digit BIN database.
You have the right to create your own software product using the database, and sell limited access to this service.

2) The Site License at $2900 with 24 months of updates. Includes all features of the Commercial License plus grants access to an
Extended BIN Database (7-9 digit BINs).

Yes, you will get them automatically every month regardless of the delivery method.

Yes, you can contact us anytime.

You can view the list of supported brands and card products.

About 45%/55%.

Updated numbers could be found at home page.

Sure.

Download  database sample (6 digit, CSV, simple format)

Download  database sample (6 digit, CSV, extended format)

Download  database sample (7-9 digit, CSV, extended format)

We offer CSV (comma delimited) format.

Yes, we support 7,8, and 9 digit BINs under the Full Extended License. As you may probably know, all merchants and financial institutions will soon be required to switch from
the old 6-digit BIN standard (your current subscription) to the new 8-digit BIN standard. This new BIN standard offers greater security and increased
accuracy over the old 6-digit standard.

As stated above, the new extended standard will soon replace the outdated 6 digit standard and the International Organization for Standardization (ISO) will
require that all financial institutions and merchants have the new BINs implemented by April 2022. Merchants who have not switched over by this deadline will see their chargeback fraud utilities lose accuracy and potentially fail completely. There are many tasks that merchants have to complete ahead of the deadline to ensure they are ready.

Official document by Visa:
https://usa.visa.com/dam/VCOM/global/support-legal/documents/numerics-initiative-simplified-requirements-for-eight-digit-issuing-bin-adoption.pdf

Official document by MasterCard:
https://globalrisk.mastercard.com/wp-content/uploads/2018/12/8-Digit-BIN-Expansion-Mandate-and-PCI-DSS-Impact.pdf

First look for 9 digits, if not found move down to 8 digits, etc until it’s found.

Approximate numbers:

6 digit file: 351000

7 digit file: 182000

8 digit file: 115000

9 digit file: 528000

Our data acquisition relies on a multi-tiered framework combining high-volume online merchant processors, direct relationships with major card-issuing banks, and a worldwide contributor network across over 210 countries. Furthermore, every single data entry goes through a rigorous validation engine that checks against multiple independent references to guarantee maximum accuracy.

Official scheme documents often involve prohibitive costs, incomplete fields, and inconsistent classifications. In contrast, ExactBins delivers daily refreshes, robust attributes including direct bank contacts, massive volume spanning over 3.5 million unique BINs across 17,000+ financial institutions, and cost-effective access.

We cover all countries globally, no exceptions.

We work on the data every day, and send out updates on a monthly basis.

Initial delivery will be done via email containing your unique https:// download links. By default, all subsequent updates will be done the same way. Alternative options are: FTP/SFTP upload to your location, JSON file output, customizable API link for the whole CSV file retrieval.

Every time you will get a full updated file, and will need to replace the old file with a new one.

Yes, sure. You can view both standard and extended structures here.

We work with major banks, online merchants and private contributors to ensure high data accuracy. Each record is cross-checked against multiple sources to ensure the data quality.

We don’t publish the client list to protect their privacy. We can provide client references to reputable parties. To obtain this information, specify the country and/or industry you are interested in.

We offer:

1) The Commercial License at $1500 with 12 months of updates included. You will get access to a full featured 6 digit BIN database.
You have the right to create your own software product using the database, and sell limited access to this service.

2) The Site License at $2900 with 24 months of updates. Includes all features of the Commercial License plus grants access to an
Extended BIN Database (7-9 digit BINs).

Yes, you will get them automatically every month regardless of the delivery method.

Yes, you can contact us anytime.

You can view the list of supported brands and card products.

About 45%/55%.

Updated numbers could be found at home page.

Sure.

Download  database sample (6 digit, CSV, simple format)

Download  database sample (6 digit, CSV, extended format)

Download  database sample (7-9 digit, CSV, extended format)

We offer CSV (comma delimited) format.

Yes, we support 7,8, and 9 digit BINs under the Full Extended License. As you may probably know, all merchants and financial institutions will soon be required to switch from
the old 6-digit BIN standard (your current subscription) to the new 8-digit BIN standard. This new BIN standard offers greater security and increased
accuracy over the old 6-digit standard.

As stated above, the new extended standard will soon replace the outdated 6 digit standard and the International Organization for Standardization (ISO) will
require that all financial institutions and merchants have the new BINs implemented by April 2022. Merchants who have not switched over by this deadline will see their chargeback fraud utilities lose accuracy and potentially fail completely. There are many tasks that merchants have to complete ahead of the deadline to ensure they are ready.

Official document by Visa:
https://usa.visa.com/dam/VCOM/global/support-legal/documents/numerics-initiative-simplified-requirements-for-eight-digit-issuing-bin-adoption.pdf

Official document by MasterCard:
https://globalrisk.mastercard.com/wp-content/uploads/2018/12/8-Digit-BIN-Expansion-Mandate-and-PCI-DSS-Impact.pdf

First look for 9 digits, if not found move down to 8 digits, etc until it’s found.

Approximate numbers:

6 digit file: 351000

7 digit file: 182000

8 digit file: 115000

9 digit file: 528000

Our data acquisition relies on a multi-tiered framework combining high-volume online merchant processors, direct relationships with major card-issuing banks, and a worldwide contributor network across over 210 countries. Furthermore, every single data entry goes through a rigorous validation engine that checks against multiple independent references to guarantee maximum accuracy.

Official scheme documents often involve prohibitive costs, incomplete fields, and inconsistent classifications. In contrast, ExactBins delivers daily refreshes, robust attributes including direct bank contacts, massive volume spanning over 3.5 million unique BINs across 17,000+ financial institutions, and cost-effective access.

Yes, our practices are entirely legal and compliant. The dataset comprises technical ISO 7812 metadata with zero personal identifiable information (PII), meaning regulations like GDPR or CCPA do not apply. ExactBins legally holds intellectual property rights regarding the specific selection, arrangement, verification methods, and custom analytical flags built into the database.

Traditional range formats struggle with modern 8 to 11-digit fragmentation. Utilizing discrete individual rows enables faster, low-overhead exact-match database queries, eliminates awkward range-overlap maintenance, and avoids unallocated filler gaps.

We supply a powerful API built for automated synchronization and smooth technical integration. However, we purposely exclude an online web search interface to protect user privacy (keeping card details inside your local perimeter), minimize latency, and ensure uninterrupted availability.

Premium and Extended subscribers can unlock specialized parameters designed for deep risk management, such as a Virtual Card Identifier, Tokenized DPAN Intelligence, ISO 4217 Currency data, SWIFT/BIC routing codes, Durbin-regulated debit indicators, and detailed commercial sub-groupings.

Yes, we provide extensive coverage for prepaid products with an accuracy rate exceeding 99%. Our category column explicitly separates these entries into distinct classifications like Gift, Reloadable Prepaid, or Non-Reloadable Prepaid.

Yes, standard categories separate these variations, and we also feature an enterprise-grade Virtual Card Flag add-on driven by heuristic data analysis to pinpoint single-use or digital-only instruments that share space with regular plastic.

Yes, specialized database builds can include Business Identifier Codes (BIC/SWIFT) tied to each prefix, helping institutions streamline cross-border payment flows and strengthen automated onboarding or KYC validation.

Yes, our extended files track digital wallet token ranges (DPANs) from major providers like Apple Pay or Google Pay to return the underlying bank and country metadata. Note that Payment Account References (PAR) are non-numeric 30-character tokens rather than prefixes, meaning standard prefix lookups must rely directly on the first 8 to 11 digits of the DPAN.

Yes, payment schemes frequently share prefix blocks between physical cards and tokenized variants, meaning the same overarching data row applies to both.

Yes, systems should deploy a fallback routine: if a physical card lookup misses standard tables, query the token ranges, as the underlying country, brand, and type details remain entirely valid for the physical cards sharing that block.

Yes. While both fall under commercial tiers, our extended 8 to 11-digit depth lets systems differentiate small business accounts from large enterprise, government, or fleet allocations.

ISO 4217 currency parameters are offered as an add-on, reflecting the primary legal settlement currency of the issuing bank rather than dynamic multi-wallet sub-currencies managed internally by fintech applications.

Yes, standard attributes like card brand and category allow platforms to easily spot and isolate SMS-only instruments like Maestro or Visa Electron to appropriately handle tokenization rules.

Yes, deep 8 to 11-digit granularity isolates distinct institutional sub-categories—such as government GSA or public sector purchasing—enabling merchants to optimize interchange qualification.

Certain credit and debit products share identical 6-digit prefixes. Resolving this conflict requires longer 8 to 11-digit sets where the underlying sub-ranges are fully separated.

Absolutely; driven by ISO 7812 expansion mandates, extended BINs are heavily utilized globally. ExactBins offers native support up to 11 digits to minimize classification errors.

Yes, because sub-allocations exist, developers should build a longest-match-first strategy—checking 11 digits first, then stepping down through 10, 9, 8, and finally defaulting to the standard 6-digit prefix if needed.

That is a common misunderstanding; modern PCI DSS guidelines (such as FAQ #1091 and v4.0 standards) permit storing more than 6 digits for valid operational needs like fraud prevention, provided proper security measures like strong encryption or hashing are applied to protected fields.

Our data acquisition relies on a multi-tiered framework combining high-volume online merchant processors, direct relationships with major card-issuing banks, and a worldwide contributor network across over 210 countries. Furthermore, every single data entry goes through a rigorous validation engine that checks against multiple independent references to guarantee maximum accuracy.

Official scheme documents often involve prohibitive costs, incomplete fields, and inconsistent classifications. In contrast, ExactBins delivers daily refreshes, robust attributes including direct bank contacts, massive volume spanning over 3.5 million unique BINs across 17,000+ financial institutions, and cost-effective access.

Yes, our practices are entirely legal and compliant. The dataset comprises technical ISO 7812 metadata with zero personal identifiable information (PII), meaning regulations like GDPR or CCPA do not apply. ExactBins legally holds intellectual property rights regarding the specific selection, arrangement, verification methods, and custom analytical flags built into the database.

Traditional range formats struggle with modern 8 to 11-digit fragmentation. Utilizing discrete individual rows enables faster, low-overhead exact-match database queries, eliminates awkward range-overlap maintenance, and avoids unallocated filler gaps.

We supply a powerful API built for automated synchronization and smooth technical integration. However, we purposely exclude an online web search interface to protect user privacy (keeping card details inside your local perimeter), minimize latency, and ensure uninterrupted availability.

Premium and Extended subscribers can unlock specialized parameters designed for deep risk management, such as a Virtual Card Identifier, Tokenized DPAN Intelligence, ISO 4217 Currency data, SWIFT/BIC routing codes, Durbin-regulated debit indicators, and detailed commercial sub-groupings.

Yes, we provide extensive coverage for prepaid products with an accuracy rate exceeding 99%. Our category column explicitly separates these entries into distinct classifications like Gift, Reloadable Prepaid, or Non-Reloadable Prepaid.

Yes, standard categories separate these variations, and we also feature an enterprise-grade Virtual Card Flag add-on driven by heuristic data analysis to pinpoint single-use or digital-only instruments that share space with regular plastic.

Yes, specialized database builds can include Business Identifier Codes (BIC/SWIFT) tied to each prefix, helping institutions streamline cross-border payment flows and strengthen automated onboarding or KYC validation.

Yes, our extended files track digital wallet token ranges (DPANs) from major providers like Apple Pay or Google Pay to return the underlying bank and country metadata. Note that Payment Account References (PAR) are non-numeric 30-character tokens rather than prefixes, meaning standard prefix lookups must rely directly on the first 8 to 11 digits of the DPAN.

Yes, payment schemes frequently share prefix blocks between physical cards and tokenized variants, meaning the same overarching data row applies to both.

Yes, systems should deploy a fallback routine: if a physical card lookup misses standard tables, query the token ranges, as the underlying country, brand, and type details remain entirely valid for the physical cards sharing that block.

Yes. While both fall under commercial tiers, our extended 8 to 11-digit depth lets systems differentiate small business accounts from large enterprise, government, or fleet allocations.

ISO 4217 currency parameters are offered as an add-on, reflecting the primary legal settlement currency of the issuing bank rather than dynamic multi-wallet sub-currencies managed internally by fintech applications.

Yes, standard attributes like card brand and category allow platforms to easily spot and isolate SMS-only instruments like Maestro or Visa Electron to appropriately handle tokenization rules.

Yes, deep 8 to 11-digit granularity isolates distinct institutional sub-categories—such as government GSA or public sector purchasing—enabling merchants to optimize interchange qualification.

Certain credit and debit products share identical 6-digit prefixes. Resolving this conflict requires longer 8 to 11-digit sets where the underlying sub-ranges are fully separated.

Absolutely; driven by ISO 7812 expansion mandates, extended BINs are heavily utilized globally. ExactBins offers native support up to 11 digits to minimize classification errors.

Yes, because sub-allocations exist, developers should build a longest-match-first strategy—checking 11 digits first, then stepping down through 10, 9, 8, and finally defaulting to the standard 6-digit prefix if needed.

That is a common misunderstanding; modern PCI DSS guidelines (such as FAQ #1091 and v4.0 standards) permit storing more than 6 digits for valid operational needs like fraud prevention, provided proper security measures like strong encryption or hashing are applied to protected fields.