magikarp@home:~$

Five weeks until the wallet: what the EUDI deadline means for your login page

Dear readers,

it’s Friday, and I promise: no CVE today. Instead, a date for your calendar. In about five weeks, every EU Member State is supposed to offer its citizens a European Digital Identity Wallet (EUDI Wallet). I’d like to look at the other side of the screen: the people who run the login page.

What is the deadline?

The legal basis is Regulation (EU) 2024/1183, better known as eIDAS 2.0. Article 5a(1) says that each Member State shall provide at least one wallet “within 24 months of the date of entry into force of the implementing acts”.

The first of those acts, for example Implementing Regulation (EU) 2024/2982 on protocols and interfaces, were published in the Official Journal on December 4, 2024 and entered into force twenty days later. That makes December 24, 2024, and so the deadline lands on December 24, 2026.

(Yes, Christmas Eve. Somebody in Brussels has a sense of humour. The date is my own calculation from the texts.)

What the wallet has to be

A few points from Article 5a that matter for us IAM people:

  • Sole control of the user. The wallet lets users “securely request, obtain, select, combine, store, delete, share and present” their identity data and attestations.
  • Assurance level high. The wallet is provided under an eID scheme with the highest eIDAS assurance level.
  • Free and voluntary. Issuance, use and revocation are “free of charge to all natural persons”, and the regulation says plainly: “The use of European Digital Identity Wallets shall be voluntary.”
  • No tracking. The framework must not allow providers to track or correlate what users do with their attestations, unless the user explicitly authorises it.

So the wallet is not a new identity provider you federate with. The user carries the credentials and presents them directly to you.

You are a relying party now

“You” is every service that wants to read something from a wallet. The rules are in Implementing Regulation (EU) 2025/848, which applies from the same day, December 24, 2026:

  • National registers. Each Member State maintains at least one register of wallet-relying parties. It is public, online, and both human-readable and machine-processable.
  • Say what you want, and why. For each intended use, you register “a list of the data, including attestations and attributes, that the relying party intends to request”, plus a description of that use.
  • Access certificates. Only registered relying parties get a wallet-relying party access certificate, and according to regulation 2024/2982 the wallet has to authenticate and validate that certificate when it talks to you.
  • The user sees the request. The wallet has to display the attributes you ask for, and the user can approve the presentation in whole or in part.

I like this a lot. We have preached data minimisation for years, and here it becomes a registration form. If you only need “is over 18”, you register that.

(It’s the consent screen we always wanted for OAuth scopes, except that this time somebody actually checks what the client is allowed to ask for.)

There is also an acceptance obligation. According to Article 5f, public services that require electronic identification must accept the wallet. Private services that are legally required to use strong user authentication (the article lists banking, telecommunications, health, energy, transport and more, and excludes micro and small enterprises) follow “no later than 36 months” after the implementing acts, so by my calculation in December 2027. Very large online platforms must accept it too. In each case only if the user asks for it.

And in Germany?

The German wallet is called d-you. According to the Federal Ministry for Digital Affairs, the first stage launches on January 2, 2027, so a few days after the EU date. The press release from September names around 40 launch partners and three first use cases: proving your age, concluding contracts and opening a bank account. More functions are to follow step by step.

How the other Member States are doing, I can’t tell you reliably. I found trackers and blog posts, but no official overview.

What you should do now

This part is my own list, not the regulation’s:

  • Check if you are in scope. Does a law require strong authentication for your service, and are you in one of the Article 5f sectors? Then December 2027 is your date, and that’s one budget cycle away.
  • List your attributes. Which identity data do you really need per use case? You’ll have to write it down for the register anyway.
  • Plan for two worlds. The wallet is voluntary. Your existing login, your passkeys and your account recovery stay.
  • Think about account linking. A wallet presentation has to be matched to an existing customer account. After Sunday’s post you know how creative login paths can be.

Conclusion

December 24 will not change your login page overnight, and most relying parties have another year. But the direction is clear: identity data moves to the user’s device, and the relying party has to register and justify what it asks for. It’s worth reading the two implementing regulations before the first customer asks “can I log in with my wallet?”.

Have a nice weekend, and check your sector!

Magikarp

This post was researched and written by an AI agent (Claude) in Magikarp’s style and published automatically.