KontorBund
The Library

The EUDI Wallet: the 24 December 2026 and 24 December 2027 dates, and who has to accept it

Last checked23 October 2026
KeeperOpen — keeper wanted
StatusIn force — 24 Dec 2026 and 24 Dec 2027

The short version

Two dates carry the EU Digital Identity Wallet into business life, and neither of them is a deadline for a one-person shop. By 24 December 2026 every member state must provide at least one wallet (Article 5a(1) of Regulation (EU) 2024/1183, "eIDAS 2.0"). By 24 December 2027, private relying parties that Union or national law — or a contractual obligation — requires to use strong user authentication must accept the wallet at the user's request (Article 5f(2)), with micro and small enterprises exempt. Very large online platforms are in a group of their own (Article 5f(3)). And before anyone may request data from a wallet, they must register as a relying party — in the member state where they are established, valid throughout the Union (Article 5b).

The two dates

eIDAS 2.0 is Regulation (EU) 2024/1183, in force since 20 May 2024. It does not put a wallet in anyone's hand by itself: the deadline is counted from the implementing acts, and the first of those entered into force on 24 December 2024. Twenty-four months later comes the member states' obligation, thirty-six months later the acceptance duty. That is where 24 December 2026 and 24 December 2027 come from — the two dates are arithmetic, not negotiation.

24 December 2026 — the member states
Each member state must provide at least one EUDI Wallet (Article 5a(1)). The Commission's own policy page puts the same duty in plainer words: the framework mandates member states to provide EU Digital Identity Wallets to citizens by the end of 2026.
24 December 2027 — the relying parties
Private relying parties that Union or national law, or a contractual obligation, requires to use strong user authentication for online identification must accept the wallet at the user's request (Article 5f(2)). The 36 months run from the implementing acts of 24 December 2024.
What a wallet is meant to hold
Person identification data (PID) and electronic attestations of attributes (EAA) — a driving licence, a professional qualification, a proof of age — with selective disclosure so a user can show "over 18" instead of a date of birth, and a qualified electronic signature (Article 5a(4)).
What the user decides
The wallet is a right for the user, not an obligation. Where a relying party has to offer it, the user still chooses between the wallet and another method; existing identification procedures may continue in parallel, and users must not be pressured into using the wallet (Article 5a(15)).
The implementing acts behind the dates
Implementing Regulation (EU) 2025/848 of 6 May 2025 governs the registration of relying parties; Implementing Regulation (EU) 2026/798 of 8 April 2026 governs the registration of users — the briefing attaches Article 5a(24) to that act. The clock on both dates runs from the first of the implementing acts, on 24 December 2024.
Neither date obliges a small seller to do anything. 24 December 2026 is a duty on governments. 24 December 2027 is a duty on a defined set of relying parties, and the smallest of those are expressly carved out. If a supplier tells you that "the EU requires every business to accept the digital ID by December 2027", that is not what Article 5f(2) says — see the contractual-obligation section for what is actually unresolved.

Who has to accept it

Article 5f sorts the addressees into three groups. Read the group before you read the deadline, because only the second one has a transition period and only the second one has a size exemption.

1. Public bodies — Article 5f(1)
They must accept the wallet wherever they require electronic identification for access to online services, and that includes wallets issued by other member states.
2. Private relying parties — Article 5f(2)
Anyone whom Union or national law, or a contractual obligation, requires to use strong user authentication for online identification. The Regulation names the areas it has in mind: transport, energy, banking, financial services, social security, health, drinking water, postal services, digital infrastructure, education and telecommunications. This is the group with the 24 December 2027 date and the micro and small enterprise exemption.
3. Very large online platforms — Article 5f(3)
Providers of very large online platforms within the meaning of Article 33 of the Digital Services Act must accept the wallet where they require user authentication — but only for the data strictly necessary for the service. On the briefing's reading the acceptance obligation applies to them without a separate transition period. A size exemption cannot help here: Article 33 is the definition of the largest platforms.
Everyone else — Article 5b(1)
eIDAS 2.0 imposes no acceptance duty on other businesses. They may accept the wallet voluntarily — and must register to do so. That is the sentence most people miss: the registration duty follows the data request, not the obligation to accept.

What "accept" means, on the briefing's reading, is narrow and worth keeping straight: the relying party must offer the wallet as a means of identification as soon as a user wishes to use it, and must not insist on it. That is a duty to allow, not a duty to push.

The micro and small enterprise exemption

Article 5f(2) exempts microenterprises and small enterprises, by reference to Article 2 of the Annex to Commission Recommendation 2003/361/EC — the same size classes the Commission uses elsewhere in EU law. We have not restated the headcount and turnover thresholds from that Annex on this page; if your size is the question, read them in the Annex rather than in a summary, ours included.

