For the last two years, eIDAS 2.0 has been treated as a fixed point on the calendar: by December 24, 2026, every EU member state has to offer citizens, residents, and businesses a certified European Digital Identity Wallet. Compliance teams built roadmaps around that date. Vendors marketed “eIDAS-ready” products against it. Procurement cycles assumed it.
It’s now slipping — and the way it’s slipping matters more than the fact that it is.
The deadline isn’t missing uniformly. It’s missing unevenly.
Germany, one of the EU’s largest and most technically capable member states, has already said its national wallet won’t be ready until January 2, 2027 — a few days after the legal deadline. Bulgaria’s eID provider has indicated that serious build work hadn’t even started as of last December. Meanwhile, other states are running interoperability tests between each other right now, with Romania among the countries actively piloting cross-border credential exchange.
That spread is the real story. This isn’t a regulation quietly slipping by a uniform six months across the bloc. It’s a patchwork: some member states will have production-grade, interoperable wallets close to on time, others will be months behind, and a few are anyone’s guess. For any enterprise whose compliance or product strategy assumes “the wallet” as a single EU-wide capability arriving on a single date, that assumption just became a liability.
Why this is a delivery problem, not just a legal one
It’s tempting to read wallet slippage as a compliance-team concern — something legal and regulatory affairs will track and report on. In practice, it’s a project delivery problem, and it touches at least three things enterprises are already planning around:
- Onboarding flows. Systems designed to accept EUDI Wallet-based authentication or credential presentation need a fallback path for the countries where the wallet isn’t live yet — and that fallback needs its own testing, security review, and sunset plan once the wallet does arrive.
- Cross-border use cases. Anything that depends on a credential issued in one member state being accepted in another is only as reliable as the slowest state in that specific transaction chain. A rollout plan that assumes uniform EU coverage by a fixed date needs a country-by-country readiness view instead.
- Adjacent regulatory timelines. The wallet isn’t the only clock running. Digital Product Passport requirements under the EU’s broader ecodesign framework, and other supply-chain traceability mandates, increasingly assume digital identity and wallet infrastructure exists as a foundation. If wallet rollout staggers, anything built on top of it — including product passport ecosystems that expect verifiable business identities to already be in place — inherits that same staggered risk, even though it’s a separate regulation with its own deadline.
What “ready” should actually mean right now
For an enterprise PM or delivery lead sitting between technical teams, legal, and external partners, the practical takeaway isn’t “wait for more clarity.” It’s to treat the December 2026 date as a range rather than a milestone:
- Build a country-by-country readiness tracker, not a single go-live date, and revisit it monthly — this is a fast-moving picture, not a settled one.
- Design authentication and credentialing flows so the “no wallet yet” path is a first-class scenario, not a temporary workaround bolted on later.
- Flag dependencies explicitly to stakeholders whose own timelines assume wallet availability — including anyone building compliance workflows for adjacent regulations that lean on digital identity infrastructure.
- Keep a direct line into interoperability testing news. The states running pilots now are effectively previewing the friction points everyone else will hit later.
The bigger pattern
Large, multi-country EU digital regulations rarely land as a single synchronized moment, however clean the legal text reads. eIDAS 2.0 is following the same pattern earlier frameworks did: a firm date on paper, a staggered reality on the ground, and real advantage going to the organizations that planned for the stagger instead of the date.
That’s not a reason to slow down. It’s a reason to plan for unevenness as the default case — and to treat every “EU-wide by [date]” regulation with the same question: what does readiness look like in the member state that’s furthest behind, and what’s our plan for operating in that gap?