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
Batch lookup issuing bank, region, and card type using the first 6 digits of a bank card (BIN). Supports CSV import and export, up to 500 records per query.
Input Format
One record per line, format: Bank Card Number
Supports space, comma, tab separators
• Supports up to 500 records per batch
• Automatic Bank Card Number 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 lookup accepts full bank card numbers and returns provider-supplied issuer and card details for each submitted record. The displayed fields can include bank name, card name, card type, province or city, and a BIN value. The service is oriented to Chinese bank card records; it is not a global issuer directory or a way to look up a person or account.
BIN is a familiar name for the issuer-identification portion of a payment card number; the international standard describes the issuer identification number (IIN) and the primary account number (PAN). ISO/IEC 7812-1 specifies that numbering system. Issuer ranges may use six or eight digits, so a six-digit prefix should not be treated as a universal complete identifier. This batch process sends the full number for an individual provider lookup rather than querying only a public prefix. ISO/IEC 7812-1:2017 (confirmed current in 2022; checked 2026-10-02).
Records can pass the page’s basic format check when they contain 13–19 digits and satisfy the Luhn checksum. The lookup provider’s verified supported range is 16–19 digits. A checksum is a structural check only; it does not establish that a card was issued, is active, belongs to a particular person, or will authorize a payment.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Paste full card numbers into the text area, one per line, or upload an Excel, CSV, or TXT file. An Excel template is available. Keep each number in a single cell or line so it is not split into columns.
The page flags records that fail its format or checksum checks and removes duplicate rows by default. At least 20 valid, deduplicated records are required to continue, and a batch can contain no more than 500 input records. Review the valid count and displayed charge before starting.
After confirmation, each valid full card number is sent to the lookup provider for an individual request. The page shows processing status and any returned message as the batch runs.
Review issuer, card name or type, region text, and BIN where supplied. Export the results as an Excel workbook if needed, and retain unknown or failed rows for separate follow-up rather than treating them as verified.
A bank or card name is a provider response, not a record of account ownership. Province and city are returned location labels; they do not identify a branch or prove where an account was opened. The tool may display provider records in their original language, so some returned text can remain Chinese even when the form is in English.
Use cases
See how the tool fits into real work and everyday tasks.
A payments or finance team with documented authority to handle the card data can inspect returned issuer and card-type fields across an existing work queue, then route uncertain entries for a separate check.
When permitted to process the source file, an operations analyst can export the returned labels to help group records. Keep unmatched results in a review queue instead of inferring an issuer from the card number alone.
Q&A
Find concise answers to common questions and confusing cases.
No. The implemented input is a full card number and that full number is sent for the provider lookup. This is not a prefix-only public BIN search.
It means the number does not pass this page’s checksum test and is excluded from the valid query list. Passing the check does not prove that the card exists or is usable.
The provider did not return that field for the submitted record. The provider’s complete data coverage and update schedule have not been verified, so an unknown result does not show that the card is invalid.
No. It is only the location text returned by the provider. It does not establish a cardholder’s location, account ownership, or specific issuing branch.
Notes
Review scope, result limitations, and important precautions before use.
Related
Discover related tools, collections, and available API capabilities.