The future of digital identity beyond eIDAS 2.0 is one of greater interoperability, user control, and trust infrastructure that works seamlessly across borders and sectors. eIDAS 2.0 and the European Digital Identity Wallet (EUDI Wallet) are not the finish line — they are the foundation. What comes next is a broader shift in how organizations, governments, and individuals exchange verified data in a world where digital trust becomes as fundamental as physical identification. This article walks through the key questions shaping that future.
Wait — the instructions say to remove em dashes as punctuation. Let me apply that and all other instructions properly.
The future of digital identity beyond eIDAS 2.0 is one of greater interoperability, user control, and trust infrastructure that works seamlessly across borders and sectors. eIDAS 2.0 and the European Digital Identity Wallet (EUDI Wallet) represent a foundation, not a finish line. What comes next is a broader shift in how organizations, governments, and individuals exchange verified data in a world where digital trust becomes as fundamental as physical identification. This article walks through the key questions shaping that future.
What comes after eIDAS 2.0 in digital identity?
After eIDAS 2.0, the digital identity landscape will shift from regulatory compliance toward ecosystem maturity. The EUDI Wallet gives every EU citizen and resident a standardized way to prove who they are, but the real transformation happens when organizations build services on top of that infrastructure and when cross-border identity exchange becomes routine.
eIDAS 2.0, formally Regulation (EU) 2024/1183, amends Regulation (EU) 910/2014. It entered into force on 20 May 2024. It sets the legal and technical baseline through the regulation itself and a series of implementing acts, which are legally binding. The Architecture and Reference Framework elaborates those requirements technically but is not itself legislation. The legal deadline for EU Member States to fulfil their wallet obligations is 24 December 2026. Member States are responsible for providing or mandating wallet solutions, certifying and notifying them, and supervising the actors within their jurisdiction. The regulation also establishes frameworks for qualified electronic signatures, electronic attestations of attributes, and trust services.
Regulation alone does not create a functioning ecosystem. That requires organizations to integrate wallet-compatible services, relying parties to accept verified credentials, and users to experience genuine value from carrying their identity digitally. It is also important to understand that 24 December 2026 is a legal deadline, not a 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. Practical interoperability and national rollout are expected to develop in phases, and organizations should plan accordingly.
What follows eIDAS 2.0 is a maturation phase. Expect to see broader adoption of verifiable credentials across sectors, increasing interoperability between national wallet implementations, and growing demand for identity solutions that cover professional qualifications, healthcare records, educational credentials, and organizational identity. The NOBID consortium piloted cross-border payment use cases as one early example of how wallet-based identity extends into entirely new domains.
How will verifiable credentials reshape digital trust ecosystems?
Verifiable credentials will fundamentally change how digital trust works by making identity data portable, tamper-evident, and reusable across organizations. A person or business can carry a credential issued by a trusted authority and present it wherever it is needed, with the verifying organization performing its own checks without contacting the issuer for every transaction.
This matters enormously for organizations that currently repeat the same checks. A customer who has already completed a KYC process at their bank, verified their identity with their employer, or received a qualification from a university should not need to prove those things again every time they interact with a new service. Verifiable credentials make the “verify once, reuse everywhere” model technically possible, though the extent to which KYC data can be reused across institutions is governed by AML regulation, not by eIDAS 2.0 itself.
The trust ecosystem built on verifiable credentials has three key roles:
- Issuers: organizations that create and sign credentials, such as governments, banks, universities, or employers
- Holders: individuals or organizations that store credentials in a wallet and decide when to share them
- Verifiers: organizations that request and check credentials by performing their own verification steps
Verification involves more than a single cryptographic check. A verifier should distinguish between at least three separate steps: verifying the issuer’s signature against the relevant national trusted list (which is aggregated at EU level in the EU List of Trusted Lists, or LOTL); checking the revocation status of the credential using the issuer’s status information; and checking the wallet unit attestation to confirm that the presenting wallet is running on a certified wallet solution. Only the first of these steps can be performed fully offline. It is therefore not accurate to describe credential verification as a process that operates entirely without any connection to external sources.
This architecture reduces friction, lowers compliance costs, and puts users in control of their own data. For organizations in regulated sectors, it also creates a more defensible audit trail, because every credential carries a cryptographic proof of who issued it and when.
Governance of this ecosystem is a shared responsibility. The European Commission manages the legal framework and adopts implementing acts. Member States certify and notify wallet solutions and supervise actors within their jurisdiction. The European Digital Identity Cooperation Group supports cross-border alignment and cooperation. National competent authorities, registrars, wallet providers, issuers of Person Identification Data and attestations, qualified trust service providers, and relying parties each carry distinct roles. No single central European authority operationally manages all EUDI Wallets.
What role will AI play in the future of digital identity?
AI will play a growing role in digital identity by improving fraud detection, streamlining verification processes, and making identity systems more adaptive to emerging threats. The combination of AI-driven analysis with tamper-evident, cryptographically signed credentials creates a stronger foundation for trust than either approach delivers alone.
On the fraud prevention side, AI can detect anomalies in behavior patterns, flag suspicious onboarding attempts, and identify synthetic identities that might pass traditional document checks. Liveness detection, already used in biometric verification, relies heavily on AI to distinguish real people from spoofing attempts using photos or video. Biometric verification that solely confirms a person is who they claim to be falls outside the high-risk AI category under the EU AI Act, though organizations must still account for the processing of biometric data under Article 9 GDPR and the transparency obligations under Article 50 of the AI Act.
AI also has a role in making identity verification more accessible and less burdensome for users. Intelligent systems can guide users through onboarding flows, automatically extract and validate information from documents, and reduce the number of manual steps required. This directly addresses one of the most persistent problems in digital identity: abandonment during verification processes because the experience is too slow or complex.
There is also a governance dimension to consider. As AI becomes embedded in identity decisions, such as assessing creditworthiness, verifying professional qualifications, or detecting fraud, organizations need to ensure those decisions remain explainable, auditable, and compliant with both identity regulations and AI legislation such as the EU AI Act. The application dates for specific provisions of the AI Act, including the high-risk regime, should be verified against current legislation before drawing compliance conclusions, as these have been subject to amendment.
How will digital identity evolve across different sectors?
Digital identity will evolve differently across sectors depending on their regulatory environment, the nature of the trust relationships involved, and how quickly they adopt wallet-based infrastructure. The direction is consistent: every sector will move toward more standardized, interoperable, and user-controlled identity frameworks.
Cross-border interoperability under the EUDI Wallet framework means 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 national registration requirements or sector-specific legislation disappear, that every credential automatically carries the same legal consequence in every country, or that a central European database contains everyone’s identity. Which elements are interoperable at European level and which remain national or sector-specific will vary by use case and jurisdiction.
From 24 December 2026, public sector bodies must accept notified wallets for online services that require electronic identification. From 24 December 2027, Article 5f of the amended regulation applies to relevant regulated private sectors where strong user authentication is required by law or contract. These sectors include banking and financial services, healthcare, telecommunications, energy, transport, education, social security, drinking water, postal services, digital infrastructure, and digital services. Very large online platforms (VLOPs) are covered by a separate provision of Article 5f: where a platform requires user authentication, it must accept the EUDI Wallet on the voluntary request of the user and for the minimum necessary data. Micro and small enterprises, defined as organizations with fewer than 50 employees and an annual turnover or balance sheet total of no more than 10 million euros, are exempt from the private acceptance obligation.
Before a relying party can request wallet data, it must register with the national authority of its Member State of establishment under CIR (EU) 2025/848, adopted on 6 May 2025. Registration covers the intended use and specifies which attributes and attestations the relying party is authorized to request. The wallet checks incoming requests against this registered scope.
Financial services and banking
Financial services face some of the most demanding identity requirements, combining KYC, AML, and PSD2 obligations with growing pressure from eIDAS 2.0 and the forthcoming Anti-Money Laundering Regulation, which applies from July 2027. The opportunity here is significant: reusable identity credentials could streamline onboarding across banks, insurers, and investment platforms, though the extent of KYC reuse remains subject to AML rules. Organizations that build digital identity for financial services into their infrastructure early will gain a meaningful advantage in onboarding speed and compliance efficiency.
Healthcare and pharmaceuticals
In healthcare, digital identity enables secure patient consent, prescription management, and cross-border health data exchange. The EUDI Wallet’s support for the European Health Insurance Card is an early example. As healthcare becomes more digital and cross-border, verified identity becomes essential for protecting patient privacy while enabling seamless care. Processing health data requires a legal basis under both Article 6 and Article 9(2) GDPR. Organizations exploring identity solutions for healthcare need to balance strict data protection requirements with genuine usability for patients and practitioners alike.
Government and public services
Governments are both issuers and relying parties in the digital identity ecosystem. They issue foundational credentials, including national IDs, driving licenses, and social security information, and they also consume credentials when citizens access public services. The shift toward wallet-based identity simplifies citizen interactions while reducing the administrative burden on government systems. For relying parties in the public sector, registration remains connected to the applicable national registration framework under CIR (EU) 2025/848. Solutions for government digital identity need to prioritize accessibility, inclusivity, and long-term interoperability.
What is the difference between federated identity and self-sovereign identity?
Federated identity and self-sovereign identity (SSI) differ primarily in who controls the identity data and how trust is established. In a federated model, a central identity provider, such as a government portal, a large platform, or an employer, authenticates users on behalf of other services. In an SSI model, the individual holds their own credentials and shares them directly, without relying on a central intermediary for each transaction.
Federated identity systems, such as those built on SAML or OpenID Connect, have been the dominant approach for many years. They work well within controlled ecosystems but create dependency on the identity provider and can introduce privacy risks when that provider can track where a user authenticates.
SSI reverses that model. The user holds cryptographically signed credentials in a wallet, presents them to verifiers directly, and the issuer is not involved in the individual transaction. This preserves privacy, reduces dependency on any single organization, and aligns with the principles behind the EUDI Wallet.
The EUDI Wallet shares characteristics with SSI in that storage and presentation are decentralized. However, the governance structure is centrally organized, through national trusted lists, state-designated PID issuers, and national registration of relying parties. Describing the EUDI Wallet as an SSI system without explaining this distinction would be misleading.
In practice, the future of digital identity is not a clean choice between the two models. Many real-world systems will combine elements of both, using federated approaches for internal enterprise identity while adopting wallet-aligned models for citizen-facing and cross-border use cases. The key distinction for organizations to understand is the difference in trust architecture: centralized trust versus distributed trust rooted in cryptographic proofs and governed through trusted lists.
Should organizations start preparing for post-eIDAS identity changes now?
Yes. Organizations should start preparing now, not because the deadline is immediate, but because the underlying changes to digital identity infrastructure take time to implement correctly. The organizations that will be best positioned in the next three to five years are those that begin aligning their systems, processes, and compliance frameworks today.
There are several practical reasons to act early:
- Integration complexity: Connecting existing systems to wallet-compatible identity infrastructure requires architectural decisions that cannot be made overnight. The earlier an organization understands what changes are needed, the more control it has over the implementation timeline.
- Competitive advantage: Faster, smoother onboarding is a genuine differentiator. Organizations that eliminate redundant verification steps and reduce customer friction will see measurable improvements in conversion and retention.
- Regulatory stacking: eIDAS 2.0 does not exist in isolation. The Anti-Money Laundering Regulation applying from July 2027, GDPR, PSD2, and sector-specific regulations all interact with digital identity requirements. Building a coherent compliance framework now avoids costly retrofitting later.
- Ecosystem readiness: The value of digital identity infrastructure grows as more organizations participate. Early adopters help shape the ecosystem and build the trust relationships that make reusable credentials genuinely useful.
Organizations do not need to have all the answers immediately. A realistic starting point is a structured assessment of current identity processes, a review of how existing systems align with EUDI Wallet requirements, and a clear understanding of which use cases offer the most immediate value. Because national wallet rollouts and certification timelines will vary across Member States, organizations should monitor developments in the jurisdictions most relevant to their operations and engage with national competent authorities where appropriate. Exploring the available digital identity resources is a practical first step toward building that understanding.
How TrustTech supports the future of digital identity
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 preparing for the obligations that take effect on 24 December 2026 and 24 December 2027, the ID Connector handles the technical complexity of wallet acceptance across implementations. It manages verification against national trusted lists aggregated in the EU List of Trusted Lists, checks revocation status using issuer-provided status information, and validates wallet unit attestations to confirm that a presenting wallet runs on a certified wallet solution. It also enforces the registered attribute scope defined under CIR (EU) 2025/848, so that only the data a relying party is authorized to request is processed. Where qualified signing is required, the ID Connector connects to an accredited QTSP.
Organizations in financial services, healthcare, pharmaceuticals, and government can use the ID Connector to:
- Accept every relevant notified EUDI Wallet for identification and login, regardless of the issuing Member State
- Enable reusable identity credentials for onboarding and qualification checks, within the boundaries set by applicable sector regulation
- Connect identity presentation to qualified digital signatures, with a complete audit trail for every interaction
- Reduce onboarding drop-off with a streamlined, user-controlled verification flow
- Build interoperable identity infrastructure that works across sectors, borders, and use cases
If your organization is ready to take the next step toward future-proof digital identity, get in touch with TrustTech to discuss your specific situation and explore what the right approach looks like for you.