Batch BIN Lookup
Paste up to 2,000 card prefixes and get the issuer, brand, type, category and country for each one. Runs entirely in your browser — the prefixes never leave your device.
How this tool works
A batch lookup resolves many prefixes at once, which is what you want when you are cleaning a data set rather than checking a single number. Paste or upload a list, and each prefix is resolved against the dataset in the browser, with the results as a table you can copy or download.
Because the resolution runs locally against the loaded chunk, a large list is processed in the browser rather than sent to the API, and nothing leaves the machine. That is the point of the tool: enriching a set of records is exactly the operation where you least want the records travelling to a third party.
What a batch returns
| Input | Output |
|---|---|
| 424242 | Issuer, brand, type, category, country |
| 510510 | Issuer, brand, type, category, country |
| Unknown prefix | Reported as unknown, not guessed at |
A prefix that is not in the dataset is reported as unknown, which is a finding about the data rather than an error in the lookup.
When to use it
- Enrich a set of card records with issuer, brand and country
- Find the unknown prefixes in an imported data set
- Reconcile a merchant file against the public allocation record
- Check a large list without sending it anywhere
Frequently asked questions
How does a batch lookup work?
Each prefix is resolved against the dataset, using the chunk that contains it where possible and the API otherwise, and the results are shown as a table.
Is my data sent to a server?
The resolution runs in your browser against the loaded data. Nothing is uploaded. The API is only used as a fallback for a prefix that is not in the loaded chunk.
What happens to a prefix that is not found?
It is reported as unknown, which is a useful result rather than a failure. A set with a high proportion of unknowns is usually a set with a data quality problem.
How many prefixes can I resolve at once?
As many as the browser will hold. The data is loaded on demand, so a list larger than the loaded chunk will pull the chunks it needs.
Can I export the result?
Yes, the enriched table can be copied out as CSV or JSON for the rest of your pipeline.