eIDAS 2.0 and national digital ID programs are related but not the same thing. eIDAS 2.0 is Regulation (EU) 2024/1183, which amends Regulation (EU) 910/2014, and it sets common standards for digital identity across all EU member states. National digital ID programs are country-specific systems that each government has built to serve its own citizens. The key difference is scope: eIDAS 2.0 creates a shared framework that makes digital identities work across borders, whereas national programs typically work only within a single country. This article unpacks the most important questions organizations are asking as both layers of digital identity continue to evolve.
How does eIDAS 2.0 relate to national digital ID programs?
eIDAS 2.0 sits above national digital ID programs as an EU-wide regulatory framework. It does not replace national systems but requires member states to bring their existing digital identity infrastructure in line with common European standards. National programs remain the foundation, but eIDAS 2.0 adds a layer of interoperability, legal recognition, and minimum requirements that apply across all member states.
A national digital ID program is built by and for a specific country. It reflects that country’s legal system, technical choices, and administrative priorities. eIDAS 2.0 is the set of rules that ensures these national systems can talk to each other, that citizens can use their national identity credentials in other EU countries, and that businesses operating across borders can rely on a consistent level of assurance.
The most visible outcome of eIDAS 2.0 is the European Digital Identity Wallet, commonly called the EUDI Wallet. Every EU member state is required to make a wallet available to all citizens, residents, and businesses by 24 December 2026. This wallet connects to national identity systems but adds cross-border functionality, support for verifiable credentials, and stronger privacy controls. The EUDI Wallet is not a replacement for national ID programs. It is a standardized interface built on top of them.
Governance of the EUDI Wallet framework is a shared responsibility. The European Commission manages the legal framework and adopts implementing acts that contain the 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 between member states. National competent authorities, wallet providers, issuers of Person Identification Data and attestations, qualified trust service providers, and relying parties each carry distinct roles within this structure. No single central European authority operationally manages all EUDI Wallets.
What does eIDAS 2.0 require that national programs don’t?
eIDAS 2.0 introduces several requirements that go beyond what most national digital ID programs currently offer. The most significant is mandatory cross-border recognition: any digital identity issued under eIDAS 2.0 must be legally accepted by public sector services across all EU member states. National programs, by contrast, are typically only valid within their own country.
Beyond cross-border recognition, eIDAS 2.0 introduces a number of obligations that national programs do not always address:
- Wallet availability: Member states must provide a free EUDI Wallet to every citizen, resident, and business by 24 December 2026. Public sector bodies must also accept notified wallets as a means of identification from that date. The 24 December 2026 deadline is a legal obligation for member states, not a predicted launch date. Practical interoperability and national rollout are expected to develop in phases, and organizations should plan accordingly.
- Private sector acceptance: Certain regulated sectors, including banking and financial services, healthcare, telecoms, energy, transport, education, social security, drinking water, postal services, digital infrastructure, and digital services, must accept EUDI Wallet credentials for authentication where strong user authentication is legally or contractually required. Very large online platforms with more than 45 million users in the EU fall under a separate provision of Article 5f: for those platforms, the obligation applies where the platform requires user authentication, on the user’s voluntary request and for the minimum necessary data. This private sector obligation takes effect on 24 December 2027. Micro and small enterprises with fewer than 50 employees and an annual turnover or balance sheet total not exceeding 10 million euros are exempt. National programs rarely impose equivalent obligations on private companies.
- Qualified Electronic Attestations of Attributes (QEAAs): eIDAS 2.0 creates a new category of certified digital attestations, such as diplomas, professional licenses, and medical data, that carry legal weight across the EU. The framework also distinguishes Public Body-issued Electronic Attestations of Attributes (PuB-EAAs) and non-qualified EAAs, each with different legal status and governance requirements.
- Selective disclosure: Users must be able to share only the specific data a service needs, for example confirming they are over 18 without revealing their full date of birth. This level of data minimization is not always built into national systems.
- Interoperability standards: eIDAS 2.0 mandates technical standards to ensure wallets and credentials from different countries work together. The implementing acts contain the legally binding requirements; the Architecture and Reference Framework provides the technical elaboration of those requirements.
National programs may meet some of these requirements already, but eIDAS 2.0 makes them legally binding and applies them uniformly across the EU.
Which countries already have national digital ID programs?
Most EU member states already have some form of national digital identity infrastructure, though maturity and adoption levels vary significantly. Countries such as Estonia, the Netherlands, Germany, Austria, Belgium, and the Nordic states have well-established national eID systems that have been in use for years. These countries are generally well-positioned to develop EUDI Wallet solutions that build on their existing infrastructure. Having an established national eID system is, however, distinct from having a certified and notified EUDI Wallet. The status of individual national wallets, whether live, in pilot, certified, or notified, is time-sensitive and should be verified against current authoritative sources before any operational decisions are made.
Estonia is often cited as a leading example, with its X-Road data exchange platform and national eID card forming the backbone of a highly digitized public sector. The Netherlands has existing digital identity infrastructure including DigiD, an authentication mechanism used by citizens, and eHerkenning, used by businesses, both of which are widely used for government and regulated sector interactions. Dutch wallet development builds on this existing infrastructure. Austria has the ID Austria digital identity infrastructure, which supports eIDAS-compliant identity verification. It is important to distinguish these existing national eID systems from EUDI Wallets: a national eID system and a country’s EUDI Wallet are separate things, even where one builds on the other.
Outside the EU, countries like Norway and Iceland participate in eIDAS as part of the European Economic Area and were involved in large-scale pilot programs for the EUDI Wallet. The NOBID Consortium, which included Nordic and Baltic countries alongside Italy and Germany, piloted the use of the EUDI Wallet for cross-border payment authorization. That first wave of four Large Scale Pilots ran from April 2023 to 2025 and has concluded. A second pilot wave started in 2025, with WE BUILD focusing on business wallets and payments, and APTITUDE covering travel, ticketing, vehicle registration, and payments.
Countries with less mature national ID infrastructure face a steeper path to eIDAS 2.0 compliance, but the regulation provides a common technical baseline through the Architecture and Reference Framework and an open-source wallet prototype that member states can build from. For organizations operating in government services, understanding which national systems are already in place in your operating countries is an important first step, as is monitoring the certification and notification status of national wallets as rollout progresses.
Can organizations accept both eIDAS 2.0 and national ID credentials?
Yes, and in most cases organizations will need to do exactly that for the foreseeable future. eIDAS 2.0 and national digital ID programs will coexist during a transition period, and not all users will have adopted the EUDI Wallet immediately. Organizations should design their identity acceptance policies to support both layers.
From a technical standpoint, this means building systems that can handle multiple credential types: national eID schemes, EUDI Wallet credentials, and potentially other trusted identity sources depending on the sector and use case. The EUDI Wallet framework is designed so that a certified wallet from one member state can be used with an appropriate relying party in another member state. This does not mean that every use case will immediately be available in every member state, that national registration requirements disappear, or that sector-specific legislation is overridden. Under CIR (EU) 2025/848, adopted on 6 May 2025, a relying party must register with the national authority of its member state of establishment before requesting wallet data, and must register per intended use which attributes and attestations it will request. The wallet checks requests against this registered scope. A relying party must be able to accept every relevant notified wallet, regardless of which provider issued it.
For regulated sectors such as financial services and healthcare, accepting eIDAS 2.0 credentials alongside national ID schemes can simplify compliance. A single verified credential from an EUDI Wallet can support Know Your Customer processes, reduce repeated identity checks, and enable reusable onboarding flows. Note that reuse of KYC data is governed by AML regulation, not by eIDAS 2.0 itself. Organizations that invest in flexible identity acceptance infrastructure now will be better positioned as wallet adoption increases across Europe.
What should organizations do to prepare for eIDAS 2.0?
Organizations should start by mapping their current identity processes against what eIDAS 2.0 will require. This means identifying where identity verification happens today, what assurance levels are needed, and where cross-border interactions or regulated sector requirements will trigger new obligations under the regulation.
A practical preparation approach involves several steps:
- Assess your current identity infrastructure: Understand which national eID schemes you currently rely on, what assurance levels they provide, and where gaps exist against eIDAS 2.0 requirements. Distinguish between existing national eID systems and EUDI Wallets, and monitor the certification and notification status of relevant national wallets as rollout develops.
- Identify which obligations apply to your organization: Not all organizations face the same requirements. The mandatory private sector acceptance obligation under Article 5f of eIDAS 2.0 applies specifically to regulated sectors such as banking and financial services, healthcare, telecoms, energy, transport, education, social security, drinking water, postal services, digital infrastructure, and digital services, and only where strong user authentication is legally or contractually required. Very large online platforms with more than 45 million users in the EU fall under a separate provision of Article 5f. Micro and small enterprises with fewer than 50 employees and an annual turnover or balance sheet total not exceeding 10 million euros are exempt. The private sector obligation takes effect on 24 December 2027. Public sector bodies face an earlier obligation tied to the 24 December 2026 deadline, by which point they must accept notified wallets as a means of identification. The legal deadline and the practical rollout of interoperable national wallets may not coincide, and planning should account for a phased transition.
- Engage with the EUDI Wallet architecture: Familiarize your technical teams with the Architecture and Reference Framework, which provides the technical elaboration of the requirements set out in the implementing acts. Understanding the technical standards early reduces integration risk later.
- Review your data minimization practices: eIDAS 2.0 places strong emphasis on selective disclosure and user control. Align your data collection practices with these principles now.
- Plan for reusable identity: Design your onboarding and verification flows to accept verified credentials that users have already established elsewhere. This reduces friction, improves conversion, and positions you for a wallet-ready future.
Organizations that treat eIDAS 2.0 purely as a compliance exercise tend to miss the broader opportunity. The regulation creates the conditions for faster, more trusted digital interactions that benefit both organizations and their users. Explore the resources available to support your planning process as the regulatory timeline continues to develop.
How TrustTech supports eIDAS 2.0 and national digital identity acceptance
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 organizations in financial services, healthcare, pharma, and government, the ID Connector addresses the practical challenges of operating across both eIDAS 2.0 and national identity frameworks at the same time. Concretely, the ID Connector supports:
- Secure onboarding flows that accept national eID credentials and EUDI Wallet credentials within a single integration
- Verification against national trusted lists, which are brought together in the EU List of Trusted Lists, covering issuer signature verification, revocation status checks, and wallet unit attestation validation
- Enforcement of the registered attribute scope per intended use, so that only the data a relying party has registered to request is presented
- Reusable identity infrastructure that reduces repeated verification across touchpoints
- Qualified signing via a connected qualified trust service provider, meeting eIDAS 2.0 assurance requirements
- Cross-border interoperability support for organizations operating across multiple EU member states
- Compliance-ready architecture built for GDPR, AML, KYC, and eIDAS 2.0
Get in touch with TrustTech to discuss your specific situation and find out how the ID Connector fits your digital identity requirements.