Topic starter
23/10/2026 12:48 am
TL;DR: Consumer onboarding preferences remain fragmented, with 24% still preferring branch verification, 14% preferring digital identity wallets, and 16% refusing to open a bank account online, according to IDnow. Onboarding flows need orchestration across wallet, branch, NFC, document, and assisted checks if they are to preserve both conversion and coverage.
Editorial analysis by NHI Mgmt Group, based on content published by IDnow: “The Identity Gap: One Size Fits None. Why the EUDI Wallet Won’t Please Everyone…”.
Key questions
Q: Why does single-method identity verification fail in consumer onboarding?
A: Because customer willingness to verify identity is not uniform.
Q: What happens when EUDI Wallet support is added without fallback verification paths?
A: The organisation gains wallet acceptance but loses customers who need a different channel to complete onboarding.
Q: How should organisations prepare to accept the EUDI Wallet in onboarding flows?
A: Start by identifying every onboarding journey that will depend on wallet acceptance, then map the assurance threshold each journey actually needs.
Practitioner guidance
- Implement a multi-method orchestration layer Build identity journeys that can route between EUDI Wallet, NFC, document verification, biometric matching, and video-assisted onboarding based on context.
- Define assurance-based routing rules Tie each verification path to transaction risk, customer segment, device context, and regulatory assurance requirements rather than defaulting to one method.
- Preserve non-wallet fallback paths Keep branch, assisted, and document-based options active for customers who cannot or will not use wallet-native onboarding.
Bottom line: EUDI Wallet support does not eliminate the need for other onboarding methods because consumer preferences remain fragmented across branch, wallet, NFC, document, and assisted channels.
Glossary terms: Eudi Wallet, Identity Orchestration, Selective Disclosure, Identity proofing
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 6 days ago by NHI Mgmt Group
23/10/2026 9:49 am
Identity verification strategy is becoming an orchestration problem, not a channel selection problem. The article’s central point is that consumers do not converge on one onboarding method, even when a new credential model is introduced. That means the real governance challenge is deciding how to route each user to the right method without lowering assurance. For identity programmes, the practical conclusion is that one-size-fits-all verification is now a structural failure mode.
A question worth separating out:
Q: When should banks prioritise orchestration over wallet-only deployment?
A: They should prioritise orchestration whenever customer demographics, transaction risk, or regulatory obligations require more than one acceptable method. Wallet support is useful, but it is not a universal replacement. The better design choice is to manage identity assurance through a governed routing layer.
👉 Read our full editorial: EUDI Wallet onboarding will only work with every verification method
This post was modified 6 days ago by NHI Mgmt Group