eIDAS 2.0 addresses interoperability between member states by introducing a unified framework built around the European Digital Identity (EUDI) Wallet, mandatory cross-border recognition, and standardised technical specifications that all member states must follow. Unlike the original eIDAS regulation, which allowed significant variation between national systems, eIDAS 2.0 creates binding obligations that close the gaps in cross-border digital identity exchange. The sections below explore exactly how this works in practice and what it means for your organisation.

What mechanisms does eIDAS 2.0 introduce to enable cross-border identity recognition?

eIDAS 2.0 introduces mandatory mutual recognition of national electronic identity schemes across all EU member states, combined with a common technical framework that standardises how identity data is structured, exchanged, and verified. Every member state is now required to offer citizens, residents, and businesses a European Digital Identity Wallet, creating a shared infrastructure for cross-border recognition that the original regulation never achieved.

The original eIDAS regulation from 2014 was a step in the right direction, but it had a fundamental limitation: member states were not required to create interoperable systems, only to recognise notified schemes from other countries. This led to a patchwork of national solutions with very different levels of maturity and coverage.

eIDAS 2.0 changes this by making the EUDI Wallet a legal obligation for all member states. The regulation also introduces a set of implementing regulations covering everything from identity proofing and attribute formats to protocols, interfaces, and certification requirements. These rules ensure that a wallet issued in one country can be read, validated, and trusted in another, without the need for bilateral agreements or custom integrations.

In addition, eIDAS 2.0 opens the framework to the private sector. Qualified and non-qualified electronic attestations of attributes can now be issued by accredited private providers, not just governments. This significantly expands the range of identity data that can flow across borders in a standardised, trusted way.

How does the EUDI Wallet ensure interoperability across different countries?

The EUDI Wallet ensures interoperability through a shared Architecture and Reference Framework (ARF) that defines the technical standards, protocols, and data formats all wallet implementations must comply with. Because every member state must build or certify its wallet against the same specification, wallets from different countries can communicate and exchange verified identity data without custom integration work.

The ARF covers a wide range of technical requirements, including how identity data is structured, how wallets authenticate users, how credentials are presented to relying parties, and how privacy is protected through selective disclosure. Selective disclosure is particularly important for cross-border use: it allows a user to share only the specific attributes a service needs, such as age or nationality, without revealing their full identity profile.

To validate that wallets actually meet these requirements, the regulation introduces a certification scheme for wallet solutions. A wallet that has been certified in one member state is recognised as compliant across the EU. This removes the need for each country to independently verify another country’s implementation.

The four large-scale pilot projects launched in 2023 played a key role in testing this interoperability in practice. With over 350 participating entities from 26 member states, Norway, Iceland, and Ukraine, the pilots tested real-world scenarios ranging from opening a bank account and claiming prescriptions to mobile driving licences and cross-border payments. The insights from these pilots directly informed the technical specifications that are now being implemented across the EU.

What role do trust frameworks and trust lists play in eIDAS 2.0 interoperability?

Trust frameworks and trust lists are the backbone of eIDAS 2.0 interoperability. They create a shared, publicly accessible record of which identity providers, wallet solutions, and trust service providers have been officially recognised and certified. Without this shared infrastructure, a relying party in Germany would have no reliable way to verify whether a credential presented by a user from Portugal actually comes from a trusted source.

Under eIDAS 2.0, each member state maintains a national trusted list that includes certified wallet solutions, qualified trust service providers, and recognised electronic identity schemes. These lists are standardised in format and publicly accessible, meaning any organisation across the EU can check whether a given provider or credential meets the required level of assurance.

The regulation also introduces new trust list entries specifically for wallet ecosystems, including certified wallet relying parties and approved attribute providers. This extends the trust chain beyond just identity providers to cover the full range of entities involved in a digital identity transaction.

For organisations operating in regulated sectors such as financial services or healthcare, trust lists provide a practical compliance tool. Rather than conducting their own due diligence on every identity provider they interact with, organisations can rely on the trusted list as a verified source of truth, reducing both risk and operational overhead.

What are the main interoperability challenges organisations still face under eIDAS 2.0?

Despite the progress eIDAS 2.0 represents, organisations still face real interoperability challenges in 2026. The regulation sets the framework, but implementation timelines, technical readiness, and legacy system constraints vary considerably across member states and industries. Organisations cannot assume that cross-border digital identity exchange will work seamlessly from day one.