What the exemption does
It takes you out of the acceptance duty in Article 5f(2). A one-person shop that would otherwise be caught by the "contractual obligation" limb does not have to take the wallet.
What it does not do
It does not exempt you from registration if you decide you want to request data from a wallet anyway, and it does not touch the platform group in Article 5f(3). Nor does it change any sector rule that already obliges you to identify customers — that rule stands on its own.
Check it per entity, per service
The briefing's own checklist asks whether the company is subject to a statutory or contractual strong-authentication duty for each legal entity and each service. One legal entity with two services can be in scope for one of them.

The unsettled question: card schemes and group policies

The whole of Article 5f(2) hangs on a phrase nobody has yet defined: what counts as a contractual obligation to use strong user authentication. The briefing is explicit that this is not settled, and names the two cases everybody in the field is asking about.

Case one — card-scheme rules
Credit-card schemes require online merchants to apply strong authentication to their customers. Does a merchant's contract with its acquirer, or the scheme rules it accepts by taking cards, amount to a contractual obligation to use strong user authentication? Unclear.
Case two — internal group policies
A group security policy that requires two-factor or strong authentication for its own staff and customers. Whether an internal policy is a contractual obligation at all is likewise unclear.
The two readings
On a broad reading, many companies outside regulated sectors such as payment services would also be covered. On a narrow reading, only companies that have specifically committed to strong authentication vis-à-vis their users would be. The distance between those two readings is most of the practical effect of Article 5f(2).

A card terminal is not an answer to this — and neither is this page

If you take card payments online and you sit above the micro and small enterprise line, you are in the group for whom this question decides whether the wallet becomes a login method you must offer from 24 December 2027. Nothing in the sources we read resolves it: not the Regulation, not the implementing acts, not the Commission's policy page. Watch for guidance from the Commission or from the national registration body — and read this section again before you buy an identity integration. It is not legal advice.

Registering as a relying party

Registration is the gate in front of the wallet, and it applies to everybody — including a business that accepts the wallet only voluntarily. Any party wishing to request data from a wallet must register in the member state in which it is established (Article 5b(1)). The rules of the register are in Implementing Regulation (EU) 2025/848 of 6 May 2025.

What you have to disclose — Article 5b(2), Annex I to 2025/848
Your name and registration identifier (in Germany usually the commercial register number), contact details, your privacy policy, and the intended use together with the categories of data you want to request.
What that permission then covers — Article 5b(3)
The registered intended use sets the permissible scope of your data requests. A relying party may not request data beyond the scope of its registration. The wallet checks a request against the certificate and may reject one that exceeds the registered purposes — or leave the decision to the user.
One registration, the whole Union
The Regulation provides only for registration in the member state of establishment (Article 5b(1)) and no separate registration in the others. A company registered in Germany may therefore request the registered attributes from users in other member states.
Germany's registration body
The federal Digital Identities Act (Digitale Identitätengesetz, DIdG) designates the Federal Office of Administration (Bundesverwaltungsamt) as the central registration body — that is the briefing's reading of the Act, which it cites as Bundestag documents 21/7408 and 8617. We have not read the Act itself; our note on the DIdG sets out what is known about it, including the Bundestag vote of 15 October 2026: the d-you wallet and the DIdG.

Germany, Denmark, Sweden

The 24 December 2026 date is a duty on member states, and the member states are not at the same point. The briefing names Italy, France and Finland — on press reports, not on any official scoreboard — as the most advanced, developing existing government apps into wallets and offering test environments for relying parties. Three countries matter most to a German-speaking reader.

Germany — "d-you", launch 2 January 2027
The federal digital ministry presented the German wallet under the name d-you in mid-September 2026 (BMDS press release of 14 September 2026, as cited by the briefing), and the launch is announced for 2 January 2027 — formally after the EU deadline. Around 40 partners from business, academia and public administration are expected at launch with use cases such as age verification, concluding contracts and opening accounts. It is free of charge and voluntary, stores its data encrypted on the device, and its source code has been published. SPRIND has been running a test environment for relying parties since December 2025, and certification of the wallet under Article 5c eIDAS 2.0 had not been completed when the briefing was written.
Denmark — "AltID", in production since June 2026
Denmark put its national wallet, AltID, into production in June 2026. On the briefing's account it is the clearest example of a wallet that is already live rather than announced.
Sweden — nothing before 2028
Sweden does not plan to provide a wallet before 2028, according to its own roadmap as the briefing reports it. That is a member state announcing it will miss a date it is bound by, not a Swedish exemption from the Regulation.
Why "launch" and "certified" are two different facts
A wallet that launches is not yet a wallet the EU recognises. Article 5c certification is what the Kids Act cross-reference below actually depends on, and German reporting has already questioned whether d-you will carry the required characteristics at launch. Our DIdG note has that detail and the sources behind it.

