Topic starter
12/07/2026 12:27 pm
TL;DR: Japan’s digital policy roadmap is pushing My Number Card-based verification toward wider mobile use across iPhone and Android, with phased changes extending into 2028, according to Cybertrust Japan. The shift forces IAM and identity teams to treat mobile document verification as a governance and assurance problem, not just a convenience feature.
Editorial analysis by NHI Mgmt Group, based on content published by Cybertrust Japan: “ãiPhoneã®ãã¤ãã³ãã¼ã«ã¼ããã§ä»å¾ã®æ¬äººç¢ºèªæ¸é¡ã¯ã©ããªãï¼”.
Key questions
Q: How should organisations set assurance levels for mobile identity verification?
A: Start by tying each use case to a required assurance level, then decide whether mobile verification is sufficient for enrolment, recovery, or step-up access.
Q: What breaks when different mobile verification paths have different rules?
A: Identity consistency breaks first.
Q: How can teams tell whether mobile verification is working?
A: Look for reduced fraud loss, fewer successful account recovery abuse cases, and lower approval rates on high-risk transactions that follow recent SIM changes.
Practitioner guidance
- Define assurance tiers for mobile verification Map each identity use case to a required assurance level before allowing iPhone or Android mobile verification into production workflows.
- Standardise policy across device paths Use the same identity proofing rules, exception criteria, and approval thresholds across all mobile channels so convenience does not become a hidden downgrade.
- Separate device trust from identity trust Document which controls validate the device, which validate the document, and which validate the transaction outcome for each mobile flow.
Bottom line: Mobile document verification is becoming part of mainstream identity governance rather than a one-off convenience feature.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
12/07/2026 12:39 pm
Mobile identity verification is now an identity governance problem, not a channel feature. Once government-backed identity evidence is consumed through mobile devices, assurance depends on policy, device trust, and proofing quality rather than on the presence of a digital wallet alone. That makes verification design a governance decision that IAM teams must own, especially where access decisions depend on the outcome of the mobile check.
A question worth separating out:
Q: How should IAM teams govern mobile identity verification during a phased rollout?
A: Treat rollout as a governance exercise, not a feature deployment. Keep proofing, exception handling, and lifecycle review aligned across every supported device path so the organisation does not end up with one standard for early adopters and another for everyone else.
👉 Read our full editorial: iPhone My Number Card changes are reshaping identity verification