What is the EUDIW and how does it fit into eIDAS 2.0?

EU passport and smartphone displaying a digital credential card on marble surface, representing European digital identity documents.

The European Digital Identity Wallet (EUDIW) is a secure digital app that allows EU citizens, residents, and businesses to store, manage, and share verified identity data and documents. It sits at the heart of eIDAS 2.0, the updated EU regulation that transforms how digital identity works across Europe. This article answers the most important questions about the EUDIW and what it means for your organisation.

How does the EUDIW fit into the broader eIDAS 2.0 framework?

The EUDIW is the central instrument of eIDAS 2.0. While the original eIDAS regulation (2014) created a framework for recognising national electronic ID systems across EU member states, eIDAS 2.0 goes much further by requiring every member state to provide a digital identity wallet to all citizens, residents, and businesses. The EUDIW is how that obligation becomes reality.

The original eIDAS regulation allowed member states to notify their national eID schemes so they would be mutually recognised across borders. In practice, this led to significant fragmentation. Some countries built strong national eID systems; others did not. Cross-border recognition was patchy, and private sector use was largely excluded from the framework.

eIDAS 2.0 changes this fundamentally. It introduces a common standard for digital identity wallets, a harmonised trust framework, and an obligation for both public and private sector services to accept the wallet under certain conditions. The EUDIW is not just a technical tool. It is the mechanism through which eIDAS 2.0 delivers on its promise of a unified, interoperable digital identity layer across Europe.

For organisations operating in regulated sectors, understanding the TrustTech identity solutions landscape within this framework is an important first step in preparing for compliance.

What can the European Digital Identity Wallet actually do?

The EUDIW allows users to securely store verified identity attributes and digital documents, authenticate themselves to online services, and sign documents electronically, all from a single app. It gives users direct control over what data they share and with whom, without relying on passwords or third-party platforms.

In practical terms, the wallet supports a wide range of everyday interactions. The large-scale pilot programmes currently testing the EUDIW have explored use cases across eleven areas, including:

  • Accessing government services such as applying for a passport, filing taxes, or accessing social security information
  • Opening a bank account online without repeatedly providing the same personal information
  • Registering a SIM card and proving identity to a mobile network operator
  • Presenting a mobile driving licence or other credentials
  • Sharing educational qualifications and professional certificates
  • Authorising payments for products and services
  • Accessing healthcare records and services across borders

One of the most important features of the wallet is selective disclosure. Users can share only the specific data that is needed for a transaction, for example confirming they are over 18 without revealing their full date of birth, or sharing their nationality without disclosing their home address. This reduces the risk of unnecessary data exposure and gives individuals genuine sovereignty over their personal information.

Who is required to accept the EUDIW?

Under eIDAS 2.0, certain categories of public and private sector service providers are legally required to accept the EUDIW as a means of authentication and identity verification. This obligation applies to services that are already required to use strong authentication, including online banking, financial services, healthcare platforms, and large online platforms.

For public sector services, the obligation is broad. Any digital public service that requires identity verification must accept the EUDIW once it is available in a given member state. For the private sector, the obligation applies to services that fall within specific regulated categories, particularly those subject to existing EU regulations around strong customer authentication, know-your-customer checks, or access to sensitive data.

This is particularly relevant for organisations in financial services, where strong customer authentication requirements under PSD2 already create a clear overlap with EUDIW acceptance obligations. Healthcare providers, insurers, and government service platforms are also directly in scope. Organisations in these sectors should not treat EUDIW acceptance as optional. It is a regulatory requirement that will need to be built into their digital infrastructure.

Organisations in the finance sector can explore how this affects their specific obligations through TrustTech’s finance sector approach to eIDAS 2.0 readiness.

How is the EUDIW different from existing national eID systems?

The EUDIW is not simply a digital version of an existing national ID card. It is a new type of identity infrastructure that combines authentication, document storage, and electronic signatures in a single interoperable tool that works across all EU member states, regardless of which country issued it.

Existing national eID systems, such as Germany’s eID, the Netherlands’ DigiD, or Austria’s ID Austria, were designed primarily for domestic use. They vary significantly in technical design, assurance levels, and cross-border compatibility. While eIDAS 1.0 created a mechanism for mutual recognition, the practical reality was that cross-border use remained limited and inconsistent.

