TL;DR: Digital IDs are now being used in everyday identity and age-assurance flows, with Yoti pointing to tighter regulation and higher privacy expectations as the driver. Identity teams now need policy-led orchestration and clearer trust rules for providers, data, and high-risk checks.
Editorial analysis by NHI Mgmt Group, based on content published by Yoti: “A look back at 2025”.
By the numbers:
- Yoti passed 1 billion age checks globally in 2025, reflecting broad adoption of age assurance across regulated sectors.
Key questions
Q: When should teams use orchestration for digital identity checks?
A: Use orchestration when one identity method will not work across all markets, regulators, or customer journeys.
Q: Why do digital IDs need stronger governance once they become mainstream?
A: Mainstream use turns digital ID into an operational control, so governance has to cover provider trust, data minimisation, assurance levels, and auditability.
Q: How should organisations support Digital ID without increasing privacy risk?
A: Start by removing unnecessary data collection from the verification flow.
Practitioner guidance
- Define where selective disclosure is mandatory Map every digital ID use case to the minimum attribute set required, and prohibit collection of full documents when a single claim is sufficient.
- Treat orchestration as identity policy infrastructure Document which certified identity methods are accepted by region, product line, and risk level so providers are selected by policy rather than convenience.
- Set stronger proof thresholds for high-risk sessions Require liveness or identity proof for interviews, onboarding, and sensitive transactions where impersonation would materially affect decisions.
Bottom line: Digital IDs are no longer just a pilot concept, because they are now being used in everyday identity and age-assurance flows.
Glossary terms: Selective Disclosure, Identity Orchestration, Age Assurance, Liveness Assurance
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Digital identity has crossed from convenience feature to governance layer: The article shows that reusable identity proofs are now being used in everyday interactions, which changes the control objective from single-use verification to ongoing trust management. For IAM teams, that means digital ID is no longer a niche onboarding tool but part of the identity architecture that affects access, assurance, and data minimisation. The practitioner conclusion is that digital ID must be governed like a core identity control, not an optional enhancement.
A question worth separating out:
Q: How should security teams handle deepfake risk in identity workflows?
A: Security teams should treat deepfakes as a trust and verification problem inside identity workflows. The right response is to require out-of-band verification for high-risk actions, separate request initiation from approval, and harden help-desk and finance procedures so a convincing voice or video cannot authorize access on its own.
👉 Read our full editorial: Digital IDs moved into mainstream use in 2025