Topic starter
24/10/2026 8:47 pm
TL;DR: Treating eIDAS 2.0 as a verify-only connector leaves EU banks paying for compliance infrastructure while missing the wallet-based issuance workflows that turn the EUDI Wallet into a reusable identity anchor, reduce phishing exposure, and remove manual document handling, according to Truvity.
Editorial analysis by NHI Mgmt Group, based on content published by Truvity: “Why "Verify-Only" Won't Be Enough: The Case for Credential Issuance”.
Key questions
Q: What breaks when banks stop at verify-only wallet integration?
A: A verify-only approach leaves the organisation with expensive identity infrastructure that solves compliance but not workflow reuse.
Q: When should organisations move from verification to credential issuance?
A: They should move when the same trust decision will matter again after onboarding, such as proof of account, income, or eligibility.
Q: What are the signs that wallet identity programmes are underperforming?
A: The clearest signs are repeated redirects, manual document re-checks, high password-reset demand, and separate tools for verification, signing, and follow-on proofing.
Practitioner guidance
- Define wallet issuance governance before rollout Document which claims the organisation may issue, who approves them, how long they remain valid, and how revocation will work across products and channels.
- Separate verification and issuance workflows Map where onboarding verification ends and where reusable credential issuance begins so the two controls are not conflated in the same integration path.
- Rework customer journeys around reusable credentials Replace redirect-heavy processes with flows that can consume and later re-verify wallet credentials for account opening, proof of account, and claims validation.
Bottom line: Verify-only EUDI Wallet integration solves a mandate but leaves banks with fragmented journeys and limited operational leverage.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →