We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Bulk lookup international bank card BINs to identify card networks, issuing banks, and countries of origin.
Input Format
One record per line, format: Card Number / BIN
Supports space, comma, tab separators
• Supports up to 200 records per batch
• Automatic Card Number / BIN validation after clicking 'Next'
• If deduplication is enabled, duplicate records will be removed automatically
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This batch lookup takes each submitted card-number or BIN entry, removes spaces and hyphens for validation, and uses only its first six digits for the lookup. The returned record may include the card network or scheme, card type, issuing country, and bank name. A field can be absent, so treat each value as information returned for that prefix rather than a guaranteed complete profile.
BIN is a familiar industry term; IIN (Issuer Identification Number) is the terminology used in ISO/IEC 7812. The current ISO/IEC 7812-1:2017 page describes the issuer-numbering system and confirms that edition remains current after its 2022 review. The American Bankers Association, the registration authority for the standard, describes the IIN as eight digits. This tool nevertheless queries six digits only. It therefore performs a six-digit prefix lookup, not a full eight-digit IIN match; distinct ranges can share the same opening six digits. ISO/IEC 7812-1:2017 and the ABA IIN information page explain the standard context.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Enter one prefix or card-number entry per line, or upload an Excel, CSV, or TXT file. Each row must contain 6–19 digits; spaces and hyphens are accepted and removed during validation. The form allows up to 200 records in one batch. You do not need to provide a complete card number: the query uses only the leading six digits.
Review the parsed rows and count before starting. Remove names, notes, account details, and unrelated columns from the file. Invalid entries can be flagged during preview. If you need a reusable layout, the page offers a one-column spreadsheet template.
Results identify whether a lookup returned successfully and show the available network, card type, country, and issuer fields. A successful response does not mean every field is populated. Keep blank or unclear fields as unknown rather than filling them by inference.
Use cases
See how the tool fits into real work and everyday tasks.
A developer or QA analyst can submit a short list of approved test BIN prefixes and compare the returned network or country labels with the labels in a test-data sheet. The lookup is a convenience for reviewing metadata, not a card-payment test.
An operations team with a permitted list of prefixes can use the batch output to group records by the fields that were actually returned. Leave uncertain issuer or product values unresolved until checked through an authoritative payment-industry source.
Q&A
Find concise answers to common questions and confusing cases.
You may enter an entry from 6 to 19 digits, but the lookup still sends only its first six digits. It does not use digits seven and eight to distinguish a full eight-digit IIN.
The lookup may return only some metadata for a six-digit prefix, and multiple more-specific ranges can begin with the same six digits. An empty or broad result does not establish which issuer or product applies; verify it with the issuer or relevant payment network.
No. It reports metadata associated with a prefix. It does not authorize a payment or check whether an account, card, balance, or transaction is valid.
No. Each record’s six-digit prefix is sent to the lookup service to obtain a response. Submit only data you are authorized to share, and avoid putting full card numbers or personal information in the batch.
Notes
Review scope, result limitations, and important precautions before use.
Do not submit a complete payment card number, security code, expiry date, cardholder name, or account information. Although the tool sends only the first six digits for each valid entry, the original batch is entered or uploaded to the service; do not assume that files or submitted data are retained for no time or are processed only on your device.
The specific source, geographic coverage, completeness, and refresh schedule of the lookup data have not been established. Results can be missing or out of date, and six-digit matching can be too broad for issuer-level decisions. Do not use this lookup as payment authorization, fraud screening, compliance evidence, or proof of card validity. Confirm important details with the card issuer or payment network.
Related
Discover related tools, collections, and available API capabilities.