The European Union’s regulation requiring member states to offer a functioning EU Digital Identity Wallet to their citizens has a hard deadline: December 2026. Seven months out, the rollout is significantly behind in most of the bloc.

As of April 2026, an assessment of implementation status across all 27 member states found that only four — Denmark, France, Germany, and Ireland — had reached the stage of publicly accessible sandbox testing for their wallet implementations. Several others, including Bulgaria, Finland, Italy, and the Netherlands, had published developer repository materials without public testing available. The majority of member states had either announced projects without any public testing infrastructure, or had not confirmed what stage their development had reached.

The December 2026 deadline is a legal obligation, not a target. The eIDAS 2 regulation that established the wallet requirement carries enforcement mechanisms. Whether the European Commission would actually pursue infringement proceedings against a majority of its member states simultaneously is a political question that has not been tested. What is clear is that the infrastructure many EU privacy debates assume will exist by year-end is substantially incomplete.

What the Wallet Is Supposed to Do

The EU Digital Identity Wallet is intended to be a voluntary, government-issued digital credential that citizens can use to authenticate themselves to public and private services across the EU. Think of it as a digital container for official credentials — a driving licence, passport, national ID, educational certificates, professional qualifications, potentially health records — that works anywhere in the EU without each member state requiring its own separate login system.

The policy rationale is coherent. EU citizens currently navigate dozens of incompatible national digital identity systems. A French resident trying to access public services in Germany faces authentication friction that a physical ID card would not create. A portable, interoperable wallet would reduce that friction and enable cross-border digital service delivery that the EU’s internal market policies require.

The wallet is designed for both public services — government portals, benefits administration, tax systems — and private sector applications, including banking KYC, age verification for age-restricted services, and potentially healthcare.

Ireland: A Case Study in Contested Implementation

Ireland is the EU member state whose wallet implementation has generated the most public debate, and whose policy choices preview questions every member state will face as rollout progresses.

Ireland has written statutory deadlines into its Digital Government law requiring public services to implement the Government Digital Wallet by the end of 2026 and private sector services by the end of 2027 — mirroring the EU mandate. The government launched a pilot programme storing driving licences, birth certificates, and other official documents in a digital wallet accessible via smartphone.

The more contentious proposal: Ireland’s Communications Minister floated requiring the government digital wallet for social media access. Under this model, users would authenticate to Facebook, Instagram, and X using their government-issued digital identity, ensuring that operators could verify age and, by extension, real identity. The proposal is positioned as a child safety measure — preventing minors from accessing age-inappropriate content by requiring verified-age credentials at account creation.

The Irish Council for Civil Liberties delivered a direct critique: the proposal would end anonymous internet browsing. If every social media login is tied to a government-issued wallet, and every wallet is traceable to a specific citizen identity, then every page visit and platform interaction becomes potentially attributable to a named individual. The ICCL’s argument is that online anonymity is not a loophole to be closed but a feature of free expression — one that political dissidents, domestic abuse survivors, whistleblowers, and many others depend on.

The proposal is not law yet. But its political feasibility in the Irish context suggests it will come back in some form, and Ireland is not the only member state where the wallet’s potential as a mandatory authentication layer is being discussed.

The Sovereignty Problem

The EU’s digital sovereignty agenda is one of the explicit policy objectives behind the EUDI Wallet. The bloc has consistently articulated a goal of reducing European dependence on US technology infrastructure — on American cloud providers, operating system vendors, and platform companies.

The EUDI Wallet, as currently specified, depends fundamentally on US-controlled infrastructure for its delivery. Wallets are distributed through Apple’s App Store and Google’s Play Store. The underlying cryptographic operations run on smartphones built on operating systems neither controlled nor audited by EU authorities. Backend infrastructure for many member state implementations is hosted on AWS, Azure, or Google Cloud.

This creates a structural irony: the EU’s sovereign identity infrastructure is delivered through platforms controlled by US companies subject to US law and US government data access requests. The sovereignty arguments that justified the wallet’s creation are partially undermined by the procurement decisions required to build it.

A proposed EU business wallet — intended to unify company identification across borders — remains under negotiation as of May 2026, compounding the complexity.

The Convergence Question

One thread in Irish civil society’s critique connects the wallet timeline to the European Central Bank’s digital euro timeline. Both are expected to deploy in the 2026–2029 window. If they interoperate — if the government wallet becomes the authentication layer for digital euro transactions — then a single government application would capture both identity and transaction history.

That is not the current design intent. EU officials have been careful to frame the digital euro as privacy-protective, with holding limits and offline functionality specifically designed to prevent the kind of comprehensive financial surveillance that CBDC critics worry about. Wallet and currency are legally and technically separate systems.

But technical separation and actual isolation are not the same thing over time. Systems that start as separate tend to integrate where there is administrative convenience in doing so. The civil liberties concern is about the architecture that becomes possible once both systems are deployed, not necessarily about the intentions of the teams building them today.

The December 2026 deadline for wallet deployment and the ECB’s 2029 target for digital euro launch put both systems into the same policy window. How their relationship is defined — technically, legally, and politically — is a question worth asking now, before the infrastructure exists and the defaults are set.

EU Digital Identity Wallet rollout status data from eideasy.com (April 2026). Ireland policy developments from official government communications and ICCL public statements.