By 24 December 2026, EUDI Wallets can legally replace physical identity documents for a wide range of digital interactions across the EU, though they do not yet fully replace physical documents in all situations. Regulation (EU) 2024/1183, which amends Regulation (EU) 910/2014, requires EU member states to provide every citizen, resident, and business with a European Digital Identity (EUDI) Wallet by 24 December 2026, enabling secure, cross-border digital identity verification. Whether the wallet replaces your physical ID depends on the use case, the sector, and how far along each member state is in its rollout. The sections below address the most important questions organisations and individuals are asking right now.
What can the EUDI Wallet actually be used for?
The EUDI Wallet is designed to store, manage, and share verified identity data and digital documents across a wide range of everyday and professional situations. The wallet acts as a portable, tamper-evident container for attributes and credentials that can be shared selectively, meaning you disclose only what is strictly necessary for each interaction.
Based on the use cases developed through the EU’s large-scale pilot programmes, the EUDI Wallet supports the following scenarios:
- Mobile driving licence: Presenting your driving licence digitally, both online and at the roadside
- Travel documents: Sharing passport or travel credential data at airport security and customs checkpoints, a use case that was piloted under the EWC consortium and is not yet fully operational at border controls
- Prescription claims: Providing verified prescription details to pharmacies across EU borders
- Educational credentials: Proving diplomas, degrees, and certificates when applying for jobs or further education
- Social security access: Accessing benefits and healthcare entitlements, including the European Health Insurance Card
- Contract signing: Creating qualified electronic signatures that remove the need for paper documents
- Online payments: Verifying identity when initiating financial transactions
- Organisational identity: Proving you are an authorised representative of a business or institution
What makes the wallet particularly powerful is the principle of reusability. A person verified once, for example through their bank or government portal, can reuse that verified identity across every service they interact with. This removes the need to prove yourself from scratch every time you engage with a new organisation.
Are physical ID documents legally required under eIDAS 2.0?
eIDAS 2.0 does not abolish physical identity documents. Regulation (EU) 2024/1183 establishes the EUDI Wallet as a legally recognised, high-assurance method of identity verification, but it does not mandate that physical documents be discontinued. The wallet is intended to be accepted as a legally equivalent alternative for most digital and increasingly physical interactions.
The regulation does, however, create strong legal obligations on the acceptance side. Public sector bodies are required to accept certified EUDI Wallets as a valid form of identity verification for online services requiring electronic identification from 24 December 2026. For regulated private sector organisations, including those in banking and financial services, healthcare, telecoms, energy, transport, education, social security, drinking water, postal services, and digital infrastructure, the obligation to accept the wallet applies from 24 December 2027, under Article 5f of the regulation, within contexts where strong user authentication is legally or contractually required. Very large online platforms (VLOPs) serving more than 45 million users in the EU fall under a separate provision of Article 5f: the obligation applies 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 euros, are exempt from the Article 5f acceptance obligation.
For purely physical situations, such as border crossings or police checks in some member states, physical documents remain the standard for now. The trajectory is clearly toward greater digital equivalence, but the legal framework still accommodates both formats during the transition period. Organisations operating in regulated sectors should treat the wallet as a legally valid and increasingly expected channel.
What is the difference between a digital wallet and a physical ID document?
A physical ID document is a static, centrally issued artefact, while a digital identity wallet is a dynamic, user-controlled container for verified credentials. A physical passport or national ID card contains fixed data printed and chipped at the time of issuance. The EUDI Wallet holds multiple credentials that can be updated, selectively disclosed, and verified against national trusted lists in real time.
This distinction has significant practical implications. With a physical document, you hand over the entire document and the receiving party sees all the information on it. With the EUDI Wallet, you can share only the specific attribute needed. For example, you can prove you are over 18 without revealing your date of birth, name, or address. This selective disclosure model is a core design principle of the European Digital Identity framework and can be achieved through attribute-level disclosure without requiring zero-knowledge proofs.
Another important difference is verification reliability. Physical documents rely on visual inspection or chip reading, which requires specialist equipment and trained staff. Digital wallet credentials can be verified by checking the issuer’s signature against the relevant national trusted list, which is part of the EU List of Trusted Lists (LOTL), by checking the revocation status of the credential through the issuer’s status information, and by validating the wallet unit attestation to confirm that the presenting wallet runs on a certified wallet solution. The first of these checks can be performed offline; the second and third require connectivity. Describing wallet verification as a single, fully offline cryptographic check would therefore be an oversimplification.
Which sectors will feel the biggest impact by 2026 and 2027?
The sectors most immediately affected by the EUDI Wallet rollout are financial services, government, healthcare, and education. These are the domains where identity verification is most frequent, most regulated, and most costly when done inefficiently. Each sector faces a distinct set of obligations and opportunities under eIDAS 2.0.
Financial services and banking
Banks, insurers, and payment providers operate under layered compliance requirements including KYC, AML, and PSD2. The EUDI Wallet introduces a new channel for onboarding and re-verification that is legally recognised at the highest assurance level. For regulated financial institutions, the obligation to accept the wallet applies from 24 December 2027, within contexts requiring strong user authentication. Note that reuse of KYC data across organisations is governed by AML regulation, not by eIDAS 2.0 itself. This deadline falls twelve months after the wallet issuance and public sector acceptance deadline of 24 December 2026, giving organisations a window to test wallet-based flows before their own obligation takes effect. Organisations that begin integrating wallet acceptance ahead of that deadline can reduce onboarding friction and streamline compliance workflows. The financial services sector stands to gain considerably from reusable, wallet-ready identity data.
Government and public services
Public sector bodies are among the first obligated parties under eIDAS 2.0, with a legal deadline of 24 December 2026 to make certified EUDI Wallets available and to accept them for digital public services. It is important to note that meeting this legal deadline does not mean every national wallet will reach the same level of maturity on that date, nor that every cross-border use case will be fully operational throughout Europe immediately. Practical interoperability and broader adoption will continue to develop in phases beyond that point. The obligation covers a wide range of interactions, from tax filings and benefit claims to permit applications and cross-border administrative processes. Member states that have already invested in national digital identity infrastructure are better positioned to meet the deadline, though existing national eID systems do not automatically qualify as certified EUDI Wallets without going through the required certification and notification process. Before accepting a wallet, relying parties must also register with the national authority of their member state of establishment under CIR (EU) 2025/848 of 6 May 2025, specifying per intended use which attributes and attestations they will request. Government organisations navigating this transition need to update both their technical infrastructure and their legal acceptance frameworks.
Healthcare and pharmaceuticals
The healthcare sector faces particular complexity because identity data intersects with sensitive medical records and cross-border treatment rights. Processing health data requires both a legal basis under the GDPR and a condition under Article 9(2) GDPR. The EUDI Wallet enables verified prescription sharing, access to the European Health Insurance Card, and secure patient identification across EU member states. Healthcare is one of the regulated private sectors subject to the wallet acceptance obligation from 24 December 2027 under Article 5f of the regulation. For healthcare providers and pharmaceutical organisations, this creates both a compliance obligation and an opportunity to reduce administrative burden in patient-facing processes.
How ready are EU member states for the 24 December 2026 deadline?
Readiness across EU member states varies considerably. Some countries, particularly those in the Nordic and Baltic regions, entered 2025 with more mature national digital identity infrastructure and active participation in the large-scale pilot programmes. It is important to distinguish, however, between an existing national eID system and a certified, notified EUDI Wallet. These are not the same thing, and the status of individual national wallets changes frequently. Organisations should verify the current certification and notification status of any specific national wallet using authoritative sources immediately before making implementation decisions.
The large-scale pilots that ran from April 2023 to 2025 were instrumental in testing real-world use cases across multiple countries. The four consortia each had a distinct focus: EWC covered Digital Travel Credentials, payments, and organisational digital identity; POTENTIAL covered government services, bank account opening, SIM registration, mobile driving licences, remote qualified signing, and ePrescriptions; NOBID focused on payments; and DC4EU addressed education and social security. A second wave of pilots started in 2025, with WE BUILD focusing on business wallets and payments, and APTITUDE covering travel, ticketing, vehicle registration, and payments. These programmes have produced practical insights on interoperability, user experience, and technical standards that are now feeding into national rollout plans.
The honest picture is that not every member state will have a fully operational, widely adopted EUDI Wallet in the hands of every citizen by 24 December 2026. The legal obligation by that date is to have at least one certified wallet available and to ensure public sector acceptance, but broader adoption, private sector integration, and full cross-border interoperability will continue to develop through 2027 and beyond. A certified wallet from one member state is intended to be usable with an appropriate relying party in another member state, but this does not mean that every use case will be immediately available everywhere, that national registration requirements disappear, or that sector-specific legislation ceases to apply. For organisations operating across multiple EU markets, this uneven readiness means building flexible systems that can accommodate both wallet-based and traditional identity verification methods during the transition period. Plan for a phased rollout rather than a single European go-live moment.
What should organisations do now to prepare for eIDAS 2.0?
Organisations should treat the 24 December 2026 and 24 December 2027 deadlines as the starting points for a broader identity infrastructure transition. The most important immediate actions are assessing current identity verification processes, identifying where wallet acceptance is legally required or commercially advantageous, and beginning technical integration work now.
Here is a practical sequence of steps to follow:
- Map your identity touchpoints: Identify every process in your organisation that involves identity verification, authentication, or document signing. These are the areas where the EUDI Wallet will have direct impact.
- Assess your compliance obligations: Determine whether your organisation falls into an obligated category under eIDAS 2.0, as a public body subject to the 24 December 2026 legal deadline, or as a regulated private sector organisation subject to the 24 December 2027 acceptance obligation under Article 5f, and check sector-specific regulations such as AML or KYC requirements that intersect with the wallet framework. Remember that the legal deadline is a deadline, not a predicted launch date, and that certification, notification, and operational interoperability status of the wallets relevant to your markets must be verified separately.
- Evaluate your technical readiness: Review whether your current systems can accept verifiable credentials and integrate with wallet-based flows. Many legacy systems will require updates or middleware to connect to EUDI Wallet infrastructure. The credential formats prescribed in the Architecture and Reference Framework (ARF) are mdoc and SD-JWT VC, with ISO/IEC 18013-5 for proximity presentation, ISO/IEC TS 18013-7 for online presentation, OID4VCI for issuance, and OID4VP for presentation.
- Register as a relying party: Under CIR (EU) 2025/848 of 6 May 2025, every relying party must register with the national authority of its member state of establishment before requesting wallet data. Registration specifies per intended use which attributes and attestations will be requested. The wallet checks each request against this registered scope. A vendor that processes wallet data on your behalf does not become the relying party; the registration obligation rests with the organisation delivering the service to the end user.
- Plan for reusable identity: Design your onboarding and verification flows with reusability in mind. If a customer has already been verified elsewhere, your system should be able to accept and trust that credential. Each time a user presents credentials from the wallet, they approve that specific presentation individually.
- Build for interoperability: The EUDI Wallet ecosystem spans multiple member states and sectors. Ensure your architecture aligns with the implementing acts, which are legally binding, and with the technical elaboration in the ARF. Note that relying-party registration remains connected to the applicable national registration framework in each member state.
The organisations that act now will be better positioned to turn compliance into a competitive advantage, reducing friction for customers while meeting regulatory expectations. Explore TrustTech’s implementation approach to understand how to translate these steps into a concrete roadmap.
How TrustTech helps organisations prepare for eIDAS 2.0
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 addresses the specific technical and compliance requirements that arise when moving to wallet-based identity verification. Here is what it delivers in practice:
- Wallet acceptance across member states: The ID Connector accepts every certified EUDI Wallet regardless of the issuing member state, so relying parties do not need separate integrations per national wallet solution
- Verification against trusted lists: The connector checks issuer signatures against the relevant national trusted lists, which form part of the EU List of Trusted Lists (LOTL), and validates wallet unit attestations to confirm that presenting wallets run on certified wallet solutions
- Revocation checking: The connector checks the revocation status of credentials through the issuer’s status information as part of the verification flow
- Registered attribute scope management: The connector enforces the attribute scope registered under CIR (EU) 2025/848, ensuring that only the attributes specified in the relying party’s registration are requested
- Reusable identity data: Cryptographically verified identity data can be reused across services, reducing repeated verification for returning users
- Qualified signing via a connected QTSP: Where qualified electronic signatures are required, the ID Connector connects to a qualified trust service provider, enabling signing flows within the same integration
If your organisation needs to understand what eIDAS 2.0 means for your specific situation and how to turn that into a concrete action plan, contact TrustTech to start the conversation.