eIDAS 2.0, Regulation (EU) 2024/1183, amends Regulation (EU) 910/2014 and fundamentally changes KYC processes for financial institutions by introducing a standardised, high-assurance digital identity framework. Customers can verify their identity once and reuse that verified data across multiple organisations. Instead of repeating identity checks from scratch every time a customer opens a new account or accesses a regulated service, financial institutions can accept tamper-evident, cryptographically signed identity attributes directly from the European Digital Identity Wallet. The sections below break down exactly what this means in practice, from onboarding workflows and assurance levels to compliance timelines and how to prepare.
What does eIDAS 2.0 actually change about identity verification?
eIDAS 2.0 replaces the fragmented, country-by-country approach to digital identity with a unified European framework. Every EU Member State is now required to provide citizens, residents, and businesses with a European Digital Identity Wallet, and both public and private sector organisations must accept it as a valid means of identity verification where the relevant obligations apply. This shifts identity verification from an institution-driven process to a citizen-controlled one.
Under the original eIDAS regulation, Member States could notify their national eID schemes for cross-border recognition, but there was no obligation to do so. The result was a patchwork of incompatible systems. eIDAS 2.0 closes that gap by mandating wallet availability and cross-border interoperability across all Member States.
For financial institutions, the practical shift is significant. Identity data stored in an EUDI Wallet is cryptographically signed, meaning the attributes a customer shares, such as name, date of birth, or nationality, carry built-in tamper-evidence. Financial institutions no longer need to independently re-verify information that has already been verified at the source, whether that source is a government authority, an employer, or another regulated institution.
It is important to understand that the EUDI Wallet ecosystem involves shared governance across multiple actors. The European Commission manages the legal framework and adopts implementing acts that contain the binding requirements. EU 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 cross-border alignment and cooperation. National competent authorities, wallet providers, issuers of Person Identification Data and attestations, qualified trust service providers, and relying parties each carry distinct responsibilities within this structure. No single central European authority operationally manages all EUDI Wallets.
How does the EUDI Wallet affect KYC onboarding workflows?
The EUDI Wallet transforms KYC onboarding by enabling customers to share pre-verified identity attributes directly from their wallet, eliminating the need to collect and re-verify documents manually. A customer can consent to sharing specific verified data points in a single interaction, without uploading passport scans or completing video identification. This makes onboarding faster, less error-prone, and far less likely to cause drop-off.
Lengthy identity checks are one of the leading causes of onboarding abandonment. Every additional step a customer has to complete increases the chance they will leave before finishing. The wallet-based model reduces that friction significantly because the hard work of verification has already been done upstream.
From a workflow perspective, the EUDI Wallet also enables reusable onboarding. A customer who has already completed identity verification at their bank or with a government service does not need to start from scratch when approaching a new financial institution. The verified data travels with the customer, and the receiving institution can trust it based on the cryptographic guarantees embedded in the wallet. This is a meaningful shift for financial services teams that currently manage high volumes of manual KYC checks.
Before a financial institution can request wallet data, it must register as a relying party with the national authority of its Member State of establishment, as required by CIR (EU) 2025/848 of 6 May 2025. Registration specifies, per intended use, which attributes and attestations the institution will request. The wallet checks each presentation request against this registered scope before any data is shared.
Does eIDAS 2.0 compliance satisfy AML and KYC regulatory requirements?
eIDAS 2.0 compliance does not automatically satisfy AML or KYC requirements, but it provides a strong and legally recognised foundation for meeting them. KYC obligations under Anti-Money Laundering directives require financial institutions to verify customer identity, understand the nature of the business relationship, and apply risk-based due diligence. eIDAS 2.0 addresses the identity verification component directly, but AML compliance involves additional obligations that go beyond identity proofing alone. Reuse of KYC data across institutions is governed by AML regulation, not by eIDAS itself.
That said, the relationship between eIDAS 2.0 and AML regulation is becoming increasingly aligned. The EU’s AML regulatory framework is evolving in parallel with the digital identity landscape, and regulators have signalled that high-assurance digital identity verification carried out through the EUDI Wallet can satisfy the customer due diligence requirements under AML rules when applied correctly. The EU Anti-Money Laundering Regulation is expected to apply from July 2027, and financial institutions that align their KYC infrastructure with eIDAS 2.0 now will be better positioned to meet those requirements as well. The AML obligations and the eIDAS 2.0 acceptance requirement are distinct frameworks, even where their timelines converge.
For financial institutions, the practical implication is that accepting EUDI Wallet credentials for identity verification is becoming the expected standard. Institutions that build their KYC processes around wallet-based verification will be better positioned to meet both current AML requirements and the more harmonised compliance framework that is taking shape at the European level.
What level of assurance does eIDAS 2.0 require for financial services KYC?
eIDAS 2.0 requires the EUDI Wallet to operate at the High level of assurance, which is the highest level defined in the eIDAS framework. For financial services KYC, this matters because it means the identity attributes stored and shared via the wallet have been verified through a process that meets strict standards for identity proofing, authentication, and data integrity. This aligns directly with the risk-based requirements that AML and KYC regulations place on financial institutions.
The three levels of assurance under eIDAS are Low, Substantial, and High. The High level requires that the identity has been verified through a robust process, typically involving documentary evidence and biometric checks, and that the authentication mechanism used to access the wallet is resistant to compromise. For financial institutions operating in regulated contexts, only High assurance is typically sufficient for onboarding new customers or accessing sensitive account functions.
This is one of the reasons the EUDI Wallet represents a meaningful step forward for financial services compliance. Previous digital identity solutions varied widely in their assurance levels and were often not formally recognised across borders. The EUDI Wallet standardises High assurance at the European level, giving financial institutions a consistent and legally recognised baseline to build their KYC processes on.
How should financial institutions prepare their systems for eIDAS 2.0 KYC?
Financial institutions should prepare for eIDAS 2.0 KYC by auditing their current identity verification infrastructure, identifying where wallet-based credentials can replace or supplement existing checks, and ensuring their systems can accept and process verifiable credentials in a standards-compliant way. Preparation is not a single project but a phased process that touches technology, compliance, and operations.
A practical preparation approach involves the following steps:
- Audit your current KYC process to identify which steps involve identity document collection, manual verification, or repeated data entry that could be replaced by wallet-based attributes.
- Map your regulatory obligations to understand which KYC and AML requirements the EUDI Wallet can address and which require additional controls beyond identity proofing.
- Assess your technical stack to determine whether your onboarding platform can integrate with wallet-based credential flows and what changes are needed to support verifiable credentials. The EUDI Wallet uses mdoc and SD-JWT VC credential formats, with OID4VCI for issuance and OID4VP for presentation.
- Engage your compliance and legal teams early to ensure that wallet-based verification is documented in your policies and that your risk framework accounts for the new identity model.
- Register as a relying party under CIR (EU) 2025/848 with the national authority of your Member State of establishment. Registration must be completed before you can request wallet data, and you must specify per intended use which attributes and attestations you will request.
- Plan for interoperability by considering how your systems will handle customers arriving with wallets from different Member States. 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, but not every use case will be immediately available everywhere, and sector-specific legislation and national registration requirements continue to apply alongside the European framework.
Organisations that start this process now will have a significant advantage. Implementation timelines for identity infrastructure changes are rarely short, and building wallet readiness into existing digital transformation programmes is far more efficient than retrofitting it later.
When do financial institutions need to be eIDAS 2.0 compliant?
The eIDAS 2.0 compliance timeline for financial institutions involves two distinct deadlines. By 24 December 2026, every EU Member State must have at least one certified EUDI Wallet operational for citizens, residents, and businesses, and public bodies must accept notified wallets as a valid means of identification from that date. For financial institutions and other regulated private sector organisations in sectors including banking and financial services, healthcare, telecoms, energy, transport, education, social security, drinking water, postal services, digital infrastructure, digital services, and very large online platforms with more than 45 million users in the EU, the obligation to accept EUDI Wallet credentials applies from 24 December 2027, under Article 5f of the regulation. For the regulated private sectors listed above, this deadline applies where strong user authentication is required by law or contract. Very large online platforms are subject to a separate provision under Article 5f, which applies where the platform requires user authentication, on the voluntary request of the user and limited to the minimum necessary data.
It is important to distinguish between the legal deadline and the practical reality of national rollout. The date of 24 December 2026 is the legal deadline for Member States’ wallet obligations. It is not a guarantee that every national wallet will have reached the same level of maturity or that every possible cross-border use case will be fully operational throughout Europe on that date. Certification, notification, and operational interoperability may develop in phases across Member States, and financial institutions should not wait for a single European go-live moment before beginning their preparation. The period between the 2026 wallet launch deadline and the 2027 acceptance deadline is a practical window for integration, testing, and staff training, and institutions that delay risk both compliance gaps and competitive disadvantage as wallet adoption accelerates.
It is also worth noting that eIDAS 2.0 compliance intersects with other regulatory timelines. The EU’s updated AML framework is moving toward greater reliance on notified eID schemes, the EUDI Wallet, and qualified trust services for identity verification, with further harmonised requirements expected from 2027 onward. Financial institutions that align their KYC infrastructure with eIDAS 2.0 now will be better positioned to meet those requirements as well. The AML obligations and the eIDAS 2.0 acceptance requirement are distinct frameworks, even where their timelines converge.
How TrustTech helps financial institutions with eIDAS 2.0 KYC
Adapting KYC processes to eIDAS 2.0 is an opportunity to build a faster, more reliable, and more customer-friendly identity infrastructure. 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 financial institutions, the ID Connector handles the technical complexity of wallet-based KYC by managing verification against national trusted lists, checking revocation status via issuer status information, and validating wallet unit attestations to confirm that a presenting wallet runs on a certified wallet solution. It also enforces the registered attribute scope per intended use, so that presentation requests stay within the bounds of what has been registered with the national authority under CIR (EU) 2025/848.
TrustTech’s work in financial services supports institutions through the following capabilities:
- Secure digital onboarding with cryptographically signed identity data, reducing drop-off and manual processing
- Reusable KYC flows that allow verified customer data to be trusted and reused across products and services
- EUDI Wallet integration built on European digital identity standards, so your infrastructure is ready for wallet-based credentials from day one
- Qualified digital signatures that link identity to every consent, approval, and transaction with a complete audit trail, via a connected qualified trust service provider
- Compliance alignment with eIDAS 2.0, AML, and KYC requirements, designed to evolve as regulation matures
TrustTech’s platform connects identity proofing, qualification, and signing in a single trust infrastructure, and has delivered results including more than 59% faster onboarding and production timelines of under five months. If you are ready to future-proof your KYC processes for eIDAS 2.0, get in touch with TrustTech to discuss what the transition looks like for your organisation.