The EUDIW addresses this by establishing a common architecture through the Architecture and Reference Framework (ARF), which defines the technical specifications that all wallets must follow. This means a wallet issued by one member state must work seamlessly when a user accesses a service in another member state. The wallet also extends beyond authentication. It can carry verifiable credentials such as diplomas, professional licences, and health documents, which national eID systems typically cannot.

Another key difference is the role of the private sector. National eID systems were largely designed for government services. The EUDIW is explicitly designed for both public and private sector use, making it a genuinely cross-sector identity infrastructure.

When will the EUDIW be available and what is the rollout timeline?

Member states are legally required to make the EUDIW available to all citizens, residents, and businesses by 2026. In 2026, the rollout is actively underway, with member states at different stages of implementation depending on their existing digital identity infrastructure and national readiness.

The groundwork for the wallet has been laid through a structured preparation process that unfolded in several phases:

  1. Regulation adopted (2024): The revised eIDAS 2.0 regulation entered into force, establishing the legal basis for the EUDIW and setting the 2026 deadline for member state compliance.
  2. Large-scale pilots (2023 to 2025): Four major pilot consortia involving over 350 organisations from 26 member states, Norway, Iceland, and Ukraine tested the wallet across real-world use cases and provided feedback on the Architecture and Reference Framework.
  3. Reference implementation released: The European Commission published an open-source reference implementation of the EUDIW, giving member states and private developers a tested baseline to build from.
  4. National rollouts (2026 onwards): Member states are now required to issue wallets and ensure acceptance by in-scope services. Early movers such as Denmark, with its AltID initiative, are already signalling what a national EUDIW rollout looks like in practice.

For organisations, 2026 is not a distant deadline. It is the current year, and preparation should already be in progress.

What should organisations do now to prepare for the EUDIW?

Organisations should start by assessing whether they fall within the scope of mandatory EUDIW acceptance, then map the technical and compliance changes needed to support wallet-based interactions. Waiting for full national rollouts before acting is a risk. The organisations best positioned for the EUDIW transition are those that started preparing early.

Practically, preparation involves several parallel workstreams. First, organisations need to understand the regulatory scope. Does your service fall within the categories required to accept the EUDIW? If you operate in financial services, healthcare, government, or any regulated sector that uses identity verification, the answer is almost certainly yes.

Second, organisations should review their existing identity infrastructure. Can your current systems handle wallet-based authentication and verifiable credentials? Most legacy identity systems were not designed with the EUDIW architecture in mind, and integration work takes time.

Third, consider the opportunity beyond compliance. The EUDIW enables reusable, verified identity data. Organisations that embrace this can significantly reduce onboarding friction, eliminate repeated identity checks, and improve the customer experience. The compliance requirement and the business opportunity point in the same direction.

For organisations in the government and public sector, the government sector readiness guidance provides a useful starting point for understanding what wallet integration means in a public service context. Healthcare organisations can find relevant context through TrustTech’s healthcare sector resources.

How TrustTech helps organisations prepare for the EUDIW

TrustTech supports organisations across regulated sectors in navigating the transition to eIDAS 2.0 and the European Digital Identity Wallet. Rather than leaving organisations to piece together the regulatory, technical, and operational requirements on their own, TrustTech provides a structured path from understanding to implementation.

Concretely, TrustTech helps with:

  • Regulatory scoping: Identifying whether and how your organisation falls within the EUDIW acceptance obligations under eIDAS 2.0
  • Technical integration: Connecting your existing systems to wallet-based authentication and verifiable credential flows
  • Reusable identity infrastructure: Enabling verified identity data to flow across your onboarding, compliance, and signing processes without starting from scratch each time
  • Compliance readiness: Aligning your identity processes with eIDAS 2.0, GDPR, AML, and KYC requirements in a single coherent framework
  • Fast time to production: Getting organisations to a production-ready state in under five months, with measurably faster onboarding outcomes

Whether you are just starting to map your EUDIW exposure or are already working through integration challenges, TrustTech brings the technical depth and regulatory expertise to move you forward with confidence. Get in touch with TrustTech to discuss what EUDIW readiness looks like for your organisation.