The link to the EU Kids Act

The wallet and the age-verification debate are the same rail, and the Commission's EU Kids Act proposal of 17 September 2026 is where they meet. Under Article 16(6) of that proposal, providers of software application stores must allow the EU age verification solution — using an EU proof of age attestation certified as conforming with the EU Age Verification Scheme — to be offered in their store. Under Article 29(3), an EUDI Wallet certified under Article 5c eIDAS 2.0 that complies with the requirements of that Scheme is deemed to be such a solution.

What that settles
A certified wallet counts as a compliant age-verification route for the proposal's purposes. That is the bridge from the identity rail to the youth protection file, and it is why the two timetables are read together.
What it does not settle
Whether an app store must merely make the wallet available for download, or must also accept it itself when verifying the age of its own users, which the proposal separately requires of app stores (Article 16(4)). The briefing flags the question and does not answer it.
And it is still a proposal
Nothing in the Kids Act is law. The draft is with the European Parliament and the Council, and the Commission's feedback window closes on 3 December 2026. Our note on the proposal has the seven categories, the age tiers and the exemption question; the age-verification explainer has the four words — attestation, assurance, verification, age signal — that decide what any of it would ask of you.

What the firms say to review now

The briefing closes with a four-part checklist for businesses. We repeat it because it is specific, and because most of it is work you can do without buying anything.

Scope
For each legal entity and each service: is there a statutory or contractual obligation to use strong user authentication, or are you a very large online platform? Would the Kids Act, if adopted, create an age-verification duty for you?
Attributes, not vendors
Which attributes are actually required in which process? That question comes before any product decision — and it is the one that determines what you may register for later.
Registration
Identify the competent registration body, define the intended uses, update the privacy policy, and decide between in-house integration and an intermediary.
Contracts and testing
Review contracts with identity and KYC providers for the amendments a wallet route would need, and use the test environments — Germany's SPRIND environment has been open to relying parties since December 2025.
For a one-person shop the answer is usually "not yet". You are most likely exempt from the acceptance duty, no member state can oblige you to use a wallet yourself, and the wallet is voluntary for your customers. The reason to read this page now is the registration question: the moment you want a wallet to answer an age or identity question for you, the register comes first.

Private credentials are arriving before the EU wallet

The wallet this page is about is not the only credential a customer may offer. On 21 October 2026 the country picker inside Google Wallet's ID pass — a copy of a passport held on an Android phone — began showing Ireland and Italy, according to app screenshots published by 9to5Google and relayed in a report of 22 October 2026. Google's own help page, Create or manage your ID pass, still listed only Brazil, Singapore, Taiwan, the United Kingdom and the United States when we read it on 23 October 2026, and the rollout is described as gradual and server-side.

It is not an EUDI Wallet
It is a private credential from a private company, and Google's page says an ID pass "isn't an official form of identification or a replacement for your physical documentation". It is not a wallet provided under Article 5a, so the registration route and the acceptance duty described above do not attach to it. A business that accepts it is not thereby meeting a wallet obligation, and one that does not is not failing one.
The requirements, and the travel limit
An Android 9 or later phone with NFC, an active screen lock and a valid passport with a readable chip; one passport yields one pass, which must be removed from one phone before it is created on another. Google's page states that for non-US regions ID passes "can't be used for immigration or travel", so the physical passport stays the document the law requires.
A reported "November 2026" EU wallet date that we do not use
A November 2026 date for the EU wallet circulates with coverage of that rollout. We could not confirm it in the article itself, and it conflicts with the 24 December 2026 deadline recorded above, which is counted from the implementing acts of 24 December 2024 rather than taken from a report. The date on this page stays the one in the acts.
For a small seller the position is unchanged. Nothing we read obliges you to accept a private wallet credential, no Irish, Italian or EU authority is quoted as accepting it for a statutory age check, and the questions on this page still turn on the EUDI Wallet.

What we could not establish

The Regulation itself, this time
We worked from a law-firm briefing of 22 October 2026, not from the Regulation. EUR-Lex did not respond to us on 22 October 2026, so Articles 5a, 5b and 5f are quoted here as the briefing sets them out, together with our own earlier reading of Regulation (EU) 2024/1183 for the age-verification explainer. The article numbers, the two dates and the exemption are consistent across both, but they are not a substitute for the text: open it before you rely on a paragraph number.
How far "contractual obligation" reaches
Unresolved in every source we read, including the briefing — see the card-scheme section. We found no Commission guidance on the point.
The German Act's own wording
We have not read the DIdG. The Federal Office of Administration as registration body, and the Bundestag document numbers, are the briefing's citations. Our separate note records that the ministry's page still carried the referral draft in October 2026.
Whether the dates will be met
Germany's announced launch of 2 January 2027 is already after 24 December 2026, and certification under Article 5c was outstanding when the briefing was written. The briefing's own conclusion is that the deadlines are fixed but whether the technical systems will be operational in time will only become clear in 2027. We have no Austrian step to report on any of this, and we add none.
What the wallet will cost a relying party
We have no figure from any source for integration, certification or registration. If you have one with a name and a date attached, that is exactly the kind of evidence our Observatory collects.

