The eIDAS 2.0 regulatory timeline sets out a series of phased deadlines that EU member states must meet between 2024 and 2027. The central legal obligation is to make the European Digital Identity Wallet available to all citizens, residents, and businesses by 24 December 2026. These deadlines apply to all 27 EU member states, though the pace of implementation varies considerably in practice. The sections below break down what each deadline means, who it affects, and what organizations should be doing now to stay ahead.
What are the key eIDAS 2.0 implementation deadlines for member states?
eIDAS 2.0, formally Regulation (EU) 2024/1183, amends Regulation (EU) 910/2014 and entered into force on 20 May 2024. From that point, member states have been working against a structured set of implementation deadlines. The most widely discussed deadline is 24 December 2026, by which point every EU member state must make a functioning European Digital Identity Wallet (EUDI Wallet) available to any citizen, resident, or business that wants one. That legal deadline is an outer limit, not a predicted launch date, and it does not guarantee that every national wallet will reach the same level of maturity on that date, or that every possible cross-border use case will be fully operational throughout Europe from that moment. Beyond the wallet itself, member states also face obligations around certifying and notifying their wallet solutions, adopting implementing acts, and ensuring interoperability across borders.
Here is a summary of the key milestones in the eIDAS 2.0 timeline:
- 20 May 2024: Regulation (EU) 2024/1183 entered into force, amending Regulation (EU) 910/2014.
- Late 2024: The European Commission adopted the first five core implementing acts. These acts are legally binding and start the relevant 24-month period for certain obligations. The Architecture and Reference Framework (ARF) provides the technical elaboration of those requirements.
- 6 May 2025: The Commission adopted CIR (EU) 2025/848, establishing the registration framework for wallet relying parties. A relying party must register with the national authority of its member state of establishment before it can request wallet data, and must register per intended use which attributes and attestations it will request.
- 2025: The first four Large Scale Pilots, launched in April 2023 with over 350 entities from 26 member states, concluded their testing phase. Their findings directly informed the technical specifications and ARF that underpin the EUDI Wallet.
- 24 December 2026: The legal deadline by which member states must make the EUDI Wallet available to all eligible users, and by which public sector bodies must accept notified wallets for online services requiring electronic identification. Practical interoperability and national rollout maturity may continue to develop in phases beyond this date.
- 24 December 2027: The acceptance obligation under Article 5f of the amended regulation takes effect for relevant regulated private sector entities where strong user authentication is required by law or contract. This covers sectors including banking and financial services, healthcare, telecoms, energy, transport, education, social security, drinking water, postal services, digital infrastructure, and digital services. Micro and small enterprises with fewer than 50 employees and an annual turnover or balance sheet total of no more than 10 million euros are exempt.
It is worth noting that the implementing acts published by the Commission cover a wide range of technical and procedural requirements, from qualified electronic signatures to cross-border identity matching. Member states and organizations operating in regulated sectors need to track the full set of obligations that flow from the regulation. Governance across this framework 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 (EDICG) supports cooperation and cross-border alignment; and qualified trust service providers, wallet providers, issuers of Person Identification Data, and relying parties each carry their own distinct obligations.
Which eIDAS 2.0 obligations apply first, and which come later?
The earliest eIDAS 2.0 obligations focused on governance and technical preparation. In the period immediately following the regulation entering into force, member states were required to participate in the development of the Architecture and Reference Framework, engage with the EDICG, and begin aligning their national electronic identification schemes with the new requirements. Member states must also certify and notify their wallet solutions before those wallets can be formally recognised under the framework. These foundational steps had to happen before any wallet could be issued.
The obligations that come later, particularly from 24 December 2026 onward, are more visible to end users and organizations. Once wallets are live and notified, public sector bodies will be required to accept them for online services where electronic identification is required. From 24 December 2027, the acceptance obligation under Article 5f extends to regulated private sector entities in the sectors listed above, where strong user authentication is required by law or contract. Very large online platforms (VLOPs) are covered by a separate provision of Article 5f: for VLOPs, the obligation applies where the platform requires user authentication, on voluntary request from the user and for the minimum necessary data. The condition relating to legally or contractually required strong authentication does not apply to VLOPs. It is important to note that relying party registration under CIR (EU) 2025/848 remains a prerequisite for requesting wallet data, and sector-specific legislation continues to apply alongside eIDAS 2.0. Financial services, healthcare providers, and government agencies are among the sectors most directly affected by these obligations.
For organizations that have been monitoring from the sidelines, this phased structure is an opportunity. The period between now and the full rollout of relying party obligations is the right time to assess technical readiness, update compliance frameworks, and begin testing wallet-based interactions in a controlled environment. Organizations should not wait for a single European go-live moment, as national rollouts will develop at different paces.
What happens if a member state misses an eIDAS 2.0 deadline?
If a member state fails to meet an eIDAS 2.0 deadline, the European Commission can initiate infringement proceedings under EU law. This is the standard enforcement mechanism for EU regulations, and it can ultimately result in financial penalties imposed by the Court of Justice of the European Union. Beyond the legal consequences, a member state that misses the 24 December 2026 wallet deadline would also face practical problems: its citizens and businesses would lack access to a tool that other EU member states are already using for cross-border services.
In practice, the Commission has shown a preference for structured cooperation over immediate enforcement, particularly where technical complexity is the cause of delay. The Large Scale Pilots were designed precisely to reduce the risk of member states arriving at the deadline unprepared. The political and reputational pressure to deliver on time is significant, and the 24 December 2026 deadline has been consistently reinforced as a firm legal obligation.
For organizations operating across multiple EU markets, a member state delay does not eliminate the obligation to prepare. If your organization needs to accept EUDI Wallets as part of your digital services, your internal readiness cannot wait for the slowest member state to catch up.
How does the eIDAS 2.0 timeline affect organizations that rely on digital identity services?
The eIDAS 2.0 compliance deadline is a concern for organizations as much as for governments. Organizations that use digital identity verification as part of their services, whether for onboarding, authentication, contract signing, or regulatory compliance, need to treat the relevant deadlines as their own. Once EUDI Wallets are live and notified, users will expect to be able to use them. Organizations that cannot accept wallet-based credentials risk friction, drop-off, and potential non-compliance with sector-specific requirements.
The practical implications differ by sector. Financial services organizations face pressure from the intersection of eIDAS 2.0 with AML, KYC, PSD2, and Strong Customer Authentication requirements. Healthcare and pharmaceutical organizations need to prepare for wallet-based consent and identity verification flows. Government service providers have both a mandate to offer wallet-compatible services from 24 December 2026 and an opportunity to reduce the cost and friction of identity-intensive processes.
Organizations should be asking themselves three questions now. First, which of your current identity processes will be affected when users start presenting EUDI Wallets? Second, are your systems technically capable of verifying wallet credentials and processing the data they contain? Third, do your compliance frameworks reflect the obligations that eIDAS 2.0 places on relying parties, including the registration requirements under CIR (EU) 2025/848 and any applicable sector-specific rules? The answers to these questions will shape your implementation roadmap for the next 12 to 18 months.
Are all EU member states on the same eIDAS 2.0 schedule?
In legal terms, yes. The eIDAS 2.0 regulation applies uniformly across all 27 EU member states, and 24 December 2026 is a shared legal deadline. In practical terms, member states are at very different stages of readiness. Some countries have moved quickly and are already building toward wallet-compatible infrastructure, while others are still working through the technical and governance steps needed to meet the deadline. It is important to distinguish between a country’s existing national digital identity system and a certified, notified EUDI Wallet: the two are not automatically the same thing, and current national wallet status should be verified against authoritative sources before drawing conclusions about any specific country’s readiness.
This variation matters for organizations operating across borders. If you serve customers in multiple EU countries, you cannot assume a uniform rollout. Some users will have access to a functioning EUDI Wallet earlier than others, and the maturity and feature set of national wallet implementations may differ, at least initially. The interoperability requirements built into eIDAS 2.0 are designed to address this over time, but the transition period will require flexibility. Cross-border use means that a certified wallet from one member state can be used with an appropriate relying party in another member state, but this does not mean that every use case will immediately be available everywhere, that national registration requirements disappear, or that sector-specific legislation ceases to apply.
Norway, Iceland, and Ukraine also participated in the Large Scale Pilots, reflecting the broader relevance of the EUDI Wallet framework beyond the strict EU membership boundary. Organizations with operations in these countries should monitor how the framework is adopted there, as alignment with EU standards is likely even outside the formal regulatory scope.
Building systems that are wallet-ready in principle, and capable of accepting every certified wallet regardless of the issuing member state, is the most resilient strategy for organizations with cross-border operations.
How the ID Connector supports organizations navigating the eIDAS 2.0 timeline
Meeting the eIDAS 2.0 regulatory timeline requires practical action: updating systems, aligning compliance frameworks, and building the technical infrastructure to work with EUDI Wallets and verifiable credentials.
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.
Here is what the ID Connector does in the context of the eIDAS 2.0 timeline:
- Wallet acceptance across member states: The ID Connector enables your organization to accept any notified EUDI Wallet, regardless of which member state issued it, so you are not dependent on a single national implementation being ready.
- Verification against trusted lists: The ID Connector verifies issuer signatures against the relevant national trusted lists, which are brought together in the EU List of Trusted Lists (LOTL), checks revocation status using issuer-provided status information, and validates the wallet unit attestation to confirm that the presenting wallet runs on a certified wallet solution.
- Registered attribute scope: The ID Connector enforces the attribute and attestation scope that your organization has registered under CIR (EU) 2025/848, so that data requests stay within the boundaries of your registered intended use.
- Reusable verified identity data: Verified identity data can be reused securely across interactions, reducing friction for users and cost for organizations, without creating new linkability risks.
- Qualified signing via a connected QTSP: Where your workflows require qualified electronic signatures, the ID Connector connects to a qualified trust service provider, so that signing is handled within the eIDAS 2.0 framework.
The ID Connector is built for financial services, healthcare, pharma, and government organizations that need to be operationally ready before 24 December 2026 for public sector obligations and before 24 December 2027 for the private sector acceptance obligation under Article 5f. Get in touch with TrustTech to find out how the ID Connector fits into your organization’s implementation roadmap.