There are quite a few misconceptions about eIDAS 2.0, and they are slowing down organizations that should already be preparing. The most common ones include the belief that eIDAS 2.0 only affects governments, that the EUDI Wallet is compulsory for all citizens, and that compliance means rebuilding everything from scratch. None of these are accurate. This article addresses the six most frequently misunderstood aspects of eIDAS 2.0 and the European Digital Identity framework, so you can cut through the noise and focus on what actually matters for your organization.
Does eIDAS 2.0 only apply to government organizations?
No, eIDAS 2.0 explicitly extends beyond the public sector. Unlike the original eIDAS regulation, Regulation (EU) 910/2014, which eIDAS 2.0 amends through Regulation (EU) 2024/1183, the original framework focused primarily on cross-border recognition of national electronic ID systems between Member States. eIDAS 2.0 opens the framework to private sector organizations as well. If your organization operates in banking, healthcare, telecommunications, or any other regulated industry, eIDAS 2.0 is directly relevant to you.
The European Digital Identity Wallet is designed to be accepted by both public authorities and private service providers. Regulated private organizations that are legally required to apply strong user authentication, such as banks conducting customer due diligence or healthcare providers managing patient access, will be required to accept wallet-based credentials from 24 December 2027 onwards, as set out in Article 5f of the regulation. This obligation applies within contexts where strong authentication is legally or contractually required, and it covers a defined set of sectors including banking and financial services, healthcare, telecommunications, energy, transport, education, social security, drinking water, postal services, digital infrastructure, and digital services. Very large online platforms with more than 45 million users in the EU fall under a separate provision of Article 5f: for these platforms, the obligation applies where the platform requires user authentication, on the voluntary request of the user and for the minimum necessary data. The regulation creates new obligations and opportunities for private businesses to participate in the broader digital identity ecosystem.
For sectors like financial services and healthcare, eIDAS 2.0 is not a distant government project. It is a regulatory shift that directly affects how you onboard customers, verify identity, and exchange trusted data across borders.
Is the EUDI Wallet mandatory for all citizens?
No, the EUDI Wallet is not mandatory for citizens to use. What is mandatory is that every EU Member State must make at least one certified wallet available to all citizens, residents, and businesses by 24 December 2026. The distinction matters: Member States are legally obligated to meet this deadline, but individuals are free to choose whether they use the wallet.
The design principle behind the wallet is user control and voluntary adoption. Citizens can store digital documents such as driving licences, educational credentials, prescriptions, and government-issued identity data in a single secure app. They decide what to share, with whom, and when. Nothing is shared without their explicit approval of each individual presentation request, and users can disclose only the minimum necessary information, for example, confirming their age without revealing their full date of birth. This is made possible through selective disclosure of individual attributes, such as an “over 18” attribute, without requiring the full date of birth to be shared.
This voluntary nature is one of the wallet’s strengths from a privacy perspective. It avoids the creation of a mandatory digital identity system while still building the infrastructure that allows anyone who wants to use it to do so conveniently and securely across all EU Member States. Governance of the framework is a shared responsibility: the European Commission manages the legal framework and adopts implementing acts, Member States provide or mandate wallet solutions and supervise actors within their jurisdiction, and the European Digital Identity Cooperation Group supports cross-border alignment and cooperation between national competent authorities.
Does eIDAS 2.0 replace all existing national eID systems?
No, eIDAS 2.0 does not replace existing national eID systems. National schemes such as DigiD in the Netherlands, ID Austria, or the separate BankID systems in Sweden and Norway remain in place as distinct national infrastructure. What eIDAS 2.0 does is build a common layer on top of these national systems, enabling them to interoperate across borders and connect into the European Digital Identity Wallet framework.
The original eIDAS regulation already allowed Member States to notify and mutually recognize each other’s national eID schemes. The problem was that participation was optional, which led to significant inconsistency across Europe. Some countries had mature, widely used digital identity systems, while others had limited or no notified schemes at all.
eIDAS 2.0 addresses this by making it mandatory for every Member State to offer a wallet that connects to their national identity infrastructure. It is important to distinguish an existing national eID system from an EUDI Wallet: a country’s existing digital identity infrastructure is not automatically its EUDI Wallet. For example, DigiD is an authentication mechanism in the Netherlands, not an issuer of wallet attestations, and Dutch wallet development builds on existing infrastructure including DigiD and eHerkenning without simply relabelling those systems. National systems evolve and feed into the wallet architecture, but the wallet itself must be separately certified and notified under the eIDAS 2.0 framework.
Are verifiable credentials and the EUDI Wallet the same thing?
No, verifiable credentials and the EUDI Wallet are not the same thing, although they are closely related. Attestations are structured digital representations of trusted information that can be cryptographically verified. The EUDI Wallet is the application, or container, that stores and presents those attestations. Within the eIDAS 2.0 framework, the Architecture and Reference Framework specifies mdoc and SD-JWT VC as the credential formats for the EUDI Wallet, with ISO/IEC 18013-5 for proximity presentation and OID4VP for online presentation.
Think of it this way: an attestation is the format in which your diploma, driving licence, or identity data is encoded. The EUDI Wallet is the secure app on your device that holds those attestations and lets you share them selectively with a service provider or authority. One is the standard, the other is the tool built on that standard.
Understanding this distinction matters for organizations building or integrating with digital identity systems. You need to understand both layers: the technical specification of the attestations themselves and the wallet infrastructure through which they are exchanged. The Architecture and Reference Framework developed by the eIDAS Expert Group provides the technical elaboration of the requirements set out in the implementing acts and defines how these components work together. The first four Large Scale Pilots, which ran from April 2023 to 2025, tested exactly this interplay in real-world scenarios across 26 Member States. 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.
Is eIDAS 2.0 only relevant once fully enforced?
No, waiting for full enforcement before acting is one of the most costly mistakes an organization can make. eIDAS 2.0 is already shaping procurement decisions, technology investments, and compliance roadmaps across Europe. Organizations that treat it as a future concern are already falling behind those that are preparing now.
There are several concrete reasons to act before enforcement deadlines arrive:
- Integration takes time. Connecting your existing systems to wallet-based identity flows, attestations, and trust service providers is not a quick project. Starting early gives you room to test, iterate, and get it right.
- The first four Large Scale Pilots generated technical specifications and reference implementations between 2023 and 2025. This material is publicly available and gives early movers a significant head start.
- Regulatory overlap is real. eIDAS 2.0 intersects with AML, KYC, GDPR, and PSD2 requirements. Organizations that align their compliance programs early avoid the cost of retrofitting later.
- Competitive advantage is real. Faster, wallet-compatible onboarding reduces drop-off rates and builds customer trust before your competitors catch up.
24 December 2026 is the legal deadline by which every Member State must have at least one certified EUDI Wallet available, and public authorities must be able to accept it as a means of identification for online services requiring electronic identification. This legal deadline is an outer limit, not a predicted launch date, and practical interoperability and national rollout are likely to develop in phases. Organizations should plan for a graduated reality rather than a single European go-live moment. For regulated private organizations in scope of Article 5f, the acceptance obligation applies from 24 December 2027. Early preparation is about being operationally ready as your customers and partners increasingly expect wallet-compatible interactions.
Does eIDAS 2.0 compliance mean starting from scratch?
No, eIDAS 2.0 compliance does not require organizations to throw out their existing identity infrastructure and rebuild from zero. In most cases, the goal is to extend and connect what you already have. Existing identity verification flows, trust service integrations, and compliance processes can often be adapted.
The key shift eIDAS 2.0 introduces is interoperability and reusability. The new framework enables verified identity data to be reused across organizations and borders. A customer who has already been verified by their bank or government can bring that verified status to your platform without repeating the entire process. This reduces friction, lowers costs, and improves the user experience. Cross-border reuse operates within the EUDI Wallet framework’s defined scope: sector-specific legislation and national registration requirements continue to apply, and not every attestation will automatically carry the same legal consequence in every Member State.
For organizations already working with qualified trust service providers, electronic signatures, or existing eID integrations, the path forward is largely one of alignment and extension. You assess what you have, identify the gaps relative to eIDAS 2.0 requirements, and build toward wallet readiness in a structured way.
One concrete step is registering as a relying party. Under CIR (EU) 2025/848, adopted on 6 May 2025, any organization that wants to request data from a EUDI Wallet must register with the national authority of its Member State of establishment before doing so. Registration covers the specific attributes and attestations the organization intends to request, per intended use. The wallet checks each presentation request against this registered scope. A relying party must also be prepared to accept every relevant certified wallet, regardless of which Member State issued it or which wallet provider produced it.
How TrustTech helps organizations navigate eIDAS 2.0
Getting eIDAS 2.0 right requires translating complex technical and regulatory requirements into practical steps that fit your organization’s existing systems, sector-specific obligations, and strategic goals.
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 practice for organizations addressing the misconceptions covered in this article:
- Wallet acceptance across all certified wallets: The ID Connector handles acceptance of every notified EUDI Wallet, regardless of provider or Member State, so your organization meets its obligations under Article 5f without building separate integrations for each wallet solution.
- Verification against trusted lists: The ID Connector verifies issuer signatures against the relevant national trusted lists, which are consolidated in the EU List of Trusted Lists, and checks the wallet unit attestation to confirm that the presenting wallet runs on a certified wallet solution.
- Registered attribute scope management: The ID Connector aligns presentation requests with the attributes and attestations registered under CIR (EU) 2025/848, so each request stays within the scope your organization declared to the national authority.
- Reuse of verified identity data: Once a user has presented their attestations, the ID Connector enables that verified data to be reused across interactions within the bounds of your registered scope and applicable law, reducing friction for returning users.
- Qualified signing via a connected QTSP: For workflows that require qualified electronic signatures, the ID Connector connects to a qualified trust service provider, with a complete audit trail built for long-term compliance.
TrustTech built the ID Connector on European digital identity standards and designed it to be eIDAS 2.0 ready from the ground up. Organizations in financial services, healthcare, pharma, and government are among those for whom wallet acceptance and relying party registration are becoming immediate operational requirements. If your organization is ready to move from uncertainty to a clear implementation path, get in touch with our team.