Bulk BIN Verification & BIN Lookup
Every six digits, resolved.
Each row is normalized to an issuing range and matched against the issuing-range dataset, returning the scheme, brand, funding, country, currency and issuer. Inline, flat per row, and three possible answers.
returns inline · no queue · three verdicts
what runs per row
Two local steps, then one lookup.
The shape check runs locally and stops hopeless input before any request is made. Only the range lookup leaves the building.
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.
Six digits is the whole request
Only the BIN and a masked tail ever appear — never the rest of the number. There is no authorisation check, no balance check and no charge: this is a read of public range data.
how the job runs
Inline, not queued.
BIN rows come back completed on the submission itself — nothing queues and nothing is polled, so there is no job to wait on. The finished run is kept in your history, results CSV included.
a finished run
Three pills, not four. There is no unknown column on a BIN job.
1,396 rows · 1,396 credits, flat. A row that cannot be read as a range is skipped rather than failed.
verdicts
Three verdicts, never a fourth.
The dataset either holds the range or it does not, so there is nothing for an unknown state to say. An unlisted range is reported as unlisted.
the three states
A miss is dataset coverage, not a verdict on the card. Unlisted is not the same as disproven.
where that number comes from
Three fixed bands mapped straight from the dataset’s flags: 12 undeliverable, 62 risky, 92 deliverable. There is no weighted sum to reverse-engineer.
Three fixed bands mapped from the dataset’s signals — not a weighted sum.
The checks on a row
A range that is found returns these; one that is not returns a single failed dataset match, and nothing invented to fill the space.
- Dataset matchpass
- Issuerpass
- Risk profilepass
Precision appears only when a longer BIN prefix is available — this response had none, so the check is not here.
the profile
What the range returns.
The profile is the point of a BIN lookup: who issued this range, what it is, and the two flags that carry it to risky.
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.
Known limits
A BIN identifies the issuing range, not the account. Every card issued from that range shares these digits.
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.
Values of six to sixteen digits are accepted and truncated to the first eight. Six to eight is the whole input.
We never request a full card number and we never run authorisation checks. Only the six to eight digits that identify the range are needed, and that is all we ask for.
how it works
How bulk BIN verification works.
Every BIN in the file is normalized to its issuing range and resolved against the dataset that holds it.
- 01
Each BIN is normalized
6 to 8 digits. A longer value of up to 16 digits is accepted and truncated to its first eight — the digits that identify the issuing range. Whitespace is stripped first.
- 02
Then looked up against the issuing-range dataset
The range returns scheme, brand, funding, category, country, currency and issuer together, with prepaid and commercial as the two flags that drive risk. A miss is reported as unlisted, not as a fake card.
- 03
The verdict is one of three
Deliverable, risky or undeliverable. The engine never returns unknown for a BIN, so there is no fourth state to expect.
- 04
Results return inline
Completed on the same submission — nothing is queued and nothing is polled, so there is no job to wait on. The finished run is kept in your history with its results CSV.
Bulk BIN, drawn
A BIN identifies the issuing range, not the account, and every card from that range shares these digits; prepaid and commercial are range-level flags, not a fraud verdict; coverage is the dataset, so a miss means unlisted, not fake. Only the first 6-8 digits are ever needed — we never request a full card number and never run authorisation checks.
What is bulk BIN verification?
A BIN — a Bank Identification Number — is the leading group of digits on a payment card, and it identifies the issuing range a card was minted under rather than any individual card. Bulk BIN verification resolves many of those ranges together: each row is normalized to six to eight digits, matched against an issuing-range dataset, and returned with the profile the dataset holds for it.
That profile is range-level information: the network and brand, the funding type, the product category, the issuing country and currency, the issuer, and the prepaid and commercial flags. It describes a range of cards, not an account — nothing here reads a balance, authorises a transaction or identifies a cardholder.
What information does a BIN lookup return?
The fields below are the ones the response carries, in the dataset’s own names. Anything not in this list is not part of the lookup.
Card scheme / network
The payment network the issuing range is allocated to.
Card brand
The brand that network reports for the range.
Funding type
credit · debit · prepaid · unknown. An unresolved funding value lands the row risky.
Card category
The product class within the brand, as the dataset holds it.
Issuing country
The ISO country the range is issued in, with its name alongside the code.
Currency
The currency the range is issued in.
Issuer
The institution the range was allocated to, with its website and phone where the dataset carries them.
Prepaid flag
A range-level signal. True lands risky — not a judgement on the card.
Commercial flag
A range-level signal for business ranges. True lands risky.
Longer BIN availability
Whether a longer prefix exists for a sharper match — the precision signal, separate from the verdict.
Every field above appears in the response sketch on the single BIN lookup and in the profile section of this page — the bulk job returns the same shape per row.
What bulk BIN verification does not check.
This is a read of issuing-range data. Everything below sits outside it, on purpose — and none of it is a gap the lookup is trying to fill.
- The individual card account. A BIN is an issuing range, and every card from it shares these digits.
- The account balance. Nothing is read from an account, because no account is addressed.
- Authorisation. There is no authorisation request, no transaction simulation and no payment gateway in the path.
- A charge. Nothing is charged, and no card is contacted in any way.
- The cardholder. No name, address or identity is looked up, and none is returned.
- Whether a particular card is active. An unlisted range says the dataset does not hold it, not that a card is dead.
- Whether a transaction would be approved. Approval depends on the issuer, the balance and the risk rules at the moment of sale.
Only the six to eight digits that identify the range are needed, and that is all the page asks for. A full card number is never required, requested or stored for a BIN lookup.
BIN vs. full card number.
The distinction the whole page rests on: a BIN identifies a range, and many cards share it.
a BIN identifies
- An issuing range — the institution and network a group of cards was issued under
- The scheme, brand, funding type and product category of that range
- The country and currency the range was issued in
- Range-level prepaid and commercial signals
a BIN does not identify
- An individual card — thousands can share one BIN
- A specific account, or anything about its balance
- A cardholder, by name or otherwise
- A transaction, which is a separate event with its own data
- Whether a card is active, or whether a payment would be approved
Because the lookup needs the range and nothing else, the first six to eight digits are the whole input. A longer value is truncated to those digits before the request, so there is never a reason to hand over a full card number.
Bulk BIN verification credits.
A BIN job is one of the flat ones: no quality tiers, no multipliers.
One row, one charge
A processed row is charged at the current BIN rate, and there is no quality picker on a BIN job — nothing on this page changes the per-row cost. Email is the only kind with quality levels.
Quality tiers and credit multipliers do not exist for BIN, phone or WhatsApp work.
What is and is not charged
- A row that cannot be read as a range is skipped rather than failed, and a skipped row is not charged.
- Credits reserved above what the run actually needed are refunded when the job completes.
- Uploading and mapping the file cost nothing — the meter starts at the range lookup.
Bulk BIN verification use cases.
Where a range profile earns its place in a dataset. Every one of these ends in a row-level verdict and profile, not a fraud judgement.
Payment data enrichment
Add issuer, country, currency, funding and scheme fields to a dataset that only carries BIN digits.
Transaction data analysis
Group a large transaction set by card network and funding attributes to see how it is actually composed.
Risk-aware segmentation
Separate prepaid and commercial ranges from the rest, using the two range-level flags the dataset returns.
International payment analysis
Group issuing ranges by country and currency when a dataset spans more than one market.
Dataset normalization
Standardize BIN values — whitespace, prefixes, longer values — before anything downstream reads them.
Bulk BIN API
Send an array of ranges and read the completed profiles back from the same response.
Read the API docs →Bulk BIN verification vs. a single lookup.
Neither is better — both read the same dataset and return the same profile. What differs is how many ranges you hand over at once.
single BIN lookup
One range at a time, with the profile returned immediately. It suits reading a range you are looking at right now — during a support call, a review, or a one-off check.
The IIN/BIN checker documents the same field set.
bulk BIN verification
Many rows in one submission, each with its own verdict and profile, returned inline rather than through a queue. It suits a dataset where the row count is the point and the reasons need to be reviewable per row.
Working from a spreadsheet is the same job with a mapped CSV behind it.
Coverage & limitations.
What the dataset can and cannot tell you, kept beside the results rather than behind them.
- Every result depends on the coverage of the issuing-range dataset. A range it does not hold comes back unlisted.
- An unlisted range does not prove a card is fake, stolen or invalid. It reports what the dataset holds, which is a smaller claim.
- BIN data identifies a range rather than an account, so a profile is shared by every card issued under it.
- Prepaid and commercial are range-level signals. Plenty of legitimate cards carry them, which is why they land risky rather than undeliverable.
- A longer BIN prefix can classify more precisely, and the response says when one is available for the range.
- Provider data changes over time. A profile describes the dataset as it stood when the lookup ran.
The same boundary applies to the single BIN lookup and to every other BIN tool: a range lookup is a read of public issuing data, not a verdict on a card.
Bulk BIN API.
Bulk BIN is available as an API for API-key clients. Send an array of ranges with the kind set to bin and the completed results come back in the same response — there is no job to create and nothing to poll.
The response carries the run totals and counts alongside one result per range, with the same profile the dashboard shows. For the whole contract, read the API documentation.
$ curl -X POST https://api.multivalidator.io/api/v1/bulk \ -H "Authorization: Bearer mv_<64 hex>" \ -H "Content-Type: application/json" \ -d '{"kind": "bin", "targets": ["424671", "411111"]}'{ "success": true, "data": { "kind": "bin", "status": "completed", "total": 2, "deliverable": 2, "risky": 0, "undeliverable": 0, "unknown": 0, "results": [ ... ] }}
Bulk BIN verification FAQ.
What a BIN identifies, what the lookup returns, and what it deliberately does not do.
Bulk BIN verification resolves many BIN values in one pass. Each row is normalized to its issuing range, matched against the issuing-range dataset, and returned with the range profile — inline, on the same submission.
Stop mailing ghosts.
Start with free credits. No card, no call, no “book a demo”.