Notifications
Clear all
Topic starter
12/07/2026 12:27 pm
TL;DR: Japan’s Digital Agency has set out how the iPhone my number card will combine public personal certification and card surface information, while separating it from Apple Wallet, and notes further changes through 2028, according to Cybertrust Japan’s summary of the 2025 update. The operational issue is not the mobile wallet label itself, but which identity proofing and attribute sources are legally recognised and how organisations must adapt their verification flows.
NHIMG editorial — based on content published by Cybertrust Japan: iPhone my number card and Apple Wallet relationship and implications
By the numbers:
- 2028 年冬頃までに、本人確認にかかわる新サービスの提供開始や本人確認手法の導入、法改正が目白押しとなります。
- 2025 年 6 月 24 日にデジタル庁より「 iPhone のマイナンバーカード」提供開始に関するお知らせが公開されました。
Questions worth separating out
A: Treat mobile identity as a proofing channel with a defined assurance level, not as a generic wallet feature.
Q: When should IAM teams re-evaluate identity verification flows for mobile credentials?
A: Re-evaluate flows whenever the proofing method, legal basis, or acceptance rule changes.
Q: What breaks when organisations treat a mobile wallet as equivalent to government identity proofing?
A: Trust breaks first. Teams may accept a presentation layer as if it were an assurance method, which weakens onboarding, recovery, and audit decisions. The result is a policy mismatch between what the user sees and what the relying party can safely accept.
Practitioner guidance
- Separate proofing from presentation in policy Document which flows accept a legally recognised proofing method and which flows only use a mobile presentation layer.
- Review onboarding and recovery paths now Map how identity enrolment, re-verification, and account recovery will change as mobile identity methods expand through 2028.
- Define acceptance rules by identity method Create method-specific trust policies for physical card, mobile card, and future resident-card variants.
What's in the full article
Cybertrust Japan's full blog covers the operational detail this post intentionally leaves for the source:
- The full Japanese explanation of how the iPhone my number card maps to legal identity proofing rather than consumer wallet behaviour.
- The step-by-step differences between Apple Wallet usage, public personal certification, and the card-information functions described in the article.
- The implementation and approval distinctions for service providers that need to support the new mobile identity model.
- The forward-looking discussion of how 2028 policy and product changes may alter identity verification journeys.
👉 Read Cybertrust Japan's analysis of iPhone my number card and Apple Wallet identity →
iPhone my number card changes in identity proofing and wallet use?
Explore further
12/07/2026 12:40 pm
Mobile identity is becoming a regulated proofing channel, not just a convenient form factor. The article shows that the iPhone my number card is being positioned inside a legal identity framework, with separate handling for public personal certification and card information. That means practitioners cannot evaluate it as a consumer-wallet feature alone. The correct lens is human identity assurance, where proofing source and legal recognition matter more than device convenience. The implication is that mobile identity policy must be written around assurance boundaries, not brand-led user experience.
A few things that frame the scale:
- 71% of NHIs are not rotated within recommended time frames, increasing the risk of compromise over time, according to Ultimate Guide to NHIs , Why NHI Security Matters Now.
- 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools, according to Ultimate Guide to NHIs , Key Challenges and Risks.
A question worth separating out:
Q: Who is accountable for identity assurance when mobile proofing methods change?
A: The relying party remains accountable for deciding what evidence is acceptable, even when the government or platform vendor supplies the proofing mechanism. Compliance, IAM, and product owners should jointly define the acceptance standard and the audit trail.
👉 Read our full editorial: iPhone my number card and Apple Wallet reshape identity proofing
