IIN/BIN Checker & BIN Lookup API
Six digits, and the bank behind them.
A BIN resolves to a scheme, a funding type, a country and an issuing institution — with a reason attached to every check and not a digit more than we need.
six to eight digits is the entire input
BIN lookup checks
Four stages run against every range. The shape check resolves locally, and the provider dataset answers the other three.
Normalize & shape
Whitespace stripped and the length checked against 6-8 digits. No network call. Anything shorter or longer stops here.
Range lookup
The BIN is matched against the provider's issuing-range dataset. A miss is reported as unlisted — never as a counterfeit card.
Scheme, funding & issuer
The network, the brand, whether the range is credit, debit or prepaid, the country and currency, and the institution that issued it — with its website and phone.
Risk flags & verdict
Prepaid, commercial, and any scheme or funding the dataset cannot resolve are treated as risky. Everything else lands deliverable. Every check ships with the reason that produced it.
Only the range lookup leaves the building; the shape check runs locally.
Input to BIN — stages 01–02, drawn
Whitespace comes off, the length is checked, and the range is matched against the dataset. The rejected input underneath never becomes a request — that is the whole point of doing this locally.
The range lookup, drawn
One POST carries the partial number; the dataset answers with the scheme, the funding, the country and the institution — or tells us it does not hold the range.
the miss — same call, unlisted range
a miss is dataset coverage, not a verdict on the card
This is a dataset lookup. We never send a full card number and nothing is ever charged or authorised.
Everything the range returns.
The profile is the product. Prepaid and commercial are the two range-level flags that carry the verdict to risky — everything else is context you can use.
the range
424671
Six digits, resolved against the issuing-range dataset. This is the whole input — nothing else about the card was sent, and nothing else was needed.
- scheme
- visa
- brand
- visa
- funding
- credit
- category
- classic
- country
- US · United States
- currency
- USD
- issuer
- Northbridge Bank
- website
- northbridge.example
- phone
- +1 415 555 0100
details · 200
{"bin": "424671","found": true,"scheme": "visa","funding": "credit","brand": "visa","category": "classic","countryCode": "US","countryName": "United States","issuerName": "Northbridge Bank","issuerWebsite": "https://northbridge.example","issuerPhone": "+14155550100","currency": "USD","prepaid": false,"commercial": false,"longerBinAvailable": false}
Field map · hover to trace
- binstring
The normalized 6-8 digit issuing range.
- foundboolean
False on the miss path — then the response carries one check only.
- schemestring
The network the range is allocated to.
- fundingstring
credit · debit · prepaid · unknown. Unknown lands risky.
- brandstring
The brand the network reports for the range.
- categorystring
The product class within that brand.
- countryCodestring
ISO country the range is issued in.
- countryNamestring
The same country, spelled out.
- issuerNamestring
The institution the range was allocated to.
- issuerWebsitestring
The institution's site, as the dataset holds it.
- issuerPhonestring
The institution's phone, as the dataset holds it.
- currencystring
The currency the range is issued in.
- prepaidbooleandrives the risk verdict
Range-level flag. True lands risky.
- commercialbooleandrives the risk verdict
Range-level flag. True lands risky.
- longerBinAvailableboolean
A longer prefix exists for a sharper match — that is the precision check.
Three verdicts, in practice.
There is no fourth state here: a BIN is either in the dataset or it is not, and the flags decide the rest. Illustrative rows, with the check that decided each one.
| BIN | Brand | Funding | State | Score | Deciding check |
|---|---|---|---|---|---|
| 424671 | visa | credit | deliverable | 92 | dataset |
| 506099 | mastercard | debit | deliverable | 92 | issuer |
| 424672 | visa | prepaid | risky | 62 | risk |
| 400000 | visa | unknown | risky | 62 | risk |
| 999999 | — | — | undeliverable | 12 | dataset |
| 42467100 | — | — | undeliverable | 12 | dataset |
Sample rows for illustration — the shape is real, the rows are not. A BIN identifies a range, not a person or an account.
Where that number comes from
Three fixed bands, mapped straight from the dataset’s flags: 12 undeliverable, 62 risky, 92 deliverable. There is nothing to reverse-engineer into a fraud score, so we do not draw one.
Three fixed bands mapped from the dataset’s signals — not a weighted sum.
The checks on that row
- Dataset matchpass
- Issuerpass
- Risk profilepass
Precision is emitted only when a longer BIN prefix is available — this response had none, so the check is not here.
One call, every reason.
Every verdict ships with the checks that produced it, each carrying the reason string the engine returned. A range the dataset does not hold comes back with a single failed check and nothing invented to fill the space.
BIN 424671 was found in the provider issuing-range dataset.
reason · BIN 424671 found in provider dataset.
A Precision check appears only when the provider reports a longer BIN prefix — this response reported none, so there is no fourth row. A range the dataset does not hold returns the Dataset match check alone, failed, with nothing invented beside it.
What is an IIN/BIN checker?
An IIN/BIN checker identifies information associated with the first six to eight digits of a payment card number, commonly called the Bank Identification Number or BIN. MultiValidator uses the BIN to look up information such as card scheme, funding type, brand, country, currency, and issuing institution.
A BIN identifies an issuing range, not an individual card or account. MultiValidator only needs the BIN range for the lookup and never requires the full card number.
what that covers
- A range, not an account — every card issued from those digits shares them.
- Scheme, brand, funding, category, country and currency, as far as the dataset holds them.
- The issuing institution, with its website and phone when the provider returns them.
How BIN lookup works
Four steps, in order. The shape check answers locally; the provider dataset answers the rest.
Normalize the BIN
MultiValidator removes whitespace and validates that the input contains a supported 6–8 digit BIN range before making a lookup.
Match the issuing range
The BIN is matched against the provider's issuing-range dataset to determine whether the range is listed.
Retrieve BIN information
When a match is found, the lookup can return the card scheme, brand, funding type, category, country, currency, and issuing institution.
Return the BIN result
MultiValidator combines the available dataset and range-level signals into a clear verdict, score, and reason so the result can be understood and audited.
What information does a BIN lookup provide?
Everything below can come back on one lookup, depending on what the provider holds for that range. The field names are the API’s, so you can map them straight onto your own model.
Card scheme
Identifies the payment network associated with the issuing range.
Card brand
Returns the brand associated with the BIN when provided by the dataset.
Funding type
Identifies whether the range is associated with credit, debit, prepaid, or unknown funding.
Card category
Provides the product category associated with the issuing range when available.
Issuing country
Returns the country associated with the BIN range.
Currency
Identifies the currency associated with the issuing range.
Issuing institution
Returns the issuer name and, when available, its website and phone information.
BIN precision
Indicates when a longer BIN prefix is available for a more precise issuing-range match.
Fields the dataset cannot resolve come back unknown rather than guessed — an unlisted range returns no profile at all.
IIN/BIN checker use cases
The same lookup, pointed at the places payment data enters your systems — and at the ranges you already hold.
Payment risk screening
Use BIN-level information as one input when evaluating payment and transaction risk.
Card type identification
Identify whether a card range is associated with credit, debit, prepaid, or other supported funding types.
Payment form enrichment
Use BIN information to enrich checkout or payment workflows with card network, country, currency, and issuer context.
Fraud prevention workflows
Combine BIN attributes with other verification and fraud signals when building payment-risk workflows.
Customer and transaction analytics
Use BIN metadata to understand card mix, issuing countries, funding types, and payment patterns.
Payment data validation
Validate and normalize BIN ranges before using them in payment-related systems or internal datasets.
BIN data is one input, never a verdict on a person: it cannot tell you whether a transaction is fraudulent. Pairs naturally with phone validation and email validation when you screen more than the card.
IIN/BIN checker vs. card validation
An IIN/BIN checker identifies information associated with a card’s issuing range. It can return the network, funding type, country, currency, and issuer, but it does not verify whether an individual card is active, whether the cardholder owns it, or whether a transaction will be authorized.
Card validation and payment authorization are different processes. BIN data should be treated as range-level information and combined with other payment signals when making transaction decisions.
BIN lookup
Identifies information associated with a card's issuing range — the network, funding type, country, currency and issuer behind those digits.
- Card scheme and brand
- Funding type and category
- Country and currency
- Issuing institution
Card validation & authorization
Answers whether an individual card is active, whether the cardholder owns it, and whether a transaction will be authorized. None of that is a BIN lookup, and none of it runs here.
- Card active status
- Cardholder ownership
- Transaction authorization
- Not performed by MultiValidator
MultiValidator performs neither validation of the card itself nor authorization, and it never charges the card.
BIN vs. IIN: what’s the difference?
BIN traditionally refers to the Bank Identification Number used to identify a card issuing range. The term IIN, or Issuer Identification Number, is also used for issuer-identification digits in payment-card numbering systems.
For applications, MultiValidator accepts the supported BIN range and resolves it against the provider’s issuing-range dataset.
BIN lookup API for developers
Integrate BIN lookup directly into your application with the MultiValidator API. Submit a supported BIN range and receive structured information about the scheme, funding type, card brand, category, country, currency, issuing institution, risk flags, and lookup status.
Use the API in payment forms, checkout workflows, transaction enrichment, fraud-prevention pipelines, customer analytics, and internal payment-data systems.
For the whole contract — rate limits, error codes and bulk — read the API documentation. For lists, see bulk BIN lookup.
A BIN lookup is charged at the current per-lookup rate configured by the administrator. A provider failure is refunded, so a failed request never charges a credit.
$ curl -X POST https://api.multivalidator.io/api/v1/verify \ -H "Authorization: Bearer mv_<64 hex>" \ -H "Content-Type: application/json" \ -d '{"kind": "bin", "bin": "424671"}'{ "success": true, "data": { "kind": "bin", "target": "424671", "status": "deliverable", "classification": "safe", "score": 92, "is_valid": true }, "credits": { "used": 1, "remaining": 418, "quality": "standard" }, "kind": "bin", "target": "424671", "state": "deliverable", "qualityScore": 92, "latencyMs": 96, "checks": [ { "key": "dataset", "label": "Dataset match", "outcome": "pass", "reason": "BIN 424671 found in provider dataset." }, { "key": "issuer", "label": "Issuer", "outcome": "pass", "reason": "Issuer: Northbridge Bank." }, { "key": "risk", "label": "Risk profile", "outcome": "pass", "reason": "BIN has no elevated risk flags in provider metadata." } ], "provider": "multivalidator", "details": { "provider": "multivalidator", "classification": "safe", "bin": "424671", "found": true, "notFoundReason": null, "scheme": "visa", "funding": "credit", "brand": "visa", "category": "classic", "countryCode": "US", "countryName": "United States", "issuerName": "Northbridge Bank", "issuerWebsite": "https://northbridge.example", "issuerPhone": "+14155550100", "currency": "USD", "prepaid": false, "commercial": false, "longerBinAvailable": false }, "creditsRemaining": 417.75, "creditsConsumed": 0.25}$ curl -X POST https://api.multivalidator.io/api/v1/verify \ -H "Authorization: Bearer mv_<64 hex>" \ -H "Content-Type: application/json" \ -d '{"kind": "bin", "bin": "999999"}'{ "success": true, "data": { "kind": "bin", "target": "999999", "status": "undeliverable", "classification": "invalid", "score": 12, "is_valid": false }, "credits": { "used": 1, "remaining": 417, "quality": "standard" }, "kind": "bin", "target": "999999", "state": "undeliverable", "qualityScore": 12, "latencyMs": 88, "checks": [ { "key": "dataset", "label": "Dataset match", "outcome": "fail", "reason": "BIN not found in provider dataset." } ], "provider": "multivalidator", "details": { "provider": "multivalidator", "classification": "invalid", "bin": "999999", "found": false, "notFoundReason": "BIN not found in provider dataset." }, "creditsRemaining": 417.75, "creditsConsumed": 0.25}
| Status | Code | When |
|---|---|---|
| 400 | INVALID_REQUEST | kind must be one of: email, phone, whatsapp, bin. |
| 400 | INVALID_REQUEST | bin must be 6 to 8 digits. |
| 401 | AUTH_REQUIRED | API key required. Send Authorization: Bearer mv_... to use this endpoint. |
| 402 | INSUFFICIENT_CREDITS | Insufficient credits; creditsRemaining comes back in details. |
| 429 | RATE_LIMIT_EXCEEDED | Carries an X-RateLimit-Reset header. |
| 429 | DAILY_LIMIT_EXCEEDED | Your plan's daily BIN cap is reached. Details carry limit, used, remaining and resetsAt; the response carries an X-DailyLimit-Reset header. |
| 502 / 503 | VERIFICATION_FAILED | Provider rejected the key, provider billing is inactive, or the provider rate-limited us. |
Bulk BIN lookup.
Ranges go in as a list over the API, or as a spreadsheet in the dashboard. Jobs for email are queued; phone, WhatsApp and BIN payloads come back completed, inline.
Process multiple BIN ranges through the API or dashboard when you need to enrich or validate larger payment-data sets. MultiValidator supports bulk BIN lookup while returning structured results for each range.
json
$ curl -X POST https://api.multivalidator.io/api/v1/bulk \ -H "Authorization: Bearer mv_<64 hex>" \ -H "Content-Type: application/json" \ -d '{"kind": "bin", "bins": ["424671", "506099"]}'
csv, through the dashboard
- The upload auto-detects a BIN column — header hints are
bin,iinandcard. - Values of 6 to 16 digits are accepted and truncated to the first 8, then de-duplicated.
- Rows that do not match are skipped, not failed — nothing is sent for a cell we cannot read as a range.
Known limits
A BIN identifies the issuing range, not the account. Every card issued from that range shares these digits — we never need the rest of the number.
Prepaid and commercial are range-level flags, not a fraud verdict. Plenty of prepaid cards are perfectly good.
Coverage is the dataset. A miss means the range is unlisted, not that the card is fake — read it as unknown coverage.
A longer BIN is sometimes available for a sharper match, and we say so rather than guessing. A range match does not prove a card is genuine or active — only that the issuing range is listed. We never request a full card number and we do not run authorisation checks.
IIN/BIN checker FAQ.
The questions this lookup gets asked most — answered the same way the API answers them.
An IIN/BIN checker looks up information associated with the issuing range represented by the first six to eight digits of a payment card number.
Stop mailing ghosts.
Start with free credits. No card, no call, no “book a demo”.