The European Digital Identity Wallet is important for the future of digital identity because it gives every EU citizen and resident a secure, standardised way to prove who they are and share verified credentials online, without relying on separate accounts, passwords, or paper documents. It shifts control of identity data from centralised platforms to individuals, making digital interactions faster, more private, and more trustworthy. The sections below answer the most common questions organisations have about how the EUDI Wallet works, what it means for their sector, and when they need to be ready.
How does the EUDI Wallet change the way identity data is shared?
The EUDI Wallet changes identity data sharing by putting verified credentials directly in the hands of the individual, who then decides what to share, with whom, and when. Instead of organisations requesting data from a central database or asking users to fill in forms, they receive cryptographically verified attributes directly from the user’s wallet. This makes the exchange faster, more private, and tamper-evident.
Today, most digital identity processes rely on one of two approaches: either users create new accounts and re-enter their information every time, or organisations query a central identity provider. Both approaches involve friction, privacy risks, and compliance overhead. The EUDI Wallet replaces this with a model where identity data is verified once, stored securely on the user’s device, and reused across any service that accepts wallet-based credentials.
The practical shift is significant. A user no longer needs to upload a passport copy to a bank, re-verify their address for a healthcare provider, or prove their professional qualifications to a new employer. They present the relevant credential from their wallet, the receiving organisation verifies it, and the process completes in seconds. No data is stored unnecessarily, and no third party sits in the middle of the exchange.
What types of credentials can be stored in the EUDI Wallet?
The EUDI Wallet can store a wide range of verifiable credentials, from government-issued identity documents to professional qualifications and sector-specific attestations. The starting point is the Person Identification Data (PID), which covers core identity attributes such as name, date of birth, and nationality. Beyond that, the wallet supports a growing set of use cases through additional credentials.
Examples of credentials that the EUDI Wallet is designed to support include:
- National identity documents and passports
- Driving licences and vehicle registration documents
- Educational diplomas and professional qualifications
- Health insurance cards and medical prescriptions
- Tax and social security information
- Age verification and other attribute-specific proofs
- Organisational credentials for business representatives
What makes this powerful is the concept of selective disclosure. A user who needs to prove they are over 18 does not have to share their full date of birth or any other personal detail. They simply present the relevant attribute, for example a confirmation that they are older than 18, without exposing any additional information. This privacy-by-design approach is built into the wallet architecture and aligns with GDPR principles around data minimisation.
Which sectors are most affected by the EUDI Wallet rollout?
The sectors most affected by the EUDI Wallet rollout are those that currently rely on manual identity verification, repeated KYC checks, or paper-based credential exchange. Financial services, government, healthcare, and education are among the primary areas where the impact will be most immediate and far-reaching, alongside telecoms, energy, transport, social security, and digital services.
In financial services, the wallet simplifies customer onboarding, reduces the cost of KYC and AML compliance, and enables reusable identity across banking, insurance, and investment services. Customers who have already been verified through their bank can present the same credentials at another financial institution. Whether that reuse satisfies the receiving institution’s AML obligations is determined by AML regulation, not by eIDAS 2.0 itself.
In government services, the wallet creates a trusted interface for citizens to access public services across borders. This is particularly relevant for EU residents who live or work in a different member state and currently face significant friction when dealing with foreign administrations. It is worth noting that cross-border use depends on the relevant relying party being registered and operational under the applicable national framework, and that not every use case will be available in every member state simultaneously.
In healthcare, the wallet enables secure sharing of patient data, prescriptions, and insurance credentials between providers, reducing administrative burden and improving continuity of care. Pharmaceutical companies and clinical research organisations also benefit from verified identity in regulated workflows.
Other sectors, including recruitment, education, and professional licensing, will also be significantly affected, as the wallet creates a trusted infrastructure for sharing and verifying qualifications and credentials at scale. Recognition of professional qualifications, however, continues to be governed by Directive 2005/36/EC and is not altered by eIDAS 2.0.
How does the EUDI Wallet relate to eIDAS 2.0?
The EUDI Wallet is the flagship instrument of eIDAS 2.0, which is Regulation (EU) 2024/1183 amending Regulation (EU) 910/2014. eIDAS 2.0 provides the legal framework, and the EUDI Wallet is the practical implementation of that framework at the citizen and organisation level. Without eIDAS 2.0, there would be no legal basis for the wallet’s recognition across EU member states.
The original eIDAS regulation, adopted in 2014, established rules for electronic signatures, seals, and cross-border recognition of national eID schemes. While it was an important step, uptake was uneven and many citizens never interacted with it directly. eIDAS 2.0 entered into force on 20 May 2024 and significantly expands the scope by requiring all member states to offer a digital identity wallet to their citizens and residents by 24 December 2026.
eIDAS 2.0 also introduces new concepts that the wallet depends on, including Qualified Electronic Attestations of Attributes (QEAAs), which are the high-assurance credentials that can be stored and presented through the wallet. The regulation also distinguishes between QEAAs, Public Body-issued Electronic Attestations of Attributes (PuB-EAAs), and non-qualified EAAs. It defines the role of trust service providers, the legally binding technical requirements that wallet implementations must meet through the implementing acts, and the obligations for relying parties, meaning organisations that accept wallet-based identity. The Architecture and Reference Framework (ARF), developed by the European Digital Identity Cooperation Group, provides the technical elaboration of those requirements but is not itself legislation.
For organisations already working with eIDAS-compliant processes, such as qualified electronic signatures or existing eID integrations, the transition to eIDAS 2.0 and the wallet ecosystem is a natural next step. Understanding how these two elements connect is essential for any organisation planning its implementation approach.
What does the EUDI Wallet mean for organisations that verify identities?
For organisations that verify identities, the EUDI Wallet means a fundamental shift in how they receive and process identity data. Instead of running their own identity verification processes from scratch, they become relying parties that accept credentials from the wallet, verified against the relevant national trusted lists. This reduces cost, improves accuracy, and shifts liability toward the trusted issuer of the credential.
Verifying a credential presented from the wallet involves three distinct checks. First, the issuer’s signature is verified against the relevant national trusted list, which forms part of the EU List of Trusted Lists (LOTL). Second, the revocation status of the credential is checked using the status information provided by the issuer. Third, the wallet unit attestation is checked to confirm that the presenting wallet is running on a certified wallet solution. Only the first of these checks can take place fully offline.
The practical implications for relying parties are significant:
- Onboarding becomes faster. Customers or users present verified credentials directly from their wallet, eliminating the need for document uploads, manual review, and back-and-forth communication.
- Compliance overhead decreases. KYC, AML, and other regulatory checks can draw on credentials that have already been verified by a qualified issuer, reducing duplication and cost. Whether a specific reuse of identity data satisfies AML obligations is determined by AML regulation.
- Data minimisation becomes the default. Organisations only receive the specific attributes they need, which simplifies GDPR compliance and reduces data storage risk.
- Cross-border acceptance becomes more straightforward. A certified wallet from one EU member state can be used with an appropriate relying party in another member state, removing much of the complexity of verifying foreign identity documents. Sector-specific legislation and national registration requirements continue to apply, and not every credential will automatically carry the same legal consequence in every jurisdiction.
- Audit trails become more robust. Cryptographic verification creates a clear, tamper-evident record of what was shared, by whom, and when.
Before a relying party can request wallet data, it must register with the national authority of its member state of establishment under CIR (EU) 2025/848, adopted on 6 May 2025. Registration covers the intended use and the specific attributes and attestations the relying party intends to request. The wallet checks each presentation request against this registered scope. A relying party does not choose a wallet provider; it must accept every relevant notified wallet, regardless of which provider issued it. A relying party does not automatically require a qualified trust service provider for wallet acceptance. A QTSP becomes relevant in contexts such as qualified signing or the issuance of qualified attestations.
Organisations that currently invest heavily in identity verification infrastructure will need to adapt their systems to accept wallet-based credentials. This requires integration work, policy updates, and in some cases, changes to existing compliance frameworks. The earlier organisations begin this process, the less disruptive the transition will be.
When will the EUDI Wallet be available across the EU?
Under eIDAS 2.0, every EU member state must have at least one certified EUDI Wallet operational for citizens, residents, and businesses by 24 December 2026. From that same date, public bodies and public service providers are required to accept notified wallets as a means of identification for online services where electronic identification is required. Several member states piloted wallet implementations through the EU’s large-scale pilots programme, which ran from April 2023 to 2025.
The rollout is happening in stages and is governed through shared responsibility across multiple actors. The European Commission manages the legal framework and adopts the implementing acts that contain legally binding requirements. Member states are responsible for providing or mandating wallet solutions, certifying and notifying them, and supervising actors within their jurisdiction. The European Digital Identity Cooperation Group supports cooperation and cross-border alignment. National competent authorities, wallet providers, issuers of Person Identification Data and attestations, qualified trust service providers, and relying parties each carry distinct responsibilities within this governance structure. The Architecture and Reference Framework (ARF), developed by the European Digital Identity Cooperation Group, provides the technical elaboration of the requirements set out in those implementing acts.
For regulated private-sector organisations, including those in banking, financial services, healthcare, telecoms, energy, transport, education, social security, drinking water, postal services, digital infrastructure, and digital services, a mandatory acceptance obligation applies from 24 December 2027, under Article 5f of the regulation. This obligation applies in contexts where strong user authentication is required by law or contract. Very large online platforms serving more than 45 million users in the EU are subject to a separate provision under Article 5f: they must accept the EUDI Wallet where the platform requires user authentication, on the voluntary request of the user and for the minimum necessary data. Micro and small enterprises, defined as organisations with fewer than 50 employees and an annual turnover or balance sheet total of no more than 10 million euro, are exempted from this obligation.
It is also worth noting that availability does not mean instant, universal adoption. The 24 December 2026 date is the legal deadline for member states’ wallet obligations; practical interoperability and national rollout are likely to develop in phases. Even once wallets are technically available, the level of maturity and the range of cross-border use cases that are fully operational may vary between member states. Organisations will need time to integrate, test, and update their processes, and relying-party registration remains connected to the applicable national registration framework. Regulated sectors with mandatory compliance timelines face the most pressure to move quickly, while others may have more flexibility in their transition timeline.
For organisations that have not yet started planning, the 24 December 2026 deadline for wallet issuance and public-sector acceptance is approaching rapidly, and the 24 December 2027 deadline for mandatory acceptance by regulated private-sector organisations is not far behind. The question is no longer whether to prepare but how quickly to act.
How TrustTech helps organisations prepare for the EUDI Wallet
The ID Connector is an integration that lets relying parties accept every certified European wallet, whatever Member State issued it, for identification, login and qualified signing. EUDI Wallet acceptance comes first; the same interface also carries other IDs, such as national eIDs, bank IDs and identity documents, inside and outside the EU.
For organisations in financial services, healthcare, pharma, and government, the ID Connector handles the technical and trust-layer requirements that wallet acceptance involves: verification of issuer signatures against national trusted lists that form part of the EU List of Trusted Lists, revocation status checks, validation of wallet unit attestations, and enforcement of the registered attribute scope under CIR (EU) 2025/848. Qualified signing is available through a connected qualified trust service provider.
Specifically, TrustTech supports organisations with:
- Assessing current identity infrastructure against eIDAS 2.0 requirements
- Implementing wallet-ready onboarding and verification flows
- Enabling reusable identity and compliance checks across your organisation
- Integrating qualified electronic signatures and attestations via a connected QTSP
- Building interoperable trust infrastructure across sectors including finance, government, healthcare, and pharma
- Going live in production in under five months
If your organisation is ready to take the next step toward EU digital identity readiness, get in touch with TrustTech to discuss what that looks like in your specific context.