Topic starter
25/10/2026 11:07 am
TL;DR: AMLR remote onboarding needs multiple compliant routes, according to IDnow, because recognised eID schemes, the EUDI Wallet, and QTSP-led document verification can all support completion. Verification programmes need routing that keeps customers in process when device, document, or risk conditions change.
Editorial analysis by NHI Mgmt Group, based on content published by IDnow: “How adding versatility in your user onboarding flow can help in the context of AMLR identity verification”.
Key questions
Q: Why does QTSP-led identity verification matter under AMLR if wallet-based onboarding is mandatory?
A: Because mandatory wallet acceptance does not make the wallet the only usable route.
Q: What breaks when an onboarding flow depends on one verification option only?
A: The flow becomes brittle.
A: They should build orchestration around multiple compliant routes, not a single verification method.
Practitioner guidance
- Map every remote onboarding route Document the accepted eID, EUDI Wallet, and QTSP-led IDV paths, then define when each path is eligible and who approves exceptions.
- Design failover between IDV methods Ensure the same onboarding session can move from NFC to optical review or video without restarting the process or losing evidence.
- Set assurance rules by risk segment Use device capability, document type, and session risk to decide when to keep automation and when to escalate to human review or video.
Bottom line: AMLR remote onboarding should be built as a multi-route identity flow, because a single verification method creates avoidable failure points.
Glossary terms: Remote Onboarding, Qualified Trust Service Provider, Risk-based Routing, Verification Orchestration
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 7 days ago by NHI Mgmt Group
27/10/2026 7:17 pm
AMLR onboarding is now a routing problem, not a single-method compliance test: the regulation permits more than one valid remote onboarding path, and that changes the control model. A programme that hard-codes one route turns a compliance choice into a business interruption point. The implication is that identity governance must be designed around route availability, not just route approval.
A few things that frame the scale:
- Gartner predicts that by 2026, 30% of enterprises will consider identity verification solutions unreliable in isolation because of AI-driven attacks.
A question worth separating out:
A: Use the option that matches device capability, document type, and risk level. NFC gives the strongest cryptographic assurance where available, optical review broadens coverage, and video handles complex or exception cases. The decision should be policy-driven, with routing rules that keep the customer in a compliant path.
👉 Read our full editorial: AMLR remote onboarding needs more than one verification path
This post was modified 7 days ago by NHI Mgmt Group