In force since 20 May 2024 (Art. 2; OJ L 2024/1183, 30.4.2024); it amends Regulation (EU) No 910/2014 and sets no separate application date. Two dated duties follow from the implementing acts under Arts 5a(23) and 5c(6), in force since 24 December 2024: each Member State must provide a European Digital Identity Wallet within 24 months, by 24 December 2026 (Art. 5a(1); clm-eidas2-wallets), and private relying parties that must use strong user authentication — except micro and small enterprises — must accept the wallet at the user's voluntary request within 36 months, by 24 December 2027 (Art. 5f(2); clm-eidas2-private-acceptance). The first is a duty on Member States, the second a qualified duty on some businesses, not on all. Re-read on 27 Oct 2026 in the Official Journal text retrieved from Cellar.
In short: what you need to know
Objective: Secure electronic identification and trust services across the internal market, extended by the European Digital Identity Wallets each Member State must provide and recognise.
Who it binds: Member State · Public authority · Large company · Very large online platform · Trust service provider
Who it protects:not established
Core obligations: eIDAS2 Art. 5a (of Regulation (EU) No 910/2014, as inserted) · eIDAS2 Art. 5f (of Regulation (EU) No 910/2014, as inserted) key provisions →
Sanction ceiling:not establishedNo ceiling at EU level: Art. 16(2) of Regulation (EU) No 910/2014, as replaced, requires Member States to set administrative fines for trust service providers with a maximum of at least EUR 5 000 000 or, for a legal person, 1 % of worldwide annual turnover if higher. A floor for the national maximum, not a ceiling.enforcement →
What does the eIDAS2 do?
Secure electronic identification and trust services across the internal market, extended by the European Digital Identity Wallets each Member State must provide and recognise.
Regulated actor
Member State · Public authority · Large company · Very large online platform · Trust service provider
Protected party
not established
Territorial reach
not established
Implementation model
Directly applicable
Enforcement mechanism
not established
When does the eIDAS2 apply? Key dates
Entry into force, application and transposition are different events and are kept apart. A date at month precision is shown as a month rather than invented as a day.
20 May 2024Entry into forceEntry into force
24 December 2026Compliance deadlineEach Member State must provide at least one European Digital Identity Wallet (Art. 5a(1)). A deadline for Member States, not for businesses.
24 December 2027Compliance deadlinePrivate relying parties that Union or national law or a contract requires to use strong user authentication for online identification must also accept European Digital Identity Wallets, only at the user's voluntary request (Art. 5f(2)). Microenterprises and small enterprises are excluded.What it requires: Where strong user authentication is already required, be able to accept the wallet when a user chooses to use it.
1 rule in the dataset turn on this instrument. They are conditions, not a test: the engine ranks them against what you actually answer, and downgrades rather than excludes where a question is left blank.
Potentially applicable
activity Providing digital identity services
Under the European Digital Identity framework (Regulation (EU) No 910/2014 as amended by Regulation (EU) 2024/1183), each Member State must provide at least one European Digital Identity Wallet within 24 months of the entry into force of the implementing acts under Arts 5a(23) and 5c(6), which entered into force on 24 December 2024. The rule covers the wallet obligation only.
2 provisions recorded. This is what the dataset holds, not the whole instrument — an article that is not here has not been entered, which is a different statement from its not existing.
Article
Heading
Binds
Applies
Art. 5a (of Regulation (EU) No 910/2014, as inserted)load-bearing
European Digital Identity WalletsEach Member State must provide at least one European Digital Identity Wallet within 24 months of the entry into force of the implementing acts referred to in Art. 5a(23) and Art. 5c(6).
Member State
no application date recorded for this article
Art. 5f (of Regulation (EU) No 910/2014, as inserted)load-bearing
Cross-border reliance on European Digital Identity WalletsPublic-sector online services that require electronic identification must also accept the wallet (5f(1)). Private relying parties required by Union or national law, or by contract, to use strong user authentication for online identification — except microenterprises and small enterprises — must also accept it, no later than 36 months from the entry into force of the implementing acts under Arts 5a(23) and 5c(6) and only upon the user's voluntary request (5f(2)). Very large online platforms that require user authentication must accept and facilitate it at the user's voluntary request (5f(3)).
Large company · Public authority · Very large online platform
no application date recorded for this article
How is the eIDAS2 enforced?
No enforcement recorded
This dataset holds no enforcement action under this instrument. That is what the record says; it is not a finding that none has been taken.
Every statement this site makes about eIDAS2, graded by what actually carries it. The grade is derived from the claim type and its sources, never stored, so it cannot drift from what it describes.
The instrument record itself was last verified on 27 October 2026; every claim below carries its own date.
2 Primary law
Primary lawlaw
Under eIDAS2 each Member State must provide at least one European Digital Identity Wallet within 24 months of the entry into force of the implementing acts under Articles 5a(23) and 5c(6) of Regulation (EU) No 910/2014; those acts entered into force on 24 December 2024, which puts the deadline at 24 December 2026.
From 24 December 2027, private relying parties that Union or national law or a contract requires to use strong user authentication for online identification must also accept European Digital Identity Wallets, but only at the user's voluntary request; microenterprises and small enterprises are excluded.
1 recorded interaction with other instruments — each with a direction, the provisions that carry it and its own sources. Direction is preserved as recorded: an instrument that amends another is not the same as one amended by it.
This instrument leaves a matter to the other: a without-prejudice clause, a 'shall not affect' clause or an express reference sending the reader there. The locator is in the DEFERRING instrument's text (from). Added 27 Oct 2026 (docs/V2-DATA-DESIGN.md §1.4).
The eIDAS Regulation, as amended by eIDAS2, is without prejudice to the GDPR.