My Number Card verification in Japan: a JPKI guide for business

Excluded from normalized aggregate trends after staff review: 3056 posts were attributed to March 2026; 671 shared March 14, 2026. The preceding six-month median was 13.5 posts.

Review evidence: 3,056 posts in March 2026; 671 shared March 14, 2026; preceding six-month median 13.5. Reviewed August 9, 2026.

This company's pages remain public, but its content is excluded from normalized aggregate trends. Unfiltered raw trends and advanced filtering are available to Accelerate and Lead accounts.

Japan’s My Number Card verification uses electronic certificates stored on the card’s IC chip and validated through the Japanese Public Key Infrastructure (JPKI), rather than using the holder’s My Number itself. Businesses can access the system either by becoming certified platform operators or by working through one, with the signature certificate providing verified name, address, date of birth, and gender for onboarding or signing, while the user-authentication certificate supports login without returning these attributes. About 104.18 million cards were held by July 2026, and card functions are available on iPhones from June 2025, with an updated Android implementation expected in autumn 2026. J-LIS certificate-check fees, formerly 20 yen for signature certificates and 2 yen for user-authentication certificates, have been waived since January 2023, although intermediary operators may charge their own fees. JPKI is used for financial account opening, loan contracts, electronic signatures, login, and age verification, and may become increasingly important as reported AML changes from April 2027 shift financial institutions away from photo-based remote identity checks. Businesses are advised to provide document-based alternatives for people without usable cards or compatible devices, while retaining responsibility for screening, risk assessment, and onboarding decisions.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.