TL;DR: Awareness sharply affects trust in a secure rollout, with informed consumers far more confident than those unfamiliar with it, according to IDnow research, which finds that 51% of French and German consumers have never heard of the EUDI Wallet, while only 20% clearly understand it. Selective disclosure and simple, interoperable user journeys will determine whether digital identity systems earn durable public trust.
At a glance
What this is: IDnow’s consumer research shows that the EUDI Wallet still lacks basic public understanding in France and Germany, and that familiarity materially increases confidence in a secure rollout.
Why it matters: IAM, identity verification, and digital wallet programmes need trust, usability, and selective-disclosure design to work in practice, not just in policy.
By the numbers:
- 51% of respondents have never heard of the EUDI Wallet.
- 75% of informed consumers have confidence in a successful rollout, compared to 33% of those who have never heard of it.
- 63% said they would be more likely to use the EUDI Wallet when told it could prove they were over 18 without sharing personal details.
Context
The core issue is not whether the EUDI Wallet can exist on paper, but whether people understand it well enough to trust it in everyday use. Digital identity programmes often fail at the adoption layer before they fail at the technical layer, because users cannot evaluate safeguards they do not understand. Digital Identity, eID and identity wallets become difficult to operationalise when public confidence lags the policy schedule.
This research is a useful reminder that identity infrastructure is not only an authentication problem, but also a governance and communication problem. Selective disclosure, interoperability, and user comprehension all shape whether a digital wallet becomes a trusted identity control or just another underused public system.
Key questions
Q: How should organisations build trust in digital identity wallets before launch?
A: Treat trust as a programme control, not a communications afterthought. Users need clear explanations of what the wallet does, what data it shares, and how selective disclosure works in practice. Adoption improves when the user journey is simple, the privacy story is concrete, and relying parties behave consistently across services.
Q: Why do digital identity programmes fail when users do not understand them?
A: Because comprehension is part of operational readiness. If users cannot explain the value, privacy safeguards, or transaction flow, they are less likely to trust the system or complete enrolment. That weakens adoption even when the underlying identity architecture is technically sound and policy compliant.
Q: What are the main signs that a digital wallet rollout will struggle?
A: Low awareness, high confusion, and uneven confidence are early warning signs. When users do not know what the wallet does, or when different services behave inconsistently, the programme is likely to face trust resistance, support burden, and slower adoption than planned.
Q: How do interoperability and user trust interact in digital identity systems?
A: They are tightly linked. A wallet that works differently across issuers or relying parties feels unreliable, even if the cryptography is solid. Consistent validation, consent handling, and credential presentation are necessary so users experience one coherent identity system rather than a set of disconnected pilots.
Technical breakdown
Why selective disclosure changes digital identity risk
Selective disclosure means a person can prove one attribute, such as age, without exposing unrelated personal data. Technically, this reduces overcollection and narrows the privacy surface, but it only works if relying parties trust the verification workflow and users understand what is being shared. In wallet ecosystems, the security control is not just cryptography. It is also policy, presentation, and consistent validation across services. If users cannot explain the transaction to themselves, confidence in the system drops even when the underlying assurance model is sound. See the Identity Proofing and KYC Guide.
Practical implication: Practitioners should test whether wallet journeys explain what is shared, with whom, and why, before treating selective disclosure as an adoption feature.
Why interoperability is the real adoption test
Interoperability determines whether identity wallets work across borders, sectors, and service providers without confusing users or weakening assurance. In practice, this means the wallet, issuers, and relying parties must agree on credential formats, validation logic, and consent handling. If the user experiences inconsistent behaviour from one service to the next, the programme looks unreliable even when the core architecture is sound. That is why interoperability is both a technical and a trust requirement, not just a standards issue. See the Digital Identity, eID and Identity Wallets Guide.
Practical implication: Practitioners should validate end-to-end interoperability journeys early, not wait for launch-stage integration testing to expose user confusion.
Why trust in digital identity depends on assurance, not awareness alone
Awareness campaigns can improve recognition, but they do not by themselves create trust. Users judge digital identity systems by whether they appear safe, understandable, and reversible when something goes wrong. That means assurance signals, governance transparency, and dispute handling matter as much as registration flows. When confidence differs so sharply between informed and uninformed users, the programme has a communication deficit that can become an operational one. Identity systems succeed when trust is designed into the user experience and governance model together. Read the Ultimate Guide to NHIs: Regulatory and Audit Perspectives.
Practical implication: Practitioners should align comms, policy, and assurance evidence so the user story matches the technical trust model.
NHI Mgmt Group analysis
Trust gap, not launch timing, is the binding constraint: the research shows that digital identity adoption can stall even when the policy timetable is fixed. Users do not trust systems they do not understand, especially when personal data and cross-service reliance are involved. For identity programmes, the practical lesson is that rollout readiness must include comprehension and confidence measures, not only technical go-live criteria.
Selective disclosure is the clearest adoption lever: people respond to digital identity when they can see that the system limits data exposure to the minimum necessary. That is a governance advantage because it converts abstract privacy promises into a concrete user benefit. The field should treat selective disclosure as a trust control, not a marketing message, and align it with identity proofing and KYC expectations where assurance and privacy need to coexist.
Interoperability failure is a governance failure in disguise: when different systems do not behave consistently, users experience the wallet as unreliable even if the underlying components are compliant. That shifts the burden from engineering teams alone to programme owners who must govern issuer, wallet, and relying-party behaviour together. Practitioners should treat interoperability as part of identity governance, because confidence erodes quickly when the user journey fragments.
Digital identity programmes are judged by the user’s mental model: if people cannot explain what the wallet does, what it shares, and what they retain control over, they will default to caution. That is especially true where governments or regulated services are involved, because trust is inseparable from accountability. The conclusion is straightforward: usability, consent clarity, and visible safeguards are now core identity controls, not optional communication extras.
What this signals
EUDI Wallet trust gap: public confidence in digital identity will increasingly depend on whether users can understand and verify what the wallet is doing in live transactions. Launch plans that ignore comprehension will meet adoption friction, even when the underlying assurance model is technically sound.
A digital wallet programme should be judged against the user experience of assurance, not just against enrollment targets. When selective disclosure, interoperability, and consent transparency align, identity systems are far more likely to earn durable trust across regulated services.
For practitioners
- Define the trust story before the rollout date Map the exact user questions that must be answered at first contact, including what data is shared, what is not shared, and how the user retains control.
- Test selective disclosure in real service journeys Validate whether age checks, address checks, and other attribute proofs work without forcing unnecessary disclosure or confusing the relying party.
- Measure public understanding as a launch metric Use awareness, comprehension, and confidence indicators as programme gates alongside technical readiness and integration testing.
- Stress-test interoperability across relying parties Check that wallet behaviour, credential validation, and consent prompts remain consistent across the services people will actually use.
Key takeaways
- The research points to a familiar identity governance problem: users do not trust what they cannot understand, even when the architecture is sound.
- The strongest adoption signal is not awareness alone but whether the wallet can prove specific attributes without unnecessary disclosure and still work across services.
- Programme owners should treat comprehension, interoperability, and selective disclosure as launch criteria because each one affects real-world trust and uptake.
Related NHI Mgmt Group resources: Digital Identity, eID and Identity Wallets Guide · Identity Proofing and KYC Guide · Ultimate Guide to NHIs: Regulatory and Audit Perspectives
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-63 and NIST CSF 2.0 set the technical controls, while GDPR and ISO/IEC 42001:2023 define the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-63 | SP 800-63C — Federation | The article focuses on federated digital identity wallets and cross-service trust. |
| SP 800-63B — Authentication | Wallet adoption depends on reliable authentication and user comprehension at use time. | |
| Recommendation — Align wallet trust, federation, and relying-party validation with SP 800-63C before rollout. Test authentication journeys so the wallet remains understandable and dependable for end users. | ||
| NIST CSF 2.0 | PR.AA-05 — Access Permissions, Entitlements and Authorizations | Selective disclosure and least-data sharing are authorization questions in practice. |
| Recommendation — Use PR.AA-05 to limit shared attributes to the minimum required for each transaction. | ||
| GDPR | Art.5 — Principles relating to processing of personal data | The article centers on personal data minimisation and user control in digital identity. |
| Recommendation — Design wallet flows to minimise personal data exposure and make consent understandable. | ||
| ISO/IEC 42001:2023 | GOVERN — AI Governance and Accountability | The article mentions AI-driven identity assurance in a broader vendor context, but the primary topic is digital identity governance. |
| Recommendation — Document governance, accountability, and user-impact checks for AI-assisted identity workflows. | ||
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.
- Digital Identity Wallet: A digital identity wallet is software that stores and presents credentials for a person or organisation. It is a portability layer, not an authorization system. The wallet moves verified proof between parties, while the relying party still has to decide whether the proof is sufficient for the requested action.
- Identity Interoperability: Identity interoperability is the ability for different systems and vendors to represent, validate, and govern the same identity subject consistently. It matters because fragmented semantics create audit gaps, inconsistent lifecycle handling, and control drift across platforms.
- 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.
Deepen your knowledge
The NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, identity lifecycle, and related control thinking for practitioners working across identity and access programmes. It helps teams connect identity controls to the governance decisions that determine whether security capabilities are actually usable.
Published by the NHIMG editorial team on October 22, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org