JCB Card Generator (fake)

JCB card numbers: structure, BIN ranges and where they are accepted

JCB stands for Japan Credit Bureau, founded in Tokyo in 1961 as the first credit-card issuer aimed at the Japanese domestic market. What started as a closed-loop card for restaurants and department stores in Tokyo is today an international scheme accepted in roughly 190 countries, with more than 35 million merchants in the Asia-Pacific acceptance network alone. Inside Japan, JCB still holds around 70% of the domestic card market share, and most travel, transit and convenience-store loyalty cards in the country sit on top of JCB rails.

A JCB account number always starts with a BIN/IIN in the range 3528-3589 (the first four digits). The total length is typically 16 digits, although the standard allows 17 to 19 digits for some product families. The very last digit is the Luhn check digit, calculated with the same modulo-10 algorithm used by Visa, Mastercard and every other major scheme — so a JCB number that looks valid still has to pass the Luhn checksum before any gateway will route it.

Why so many BINs and Japanese partnerships

The wide 3528-3589 range exists because JCB historically issued co-branded products with dozens of Japanese banks, retailers and transit operators under the old JIS (Japanese Industrial Standards) numbering policy. Outside Japan, JCB relies on reciprocal acceptance agreements rather than building its own merchant base from scratch: a JCB card runs on Discover rails in the United States, on RuPay in India, on UnionPay in mainland China, and on Diners Club International in many other regions. That is why a Japanese tourist can swipe a JCB in a US store that does not display the JCB logo — the transaction is routed through Discover.

Security: J/Secure, EMV and tokenisation

JCB authentication uses J/Secure, the JCB implementation of the 3-D Secure 2 protocol, alongside loyalty programmes such as J/Premier. The CVV2 printed on the back is a 3-digit code, identical in format to Visa and Mastercard. Since 2020 every JCB card issued in Japan is required to carry an EMV chip, and the scheme participates in Apple Pay, Google Pay and Samsung Pay tokenisation, so e-commerce flows that use a Device PAN (DPAN) never see the real number.

Acceptance in Brazil and Latin America

In Brazil, JCB acceptance is narrower than Visa or Mastercard but broader than people assume: the three major acquirers — Cielo, Rede and Stone — all support JCB, mainly to serve the tourist corridor in São Paulo and Rio. If you ever tried to use a JCB card outside Tokyo and saw it being declined for "additional verification", that is the scheme's anti-fraud heuristic kicking in: out-of-region transactions on JCB BINs frequently require a step-up via J/Secure or a phone authorisation with the issuer.

FAQ

Can these numbers charge a real account? No. The generator produces BIN-valid, Luhn-valid PANs but none of them is linked to a JCB issuer account. They will be rejected the moment they hit a real acquirer.

Are they suitable for sandbox testing on PSPs? Yes — gateways like Stripe, Adyen, MercadoPago and PagSeguro ship dedicated JCB test PANs (e.g. 3566002020360505 on Stripe). Generated numbers from this tool follow the same Luhn rule and are useful to test your form-field validation and BIN-lookup logic, but for end-to-end charge flows always use the test PANs published by the PSP itself.

Does JCB processing differ from Visa or Mastercard at the integration layer? At the PSP API level, no — you POST the same JSON. At the acquiring layer, however, interchange fees, settlement currencies and chargeback windows differ, which is why some merchants choose to accept only Visa/Master.

Why does my generated 16-digit number start with 3528? Because that is the lowest valid JCB BIN; the tool picks a random prefix from the 3528-3589 range, fills the account body and computes the Luhn check digit at the end.