EUDI Wallet adoption hinges on trust, disclosure and friction

At a glance

What this is: IDnow's survey says EUDI Wallet adoption will depend on trust, transparency and reduced verification friction more than on speed alone.

Why it matters: Banks, telcos and public-sector identity teams need to design onboarding that balances assurance, privacy and user choice rather than assuming digital wallet uptake will be automatic.

By the numbers:

• Nearly half of respondents, 46%, said they often abandon a transaction when processes are too complex or take too long.

Context

The central governance problem is not whether the EUDI Wallet can exist, but whether identity systems can win user trust without creating avoidable friction. In consumer IAM, adoption depends on how assurance, data minimisation and usability are balanced at the point of verification.

The article frames the issue through a familiar identity gap: users want stronger fraud protection and more control over what they disclose, yet many still prefer legacy verification methods. That makes EUDI Wallet adoption a programme design question, not just a standards or rollout question.

Key questions

Q: How should banks prepare for EUDI wallet acceptance in regulated journeys?

A: Banks should classify which journeys can rely on wallet-presented evidence and which still require additional verification. The key is to tie wallet acceptance to transaction risk, assurance level, and audit requirements before production use. That avoids treating the wallet as a universal replacement for identity controls and keeps compliance decisions explicit.

Q: Why does friction matter so much in digital identity onboarding?

A: Friction matters because abandonment is a governance outcome, not just a UX outcome. When users stop midway through verification, institutions lose conversion and may push customers toward weaker or less secure alternatives, which undermines both security and assurance.

Q: What are the best practices for selective disclosure in consumer identity?

A: Best practice is to request only the claim needed for the transaction, explain why it is needed and avoid collecting full identity data by default. That approach reduces privacy exposure, improves user trust and aligns verification with the principle of minimum necessary information.

Q: What should organisations do when consumers still prefer legacy verification methods?

A: Organisations should keep multiple verification options available and treat them as part of one orchestration model, not separate programmes. Wallets, in-person checks and remote identity methods will coexist, so the programme should flex to user preference without lowering assurance.

Technical breakdown

Why selective disclosure changes onboarding economics

Selective disclosure lets a user prove only the attribute needed for a transaction, such as age, rather than exposing a full identity dossier. That is more than a privacy feature. It changes the cost model of identity verification because the institution can ask for just enough evidence to satisfy the use case while reducing unnecessary data handling. In practice, that shifts the design problem from collecting more identity data to deciding which claims are sufficient for a given assurance level. See the Digital Identity, eID and Identity Wallets Guide.

Practical implication: Design verification journeys around minimum-necessary attributes, not blanket data collection.

Why friction is now an assurance problem

Identity assurance fails when users abandon the flow before verification completes. The survey shows that complexity and delay are not just experience issues, they are control issues, because a broken journey can push users toward weaker or abandoned processes. In digital identity programmes, the relevant question is whether the verification path preserves enough integrity and usability to complete the transaction without creating shadow workarounds or drop-off. See the Identity Proofing and KYC Guide.

Practical implication: Treat user abandonment as a control failure, not just a UX metric.

How wallet-based identity fits alongside existing verification methods

The EUDI Wallet will not replace every onboarding method at once. Consumers still prefer in-person verification, NFC chip reads, selfie-based checks and video calls in significant numbers, which means institutions will need multi-path identity orchestration. The architecture problem is to route users to the right assurance method for the risk level, jurisdiction and product journey, rather than forcing one universal process across all customers.

Practical implication: Build adaptive onboarding paths that match assurance to transaction risk.

NHI Mgmt Group analysis

The EUDI Wallet is being judged as a trust framework before it becomes a scaling framework. Consumers are not only evaluating whether the wallet works, but whether it reduces fraud exposure without demanding unnecessary disclosure. That means identity teams should stop treating adoption as a rollout metric and start treating trust as the primary control surface.

Selective disclosure is the named concept that matters here. The article makes clear that users value the ability to prove a specific attribute without revealing their entire identity record. That preference changes the governance conversation from full-profile collection to claim-level minimisation, which is where modern consumer IAM programmes will win or lose acceptance.

Assurance design now has to absorb user tolerance for friction. Nearly half of respondents said they abandon transactions when processes become too slow or complex, yet many also accept extra checks if security improves. The practitioner lesson is that assurance strength and completion rate must be managed together, not as competing objectives.

EUDI Wallet adoption will be hybrid by necessity, not by exception. The survey shows consumers still prefer several verification methods, including in-person checks, NFC and video calls, alongside wallets. That means the market is moving toward orchestration of assurance paths, not the replacement of all legacy identity journeys at once.

Identity programmes that ignore data transparency will underperform even when the cryptography is sound. Respondents want to know what data is being used and to control what they disclose, which means trust hinges on explainability as much as on authentication strength. In consumer identity, governance has to make disclosure visible and understandable, not merely compliant.

From our research library:

• Nearly 60% of companies reported that fraud losses were still increasing in 2025.
• Read next: Digital Identity, eID and Identity Wallets Guide

What this signals

Selective disclosure is becoming the practical differentiator in consumer identity. The market will not reward identity systems that simply verify more aggressively. It will reward those that can prove enough, disclose little and still complete the transaction cleanly.

Identity teams should expect hybrid onboarding to persist well after wallet availability increases. The operational task is to make assurance routing visible, explainable and consistent across channels so users can move between methods without re-learning the process each time.

For practitioners

• Design for minimum necessary disclosure Map each onboarding flow to the smallest set of identity attributes needed for the transaction and document when selective disclosure is sufficient.
• Measure abandonment as a security signal Track where users drop out because verification is too complex or too slow, then treat those points as evidence of control friction.
• Offer multiple assurance paths Support wallet-based, in-person, NFC, selfie and video-call options so customers can move through the path that fits the risk and context.
• Make data use transparent in the journey Show users what data is requested, why it is needed and what will be shared before they commit to the verification step.

Key takeaways

• The survey shows that EUDI Wallet uptake will depend on trust, disclosure control and transaction friction, not just on technical availability.
• Consumer behaviour is fragmented, with many respondents still preferring legacy verification methods alongside wallet-based identity.
• Banks and other relying parties will need adaptive onboarding, selective disclosure and clearer transparency if they want wallet journeys to scale.

Related NHI Mgmt Group resources: Digital Identity, eID and Identity Wallets Guide · Identity Proofing and KYC Guide · Fraud Prevention Guide for Digital Businesses · NHI Lifecycle Management Guide

Key terms

• Selective Disclosure: Selective disclosure is the practice of sharing only the identity attributes needed for a specific decision. In credential-based systems, it reduces oversharing, lowers retention burden, and limits exposure when a verifier does not need the full record to make a trustworthy judgment.
• Identity Assurance: The confidence an organisation has that a person or system is truly who it claims to be before access or action is granted. In modern IAM, assurance depends on evidence quality, channel trust, and the strength of verification around high-risk decisions.
• Authentication Journey: An authentication journey is the sequence of steps a user follows to register, sign in, and gain access to an application. When verification is embedded into that journey, identity governance shifts from a separate control layer into the access path itself.
• Identity Orchestration: Identity orchestration is the control layer that routes identity decisions across applications and environments instead of letting each system manage access independently. For agents, it is the mechanism that can centralise policy, auditing, and downscoping at runtime.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are building or maturing an IAM programme, it is worth exploring.