KEY TAKEAWAYS
- UnionPay uses 62 with 16–19 digits.
- Security code: 3 digits (back).
- Format checks are free; live status needs an issuer check.
- Validate locally first to avoid spending checks on bad rows.
- Every UnionPay card checking result class should map to a defined workflow action.
- Unknown deserves one fallback pass, not infinite retries.
Every network has its own number format — UnionPay included. This page covers the format facts you need for correct validation, and how to verify live status beyond the format.
UnionPay format at a glance
| Property | Value |
|---|---|
| Prefix / IIN ranges | 62 |
| Number length | 16–19 digits |
| Security code | 3 digits (back) |
| Checksum | Luhn (mod 10) |
What is specific about UnionPay
- UnionPay (China UnionPay) issues both domestic-only and international cards; the format is identical, so only a live check distinguishes usability abroad.
- Some UnionPay cards do not follow Luhn strictly — validators should treat Luhn failure as a warning, not always a hard reject, for this range.
- Co-badged UnionPay/Discover cards sit in shared ranges and route differently depending on the acquirer.
Validating and verifying
Bulk UnionPay lists
UnionPay dominates the Chinese market and appears increasingly elsewhere through partner agreements. Its numbers begin with 62 (plus select 60/81 ranges), and behavior splits sharply between domestic and cross-border: domestic issuer responses are fast and deterministic, while international traffic may be challenged or routed through partners.
Treat UnionPay verification as a two-layer problem: BIN data to confirm the range and expected card type, then a live check to learn whether the specific account is active on the route you have.
What is different about UnionPay
Reference metadata for UnionPay tells you the issuer and type; only a live check reveals whether the account is active. When a UnionPay check returns error, suspect the format or the route first — the card is still unclassified. UnionPay behaviour is shaped by both the network and the issuing bank, which is why two cards with the same brand can resolve differently. The reference data holds UnionPay ranges across many issuing banks, and the BIN tools expose them directly. Holding that line is what makes UnionPay card checking reliable over time.
The BIN layer behind UnionPay card checking
Analysts use BIN distributions to spot shifts in a portfolio long before individual results would show them. BIN data answers who issued a number and what kind of card it is; status requires a live check. The reference table holds hundreds of thousands of issuer ranges, and the tools expose it without any account-status claims. Six digits usually identify the institution; eight add the program or product level on many ranges. Write it down; UnionPay card checking workflows live and die on small consistencies.
Running UnionPay card checking well: the operating steps
Decide how each outcome is handled before the run starts; a triage plan written after the results arrive is usually just a spreadsheet. Size batches to the provider ceiling. Past that line, extra concurrency converts into timeouts rather than throughput. Keep a small balance buffer so an interrupted run never leaves a half-classified list and the temptation to re-check everything. For recurring workloads, schedule the run before the moment the answer is needed — ahead of a billing cycle, a payout batch or an onboarding window. Keep it in mind whenever UnionPay card checking results are reviewed.
What each UnionPay card checking outcome commits you to
The honest reading of unknown is "no answer yet". The card is neither good nor bad, and the remedy is a different route, not a repeat of the same one. Errors are free by design: no classification means no charge, so retrying after fixing the cause costs nothing but effort. Dead results are conclusive for the moment and should never be re-checked in the same run; retries on dead cards spend balance for identical answers. A live answer is evidence about the account, not a guarantee about a specific future transaction; issuer rules can change between the check and the charge. The habit costs nothing and removes a recurring class of mistakes.
Boundaries of UnionPay card checking
Check only cards you own or are authorised to process; verification is not a shortcut around cardholder authorization. Operators remain responsible for the legal basis on which they hold and process card data. Where a check is used inside a payment flow, it complements authorization rather than replacing it. In UnionPay card checking work, that is the difference between a signal and a guess.
Keeping UnionPay card checking predictable
Treat provider outages as routing problems: switch routes, recover the unclassified remainder, keep the answers you already paid for. Budget verification against the cost of failure, not against zero; the comparison is what makes spend defensible. Track cost per classified card rather than cost per request; it is the only metric that reflects retries and unknown rates. Document the route, the batch policy and the retry rules next to each production run; six months later that note is the diagnosis. In UnionPay card checking work, that is the difference between a signal and a guess.
Failure modes to design out of UnionPay card checking
Chasing every unknown in UnionPay card checking with unlimited retries costs more than classifying the rest of the list. Storing card data beyond the needs of UnionPay card checking creates risk without adding value. Assuming every UnionPay card checking gateway covers every brand is the fastest way to a list full of errors.
- Ignoring cost per classified card hides the real price of a cheap UnionPay card checking route with a high failure rate.
- Increasing parallelism past the provider ceiling in UnionPay card checking converts capacity into timeouts.
- Retrying a dead card during UnionPay card checking spends balance for an answer that will not change within the run.
- Validating after the paid UnionPay card checking request, rather than before, doubles the cost of bad input.
Using UnionPay card checking on the right side of the line
Verification is at its best when it is boring: a routine status step inside an existing, authorised process. High-value decisions deserve fresh checks; stale results drift as accounts change. Results describe the account, never the person; they should inform routing and risk decisions, not identity decisions. That single habit separates routine UnionPay card checking from expensive UnionPay card checking.
Measured behaviour of UnionPay card checking
Latency percentiles matter more than averages: the p90 and p99 tell you what a slow run actually feels like. The reference BIN table covers hundreds of thousands of issuer ranges, and it is deliberately separate from account-status data: one describes issuers, the other describes cards. Aggregate numbers describe populations, not individual cards. Use them to size timeouts and retry budgets, never to judge one account. When the classified rate moves, the cause is usually a route or provider change rather than the underlying cards. That single habit separates routine UnionPay card checking from expensive UnionPay card checking.