The European digital identity wallet: Ivaylo Bozoukov on what the 2026 deadline means for financial services

European financial services are approaching a compliance deadline unlike anything the sector has faced before. By December 2026, every EU member state must make at least one compliant European Digital Identity Wallet, known as the EUDI Wallet, available to its citizens. A year later, by December 2027, banks, payment institutions and e-money issuers across the bloc will be legally required to accept wallet-based credentials from their customers. For an industry still largely built around document scanning and manual verification, the shift is bigger than a new compliance box to tick.

A deadline built into law

The EUDI Wallet is not a voluntary pilot programme that financial institutions can choose to ignore. It is mandated under eIDAS 2.0, formally Regulation (EU) 2024/1183, which requires selective disclosure of personal data, user-controlled access and explicitly prohibits any centralised data repository holding citizens’ identity information. That last point matters more than it might first appear. Unlike a national identity database that a bank might query directly, the EUDI Wallet architecture keeps identity data with the citizen, who chooses what to disclose and to whom.

“Most financial institutions are used to thinking about identity verification as something you request from a central authority or a document,” said Ivaylo Bozoukov. “The EUDI Wallet inverts that. The citizen holds the credentials, and the institution verifies them cryptographically against an EU-level trust framework. That is a different verification model, not just a different interface.”

How wallet verification differs from document scanning

The mechanics matter for compliance teams specifically. When a customer presents a wallet-based credential, the institution is not looking at a scanned passport or driving licence. It is receiving a selectively disclosed, cryptographically signed attribute set, verified against the trust framework without ever taking custody of the underlying identity document itself. For Know Your Customer and anti-money laundering purposes, a verified Person Identification Data credential issued at Substantial or High assurance level under eIDAS 2.0 already meets regulatory requirements. That is a materially different compliance posture from the document-upload-and-manual-review workflows most onboarding teams currently run.

Pilots are already testing the real world

This is not a theoretical framework waiting for its first real use. Large-scale pilot projects spanning 26 member states and involving more than 350 organisations are already testing wallet applications ranging from mobile driving licences to healthcare credentials and financial services onboarding. The EU has set a target of 80 percent citizen adoption by 2030, an ambitious figure that assumes both public administrations and private-sector relying parties move quickly to make the wallet genuinely useful, rather than a compliance formality nobody actually uses.

Ivaylo Bozoukov points to the pilots as the part of the rollout that deserves closer attention from financial services leaders. “The pilot data is where you find out what actually works at scale, not the regulation text,” he said. “Institutions that are only reading the legal deadlines and not tracking the pilot results are going to be building onboarding infrastructure based on assumptions rather than evidence.”

The procurement problem few are discussing openly

For fintechs and regulated financial institutions, the practical implication is unglamorous but urgent: every firm operating in the EU needs verification infrastructure capable of handling both document-based and credential-based onboarding flows well before the December 2026 wallet availability date, since customer adoption will be gradual and both pathways will need to coexist for years. Building, testing and certifying that dual capability is not a task that can be compressed into a final-quarter sprint. Identity verification vendors, core banking providers and in-house engineering teams all need to be aligned on a roadmap now, not once the wallet becomes visible to end users at scale.

That dual-track requirement is where many institutions are underestimating the work involved. It is not simply a matter of adding a new authentication button to an existing onboarding flow. Systems built around document capture, optical character recognition and manual fallback review need a parallel, cryptography-based verification path that can interrogate wallet-issued credentials against the EU trust framework, log the result in a way that satisfies auditors, and fail gracefully back to existing document flows for the large share of customers who will not yet hold a wallet.

What this means beyond Europe

While the EUDI Wallet mandate is specific to the EU, the underlying shift toward wallet-based, user-controlled identity verification is being watched closely well beyond European borders. Ivaylo Bozoukov argues that financial institutions across the GCC, East Africa and other emerging markets pursuing financial inclusion at scale have strong reasons to pay attention now rather than later.

The technical architecture behind the EUDI Wallet, selective disclosure, cryptographic verification, user control over data, solves real problems for financial inclusion, not just European regulatory compliance, Ivaylo Bozoukov said. “Markets building digital identity infrastructure for the first time do not need to repeat the mistakes of centralised systems that raise both security and privacy concerns. There is a genuine opportunity to learn from what Europe is building and adapt the parts that fit local regulatory and infrastructure realities.”

Preparing for a deadline that will not move

Regulatory deadlines of this scale rarely slip meaningfully once implementing legislation is in force, and the EUDI Wallet timeline has been stable since the eIDAS 2.0 regulation entered into effect. For financial institutions operating in or serving the EU market, the practical question is no longer whether wallet-based verification is coming. It is whether onboarding, compliance and engineering teams have a credible plan to support it alongside existing document-based processes by the time customers start presenting wallet credentials at scale.