Topic starter
25/10/2026 11:09 am
TL;DR: Identity verification has become a fragmentation problem, according to IDnow, where document checks, biometrics, AML screening and fraud controls sit in separate tools while compliance teams must adapt to fast-changing AMLA and eIDAS 2.0 requirements. The practical issue is not individual check quality, but whether verification journeys can be governed, observed and changed without rebuilding the stack.
Editorial analysis by NHI Mgmt Group, based on content published by IDnow: “Lessons From… Building a Platform That Makes Compliance Simple Again.”.
Key questions
Q: How should organisations govern identity verification across multiple vendors?
A: They should govern the full transaction as one control surface, not as disconnected point checks.
Q: Why does identity fragmentation create security and compliance risk?
A: Fragmentation makes it hard to apply the same policy to the same person because each system may see a different version of the record.
A: Fragmented verification usually shows up as custom flow logic, too many orchestration nodes, and inconsistent checks across journeys.
Practitioner guidance
- Define the verification journey as a governed workflow Map document checks, biometric steps, AML screening and fraud signals into one controlled onboarding flow so every decision is explainable across the full path.
- Move policy changes out of code release cycles Give compliance teams the ability to adjust checks by customer segment, market and risk level without opening a development ticket.
- Build an end-to-end audit trail for every outcome Capture which signals were used, which rule fired and whether the case was approved, escalated or declined so audits do not require manual reconstruction.
Bottom line: Fragmented identity verification creates a governance problem when checks, audit evidence and decisions are split across separate systems.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →