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 verify the match between bank card numbers and cardholder names to prevent financial fraud.
Input Format
One record per line, format: Name 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 batch tool submits two fields for each record: a name and a bank card number. It organizes the response from an online verification service into a row status such as match, mismatch, or unknown, with a note and any bank, card type, or card status information the service returns. Those extra fields may be blank. This is a service response for China-related bank-card records, not a US bank account lookup or a way to verify a card issued elsewhere.
Before any online check, the page screens the card number for 13–19 digits and a passing Luhn checksum. Luhn is a transcription check: it can catch some mistyped numbers, but it does not identify the account holder, show that an account exists, or predict the service result. A number that passes this screen still needs a response from the verification service.
The form and result labels are in English. Names and other returned record values may be in Chinese or another source language; they are displayed as returned rather than translated. The implementation sends each name-and-number pair to a connected third-party service. The original data collector, coverage, record refresh schedule, and retention period have not been verified.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Provide one name and its corresponding card number on each line, separated by a space, comma, or tab. You can also import an XLSX, CSV, or TXT file, or use the downloadable CSV example. Keep the name and number in separate columns in a spreadsheet, and preserve any leading zeros in the card number by storing that column as text.
Review the parsed rows, missing fields, and card numbers that fail the local format check. The batch limit is 500 records. Empty rows are removed and identical name-and-number pairs are deduplicated by default; review the available options if you need to keep repeated pairs. Only valid, nonduplicate rows count toward the verification preview and displayed cost.
Check the record count and price shown on screen, then start the batch. The page sends each pair for an online response and displays a status, note, and any returned bank or card details. Use the result export if you need a spreadsheet record of the displayed rows.
Use cases
See how the tool fits into real work and everyday tasks.
A team collecting China bank-card details for a permitted workflow can submit a prepared list and sort clear matches from mismatches, unknowns, and errors. Staff can then review the flagged rows with the person who supplied the information.
When an operations team has transcribed a set of name-and-card pairs, the preview can catch missing fields and numbers that fail the basic checksum screen. The response table helps direct follow-up, but should not be the sole basis for releasing funds or approving an account.
Q&A
Find concise answers to common questions and confusing cases.
No. Unknown means the response did not resolve to a clear match or mismatch status. Check the row note and the submitted details; do not relabel an unknown or service error as a mismatch.
No. The 13–19 digit and Luhn checks screen formatting only. They do not confirm that a card or account exists, is active, belongs to the named person, or can be used for a transaction.
It is intended for the supported China-related service context. Do not treat the results as a US bank lookup or assume that a card from another country is covered. The connected service’s complete issuer coverage has not been verified.
The form and status labels are English. Bank names, card details, notes, or other values returned by the service can remain in their original language.
Notes
Review scope, result limitations, and important precautions before use.
A check is online: each name and card number is sent to a connected third-party verification service. Submit only records you are authorized to use and that are necessary for the task. Do not enter PINs, security codes, passwords, or other card credentials; this check uses only the name and card number. The service’s original collection source and retention or deletion practices have not been verified, so do not assume the submission is retained for a known period or automatically erased.
A “match” is only the status returned for the submitted pair. It does not authenticate the person operating the tool, establish the cardholder’s consent, prove account ownership for a particular transaction, or certify identity. A mismatch, unknown result, or error should be reviewed through a trusted channel with the cardholder or issuing institution before any consequential decision.
Related
Discover related tools, collections, and available API capabilities.