Some of the most common challenges include:

• Uneven implementation timelines: While member states are legally required to offer EUDI Wallets, the pace of deployment differs. Some countries are further ahead than others, meaning cross-border use cases may not be fully functional everywhere at the same time.
• Legacy system integration: Many organisations have existing identity and onboarding systems that were not designed with wallet-based credentials in mind. Connecting these systems to the new wallet ecosystem requires technical investment and architectural changes.
• Attribute schema inconsistencies: Even within a shared framework, differences in how attributes are defined and populated at the national level can create friction when credentials are used cross-border.
• Relying party registration and compliance: Organisations that want to accept EUDI Wallet credentials must register as relying parties and meet specific technical and legal requirements. Understanding and completing this process takes time and expertise.
• User adoption and trust: Technical interoperability alone does not guarantee that users will adopt the wallet or that organisations will accept it. Building user confidence in cross-border digital identity takes time and clear communication.

Organisations in government and other regulated sectors face an additional layer of complexity, as they must align their identity processes with both eIDAS 2.0 requirements and sector-specific regulations such as AML, KYC, and GDPR simultaneously.

How should organisations prepare their systems for eIDAS 2.0 interoperability?

Organisations should prepare for eIDAS 2.0 interoperability by starting with a clear assessment of their current identity infrastructure, identifying the gaps between their existing systems and the requirements of the EUDI Wallet ecosystem, and then building a phased roadmap toward compliance and integration. Waiting for full market maturity before acting is a risky strategy, as the regulatory obligations are already in effect and the ecosystem is moving fast.

A practical preparation approach follows these steps:

1. Map your current identity processes: Understand how you currently verify, onboard, and authenticate users or counterparties. Identify where cross-border identity is already relevant and where it will become relevant under eIDAS 2.0.
2. Assess your technical architecture: Evaluate whether your existing systems can support wallet-based credential presentation, selective disclosure, and the protocols required by the ARF. Identify integration points that need updating.
3. Understand your relying party obligations: If you plan to accept EUDI Wallet credentials, you will need to register as a relying party and comply with the relevant implementing regulations. Start this process early.
4. Align with trust list requirements: Ensure that any identity providers or trust services you use are listed on the relevant national trusted lists. Build processes for monitoring changes to these lists over time.
5. Pilot with real use cases: Rather than preparing in the abstract, identify one or two concrete cross-border identity scenarios relevant to your business and test your readiness against those specific cases.
6. Engage with the ecosystem: Stay connected with developments in your sector, including the outcomes of the large-scale pilot projects and any sector-specific guidance from regulators.

Organisations that treat eIDAS 2.0 interoperability as a compliance checkbox will miss the broader opportunity. Cross-border digital identity, when implemented well, reduces onboarding friction, lowers the cost of compliance, and enables faster, more trusted digital interactions across the EU. The organisations that invest in getting this right now will be better positioned to serve customers and partners across borders as the ecosystem matures. For more guidance on building a practical roadmap, explore the resources available from TrustTech.

How TrustTech helps with eIDAS 2.0 interoperability

Preparing for eIDAS 2.0 interoperability is not just a technical challenge, it is a strategic one. Many organisations know the regulation is relevant but are unsure where to start or how to connect the regulatory requirements to their existing systems and processes. That is exactly where TrustTech comes in.

TrustTech supports organisations across the full journey toward eIDAS 2.0 readiness, with a practical focus on what actually needs to change and how to make it work. Concretely, TrustTech helps with:

• Assessing your current digital identity infrastructure against eIDAS 2.0 and EUDI Wallet requirements, so you know exactly where the gaps are
• Designing and implementing wallet-ready onboarding flows that support selective disclosure, reusable credentials, and cross-border identity recognition
• Integrating with trust frameworks and trust lists so your systems can automatically validate credentials from other member states
• Supporting relying party registration and compliance with the relevant implementing regulations under eIDAS 2.0
• Enabling reusable KYC and compliance checks that work across borders and reduce the burden of repeated verification for your customers

TrustTech works with organisations in finance, government, healthcare, and other regulated sectors, combining deep technical knowledge with practical implementation expertise. The result is a digital identity setup that is compliant by design, scalable across borders, and genuinely easier for your users. Ready to take the next step? Get in touch with TrustTech and find out how we can help your organisation prepare for the future of digital identity in Europe.