Yes, your organisation should start preparing for the EUDI Wallet now. Member States are legally required to make the European Digital Identity Wallet available to all citizens, residents, and businesses, with 24 December 2026 as the binding legal deadline under eIDAS 2.0. Waiting until wallets are live before acting puts your organisation at a serious disadvantage. This article walks through the key deadlines, the sectors most immediately affected, what preparation actually looks like in practice, and how to take your first concrete steps.
What are the key deadlines organisations need to know about the EUDI Wallet?
The most important legal deadline is 24 December 2026, by which all EU Member States are legally obligated to provide an EUDI Wallet to every citizen, resident, and business. This is a binding requirement under eIDAS 2.0, which amends Regulation (EU) 910/2014 to close gaps in cross-border digital identity and extend the rules to the private sector.
It is important to understand what this deadline does and does not mean. It establishes the legal obligation for Member States to make wallets available, but it does not guarantee that every national wallet will have reached the same level of maturity on that date, or that every possible cross-border use case will be fully operational throughout Europe from day one. National rollout, certification and notification of wallets, operational interoperability, and acceptance by relying parties are distinct stages that will develop in phases across Member States.
From 24 December 2026, public sector bodies must accept notified EUDI Wallets for online services that require electronic identification. A separate obligation applies to the private sector: from 24 December 2027, Article 5f of eIDAS 2.0 requires relevant regulated private sector organisations to accept EUDI Wallet credentials where strong user authentication is legally or contractually required. The sectors named in Article 5f include banking and financial services, healthcare, telecoms, energy, transport, education, social security, drinking water, postal services, digital infrastructure, and digital services. 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. Very Large Online Platforms are covered by a separate provision of Article 5f: for VLOPs, the obligation applies where the platform requires user authentication, on the voluntary request of the user and for the minimum necessary data.
The exact technical requirements for relying parties are elaborated in implementing acts. CIR (EU) 2025/848, adopted on 6 May 2025, establishes the registration requirements for wallet relying parties. Under that regulation, a relying party must register with the national competent authority of its Member State of establishment before it can request wallet data. Registration is per intended use: the relying party declares which attributes and attestations it will request, and the wallet checks each request against that registered scope. The implementing acts are legally binding; the Architecture and Reference Framework provides the technical elaboration of those requirements.
Large-scale pilots involving more than 350 entities across 26 Member States, Norway, Iceland, and Ukraine tested the wallet across real-world scenarios between April 2023 and 2025. The technical architecture and reference implementation are publicly available. The foundations are already in place, and the transition from pilot to live deployment is well underway ahead of the 2026 deadline.
Which sectors and use cases will be affected first?
The sectors most immediately affected are those already operating under strict identity verification and data exchange requirements. Financial services, government, healthcare, and telecommunications are at the front of the queue, both because they featured prominently in the large-scale pilots and because their regulatory environments make digital identity adoption both urgent and impactful.
The four large-scale pilot consortia explored concrete use cases that give a clear picture of where the EUDI Wallet will be applied first. The POTENTIAL consortium piloted government services, bank account opening, SIM card registration, mobile driving licences, remote qualified signing, and e-prescriptions. The EWC consortium focused on digital travel credentials, payments, and organisational digital identity. The DC4EU consortium covered education credentials and social security. The NOBID consortium concentrated on payments. A second wave of pilots started in 2025: WE BUILD focuses on business wallets and payments, and APTITUDE covers travel, ticketing, vehicle registration, and payments.
If your organisation operates in financial services or healthcare, the wallet will affect your onboarding, verification, and data exchange processes sooner than most. Government organisations face direct obligations as both issuers and verifiers of identity credentials.
What does preparing for the EUDI Wallet actually involve?
Preparing for the EUDI Wallet means understanding how the wallet will interact with your existing identity verification, onboarding, and data exchange processes, and then adapting your systems and compliance frameworks to accept and issue verifiable credentials. It is a set of interconnected workstreams spanning technology, compliance, and governance.
Governance of the EUDI Wallet is a shared responsibility. The European Commission manages the legal framework and adopts implementing acts. Member States provide or mandate wallet solutions, certify and notify them, and supervise actors within their jurisdiction. The European Digital Identity Cooperation Group supports cooperation and cross-border alignment. National competent authorities and registrars, wallet providers, issuers of Person Identification Data and attestations, qualified trust service providers, and relying parties each carry distinct roles and obligations. Understanding where your organisation sits within this structure is an essential part of preparation.
In practical terms, preparation involves several distinct activities:
- Regulatory mapping: Understand which eIDAS 2.0 obligations apply to your organisation, whether as a relying party, a trust service provider, or both. Public sector bodies face the 24 December 2026 acceptance deadline; regulated private sector organisations in the named sectors face the 24 December 2027 deadline under Article 5f. Relying-party registration under CIR (EU) 2025/848 must be completed with the national competent authority of your Member State of establishment before you can request wallet data.
- Technical assessment: Review your current identity infrastructure to identify what needs to be updated or replaced to support verifiable credentials and wallet-based authentication. The EUDI Wallet uses mdoc and SD-JWT VC as credential formats, ISO/IEC 18013-5 for proximity presentation, ISO/IEC TS 18013-7 for online presentation, OID4VCI for issuance, and OID4VP for presentation.
- Use case prioritisation: Identify which of your customer or citizen journeys will be most affected and where the wallet creates the greatest compliance obligation or business opportunity.
- Interoperability planning: Ensure your systems can communicate with the common toolbox architecture that underpins EUDI Wallets across Member States. Cross-border interoperability at European level covers wallet certification and credential recognition, while sector-specific legislation and national registration requirements continue to apply in each Member State. Your organisation must be able to accept every relevant notified wallet, regardless of which wallet provider issued it.
- Privacy and data minimisation review: The wallet is built on selective disclosure, meaning users share only the data that is strictly necessary for each interaction. Your data collection practices may need to be revised accordingly. Note that approving a data request in the wallet is distinct from consent as a legal basis under the GDPR: your organisation needs its own GDPR legal basis for processing the data received.
- Stakeholder alignment: Bring together your compliance, IT, legal, and business teams. EUDI Wallet readiness cuts across all of them.
Preparation is not purely a technology exercise. Organisations that treat it as an IT project alone tend to miss the compliance and governance dimensions that are equally critical for a smooth transition. Explore the available solutions that support this kind of end-to-end readiness.
What happens if an organisation waits too long to prepare?
Organisations that delay EUDI Wallet preparation risk being unable to serve customers or comply with regulatory requirements as wallet-based identity verification becomes the standard across the EU. The longer the wait, the more compressed the implementation timeline becomes, and the higher the cost and risk of a rushed rollout. National rollouts and relying-party obligations will materialise progressively, and organisations that are not ready will face gaps at each stage.
There are several concrete consequences of waiting.
First, your onboarding and verification processes may stop working as expected. If a customer presents a wallet credential and your systems cannot accept it, you lose that interaction entirely. For sectors like banking and healthcare, where identity verification is a legal requirement before service delivery, this is a compliance failure with direct consequences.
Second, competitors who prepare early will offer smoother, faster, and more privacy-respecting digital experiences. The EUDI Wallet is designed to eliminate the need for repeated form-filling and password management. Organisations that can leverage this will have a clear advantage in user experience and trust.
Third, the technical complexity of integration increases when it is done reactively. The architecture and reference implementation are available now, and the organisations that participated in the large-scale pilots have a head start in understanding how the system works in practice. Building on that knowledge early is far more efficient than starting from scratch under deadline pressure.
How should an organisation take its first steps toward EUDI Wallet readiness?
A practical starting point is to identify the customer or citizen journeys in your organisation where identity verification plays a role. Then ask whether those journeys are ready to accept wallet-based credentials, whether your data handling practices align with the wallet’s selective disclosure model, and whether your compliance team has reviewed the eIDAS 2.0 obligations that apply to your sector, including which national competent authority or registrar is relevant to your relying-party registration under CIR (EU) 2025/848.
From there, build a phased roadmap. Prioritise the use cases with the highest regulatory urgency or the greatest business impact, and build from there. Engaging with the open-source reference implementation and the technical specifications published by the European Commission is a practical way to understand what integration will require without committing to a full build immediately.
Connecting with organisations that have already participated in or followed the large-scale pilots can also accelerate your learning curve significantly. Their real-world experience with wallet functionality, interoperability challenges, and user behaviour is far more actionable than reading specifications alone. The resources available on digital identity and wallet readiness can help your team build that foundational understanding quickly.
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 complexity of wallet acceptance so that your teams can focus on the compliance and business decisions. Concretely, the ID Connector covers:
- Wallet acceptance: Accept every relevant notified EUDI Wallet, regardless of the issuing Member State or wallet provider
- Trust management and verification against national trusted lists: Issuer signatures are verified against the relevant national trusted lists, which are consolidated in the EU List of Trusted Lists
- Revocation status checking: The revocation status of each attestation is checked against the issuer’s status information
- Wallet unit attestation validation: Each presenting wallet is confirmed to be running on a certified wallet solution
- Registered attribute scope enforcement: Requests are checked against the scope declared in your relying-party registration, keeping data requests within the bounds of what you have registered under CIR (EU) 2025/848
- Qualified signing: Qualified electronic signing is available via a connected qualified trust service provider
The organisations that will navigate this transition most successfully are those that put the right technical infrastructure in place before the deadlines arrive. Get in touch with TrustTech to discuss where your organisation stands and what your next step toward EUDI Wallet readiness should be.