---
title: "BIN Data and Coverage"
description: "Where BINLookupAPI BIN data comes from, what response fields mean, and how to report incorrect data."
section: "Support"
url: "https://binlookupapi.com/docs/support/data/"
markdown_url: "https://binlookupapi.com/docs/support/data.md"
---
# Data and coverage

This page explains the dataset. The field table for a response is in the [API reference](/docs/api-reference/#response-fields).

## Data sources

BINLookupAPI gets BIN data from third-party vendors, banks, and the card networks.

- The dataset has 3,289,919 BIN records.
- Records cover 231 countries.
- BIN length is 6 to 11 digits. 88.7% of records are longer than 6 digits.
- The data includes more than 80 card brands.
- The fields include the brand, the issuer, the card type, the category, the issuing country, and issuer contact details.

Small updates ship each week. A full refresh ships every 4 weeks and can remove withdrawn records. Each refresh is on the [changelog](/changelog/). Every plan, including the free tier, reads the same live dataset.

## Scheme, funding, and category

`scheme` is the card network:

| Value | Network |
|-------|---------|
| `visa` | Visa |
| `mastercard` | Mastercard |
| `amex` | American Express |
| `discover` | Discover |
| `jcb` | JCB |
| `unionpay` | UnionPay |
| `diners` | Diners Club |
| `unknown` | The network is not one of the values above. |

`funding` is the funding type:

| Value | Meaning |
|-------|---------|
| `credit` | A credit card or a charge card. |
| `debit` | A debit card. |
| `prepaid` | A prepaid card. |
| `unknown` | The funding type is not known. |

`category` is the product level. Examples are `CLASSIC`, `GOLD`, and `PLATINUM`. The value can be `null`.

## Prepaid and commercial

| Field | `true` | `false` |
|-------|--------|---------|
| `prepaid` | The card is a prepaid card. | The card is not a prepaid card. |
| `commercial` | The card is a business card or a corporate card. | The card is a personal card. |

## Currency

`currency` is the ISO 4217 code of the issuing country. The API does not read the currency from the card account.

- If a country changed its currency, the API returns the current code. Example: Germany returns `EUR`, not `DEM`.
- The field is `null` when the issuing country is not known.
- The currency of the issuing country is not always the currency of the card account.

## Issuer contact details

| Field | Meaning |
|-------|---------|
| `issuer.name` | The name of the bank. |
| `issuer.website` | The website of the bank. |
| `issuer.phone` | The customer service phone number, in international format when it is known. |

Each field can be `null`. Many issuers do not publish a website or a phone number.

## When a BIN is not found

The API returns `NOT_FOUND` when no record matches the BIN.

Common causes:

- The BIN is not in the data.
- The card range is new, and the weekly update does not contain it yet.
- The number is not a card range.

Check the digits, then send more digits, up to 11. Matching rules are in the [API reference](/docs/api-reference/#how-the-api-matches-a-bin). If the error continues, [report the BIN](#report-incorrect-data).

## Report incorrect data

If a lookup returns incorrect data, BINLookupAPI checks the sources and corrects the record.

Send an email to [support@binlookupapi.com](mailto:support@binlookupapi.com), or use the chat in the dashboard. Include:

- The BIN that you sent.
- The field that is incorrect.
- The correct value, if you know it.
- The source of the correct value, if you have one.

WARNING: Do not send a full card number in the report.

## Related pages

- [API reference](/docs/api-reference/)
- [Changelog](/changelog/)
- [Security](/docs/support/security/)
- [Contact](/docs/support/contact/)