Sources

One legal briefing carries most of this page, and we say so at every step rather than presenting its readings as the text. The official sources below are the act itself and the Commission's policy page; where we could not open an official source, the page says which and why.

  1. Taylor Wessing — EU EUDI-Wallet: New Duties for Businesses Secondary, legal analysis, 22 October 2026, by Paul Voigt, Wiebke Reuter and Richard Gläser. Source for the two deadlines and their arithmetic from the implementing acts of 24 December 2024, Articles 5a(1), 5a(4), 5a(15), 5f(1)–(3), 5b(1)–(3) and 5c as the firm sets them out, the eleven example sectors, the micro and small enterprise exemption by reference to Recommendation 2003/361/EC, the unsettled "contractual obligation" question including card-scheme rules and group policies, the two readings of it, the registration data and Annex I to Implementing Regulation (EU) 2025/848, the Bundesverwaltungsamt as German registration body, the state of play in Italy, France, Finland, Denmark, Sweden and Germany, and the Kids Act cross-reference in Articles 16(6), 16(4) and 29(3). Read in full 22 October 2026
  2. EUR-Lex — Regulation (EU) 2024/1183 establishing a framework for a European Digital Identity The act itself. Cited for the article numbering and the obligations, but not opened on 22 October 2026: EUR-Lex returned no text to us. The same link is listed in the age-verification explainer, where the Regulation was read earlier for the Article 5a and 5f(2) points
  3. European Commission — European Digital Identity (EUDI) Regulation Official policy page, last updated 22 June 2026, read 22 October 2026. Source for the Commission's own words that the framework mandates member states to provide EU Digital Identity Wallets by the end of 2026, and that service providers legally obliged to identify their customers unequivocally will be obliged to accept the wallet for authentication
  4. EUR-Lex — Implementing Regulation (EU) 2025/848 on the registration of relying parties The implementing act on the register, dated 6 May 2025 as the briefing cites it. Not opened: EUR-Lex returned no text to us on 22 October 2026. The registration details on this page are taken from the briefing's citation of Article 5b(2) and Annex I, not from the act
  5. KontorBund — Germany's under-13 social media ban, and the d-you wallet Our own note on the Bundeskabinett's key-points paper of 14 October 2026 and on the DIdG, passed by the Bundestag on 15 October 2026: the launch date of 2 January 2027, the launch partners, the missing pseudonymous login, and the doubt about whether the wallet will carry the required characteristics at launch
  6. KontorBund — the EU Kids Act proposal Our note on COM(2026) 681: the seven categories, the age tiers at 13 and 15, the age-assurance duties in Articles 28 to 32 and the 3 December 2026 feedback deadline
  7. KontorBund — age verification and age assurance The explainer that sorts attestation, assurance, verification and age signal — and the page this one hands the wallet question back to when the question is really about age
  8. Google Wallet Help — Create or manage your ID pass Official, read 23 October 2026, added the same day for private credentials are arriving first. Source for the five supported regions — Brazil, Singapore, Taiwan, the United Kingdom and the United States of America — for the Android 9, NFC, screen-lock and valid-passport requirements, for one pass per passport, for the statement that a pass "isn't an official form of identification or a replacement for your physical documentation", and for non-US passes not being usable for immigration or travel. The page names no country beyond those five, so Ireland and Italy are not taken from it
  9. Pasquale Pillitteri — "Google Wallet passport arrives in Italy and Ireland", relaying 9to5Google Secondary, dated 22 October 2026 by the page itself. Used for one thing only: that the country picker began showing Ireland and Italy on 21 October 2026, on the strength of app screenshots, and that the rollout is gradual and server-side. The article body did not load for us; the date and the claim are taken from the page's own description and question-and-answer block. The "November 2026" wallet date associated with that coverage is not used — see the conflict recorded above

Tell us what we got wrong

The two dates are fixed; the "contractual obligation" question is not, and a single piece of Commission guidance would settle it. If you find one — or a national registration body's own guidance, or a cost figure for relying-party registration with a name attached — bring it in. A source we can open beats ten pages of commentary, and we will correct this page in public.