eIDAS 2.0 and the EUDI Wallet: What Changes for Businesses
András Somkuti, CEO & Founder · Updated 11 November 2026
eIDAS 2.0 is the common name for Regulation (EU) 2024/1183, which amended the eIDAS Regulation (EU) No 910/2014 to establish the European Digital Identity Framework. It requires every member state to provide at least one European Digital Identity Wallet (EUDI wallet), adds new trust services and leaves the three electronic signature levels and their legal effect unchanged.
What Is eIDAS 2.0?
eIDAS 2.0 updates the EU’s rules on electronic identification and trust services, and it builds the qualified electronic signature into a new digital identity: every European Digital Identity Wallet must let its user sign with one. Formally, it is Regulation (EU) 2024/1183 “of 11 April 2024 amending Regulation (EU) No 910/2014 as regards establishing the European Digital Identity Framework”.
It is not a new regulation. It amends the original eIDAS Regulation, Regulation (EU) No 910/2014 “of 23 July 2014”, so the law you read today is still Regulation 910/2014, in a consolidated version that includes the 2024 changes.
Regulation 2024/1183 “shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union” (Article 2). It was published in the Official Journal on 30 April 2024, so it entered into force on 20 May 2024. Like the original, it is “binding in its entirety and directly applicable in all Member States”.
One limit stays: eIDAS “does not affect Union or national law related to the conclusion and validity of contracts, other legal or procedural obligations relating to form, or sector-specific requirements relating to form” (Article 2(3)). If national law requires a notarial deed for a transaction, eIDAS 2.0 does not change that.
eIDAS 1.0 vs 2.0: What Changed?
eIDAS 2.0 adds a digital identity layer and four new trust services, and it leaves the signature rules most businesses rely on as they were:
| Area | What eIDAS 2.0 changed | Where |
|---|---|---|
| European Digital Identity Wallet | New: every member state provides at least one wallet | Articles 5a–5f |
| Electronic attestation of attributes | New trust service; qualified attestations have the same legal effect as paper ones | Article 3(44)–(46), Articles 45b–45h |
| Electronic archiving | New trust service; qualified archiving gives a presumption of integrity and origin | Article 3(48)–(49), Articles 45i–45j |
| Electronic ledgers | New trust service; qualified ledgers give a presumption of order and integrity | Article 3(52)–(53), Articles 45k–45l |
| Remote signing devices | Managing remote qualified signature creation devices is a trust service of its own, and can be qualified | Article 3(16)(f) and (23a), Article 29a |
| Identity checks for qualified certificates | A new list of methods, including the wallet | Article 24(1a) |
| Cross-border recognition | Moved from Article 25(3) to a new Article 24a that covers all qualified trust services | Article 24a |
| Website authentication | Browsers must recognise qualified certificates for website authentication (often called QWACs) | Article 45(1a) |
| Signature levels and their legal effect | Unchanged | Article 3(10)–(12), Article 25(1)–(2) |
What Is the EUDI Wallet?
The EUDI wallet is an electronic identification means that, under Article 3(42), “allows the user to securely store, manage and validate person identification data and electronic attestations of attributes for the purpose of providing them to relying parties and other users of European Digital Identity Wallets, and to sign by means of qualified electronic signatures or to seal by means of qualified electronic seals”. The main rules:
- Voluntary. “The use of European Digital Identity Wallets shall be voluntary.” Access to public and private services “shall not in any way be restricted or made disadvantageous” for people who don’t use one (Article 5a(15)).
- Free for individuals. “The issuance, use and revocation of the European Digital Identity Wallets shall be free of charge to all natural persons.” (Article 5a(13))
- High assurance. Wallets are provided “under an electronic identification scheme with assurance level high” (Article 5a(11)).
- Under the user’s control. Users share data “under the sole control of the user”, “while ensuring that selective disclosure of data is possible” (Article 5a(4)(a)), and “Users shall have full control of the use of and of the data in their European Digital Identity Wallet” (Article 5a(14)).
For businesses, this changes the starting point. The user carries trusted data and presents it, and selective disclosure means a company may receive less data than it does today, with stronger evidence behind it.
eIDAS 2.0 Timeline: The Dates in the Regulation
eIDAS 2.0 ties its main wallet deadlines to the Commission’s implementing acts rather than to calendar dates. These are the dates the official texts state:
| Date or period | What the text says | Source |
|---|---|---|
| 1 July 2016 | The eIDAS Regulation applies “from 1 July 2016”, with some exceptions | Regulation 910/2014, Article 52(2) |
| 11 April 2024 | Regulation (EU) 2024/1183 is adopted; it enters into force on the twentieth day after its publication in the Official Journal (published 30 April 2024), that is, on 20 May 2024 | Regulation 2024/1183, title and Article 2 |
| By 21 November 2024 | Deadline for the Commission’s implementing acts on the wallet and on its certification | Articles 5a(23) and 5c(6) |
| 28 November 2024 | The Commission adopted Implementing Regulations (EU) 2024/2977, 2024/2979, 2024/2980 and 2024/2982 under Article 5a(23), and (EU) 2024/2981 under Article 5c(6); all five were published in the Official Journal on 4 December 2024 | The implementing regulations |
| By 21 May 2025 | Deadline for implementing acts on identity checks for qualified certificates, remote signing devices, qualified website certificates, qualified archiving and qualified ledgers | Articles 24(1c), 29a(2), 45(2), 45j(2) and 45l(3) |
| Within 24 months of the wallet implementing acts’ entry into force | Every member state provides at least one wallet | Article 5a(1) |
| Within 36 months of the same date | Regulated private relying parties accept the wallet at the user’s request | Article 5f(2) |
Each of the five implementing regulations “shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union”, and the 24-month and 36-month periods run from that entry into force. In the regulation’s own words, “each Member State shall provide at least one European Digital Identity Wallet within 24 months of the date of entry into force of the implementing acts referred to in paragraph 23 of this Article and in Article 5c(6)” (Article 5a(1)).
The technical specifications in these implementing regulations “rely on the work carried out on the basis of Commission Recommendation (EU) 2021/946 … and in particular the architecture and reference framework which is part of it” (recital 4 of Implementing Regulation (EU) 2024/2977). That architecture and reference framework is often shortened to ARF.
Who Has to Accept the EUDI Wallet?
Three groups must accept the wallet, in each case when the user chooses to use it:
- Public sector bodies. “Where Member States require electronic identification and authentication to access an online service provided by a public sector body, they shall also accept European Digital Identity Wallets” (Article 5f(1)).
- Regulated private services. Private relying parties that are required by law or by contract to use strong user authentication for online identification, “including in the areas of transport, energy, banking, financial services, social security, health, drinking water, postal services, digital infrastructure, education or telecommunications”, must accept the wallet “no later than 36 months from the date of entry into force of the implementing acts referred to in Article 5a(23) and Article 5c(6) and only upon the voluntary request of the user” (Article 5f(2)). Microenterprises and small enterprises are exempt.
- Very large online platforms. Where they require user authentication, they must accept the wallet “only upon the voluntary request of the user and in respect of the minimum data necessary for the specific online service for which authentication is requested” (Article 5f(3)).
What eIDAS 2.0 Requires From Relying Parties
For companies, preparing for the wallet era involves more than adding a new button to an onboarding screen. A relying party that intends to rely on the wallet “shall register in the Member State where it is established” (Article 5b(1)), and its registration states “the intended use of European Digital Identity Wallets, including an indication of the data to be requested by the relying party from users” (Article 5b(2)(c)). After that, “Relying parties shall not request users to provide any data other than that indicated” (Article 5b(3)).
Today, a KYC form often begins with a list of fields the company has always collected. Under eIDAS 2.0, the data a wallet journey asks for is fixed up front in the registration.
Product and compliance teams also have to settle which issuers and credential types they accept and how they validate them, because “Relying parties shall be responsible for carrying out the procedure for authenticating and validating person identification data and electronic attestation of attributes requested from European Digital Identity Wallets” (Article 5b(9)). That makes data minimisation a design decision rather than an afterthought.
Can You Sign With the EUDI Wallet?
Yes. The wallet is a new way to sign with a QES, not a new kind of signature:
- It signs. Wallets must enable the user to “sign by means of qualified electronic signatures or seal by means of qualified electronic seals” (Article 5a(4)(e)).
- For individuals, by default and free. Wallets must “offer all natural persons the ability to sign by means of qualified electronic signatures by default and free of charge” (Article 5a(5)(g)). However, “Member States may provide for proportionate measures to ensure that the use of qualified electronic signatures free-of-charge by natural persons is limited to non-professional purposes.” Depending on your member state, signing for your company may fall outside the free offer.
- It can prove who you are for a qualified certificate. Before issuing a qualified certificate, a provider can verify your identity “by means of the European Digital Identity Wallet” (Article 24(1a)(a)) or by one of the other methods that Article 24(1a) lists.
- The legal effect stays the same. A wallet signature is a QES like any other: it “shall have the equivalent legal effect of a handwritten signature” (Article 25(2)), and a QES based on a qualified certificate issued in one member state is recognised as a QES “in all other Member States” (Article 24a(1)).
So a QES doesn’t have to wait for the wallet. Qualified trust service providers issue qualified certificates today, and a QES you create now keeps its legal effect under eIDAS 2.0. If you want to know what makes an electronic signature qualified, our separate article explains the requirements, and if a document comes from your organisation rather than from a person, a qualified electronic seal may be the better fit.
With Netlock, you can sign up for free and have a working QES 1 minute after you register. You identify yourself remotely with the identity card or passport of any EU member state, a US passport or driver’s licence, or in Hungary DÁP: video identification works on any device with a camera and needs no separate app, and the Netlock mobile app with a chip identity card is faster still. The identification is automatic, and a member of our staff checks it when needed. We also plan to support EU digital identity wallets for identification, and we have no date to give yet. The app and the qualified certificate are free, and you get 15 free signatures. After that, each signature costs 1 credit (see pricing).
Netlock is a qualified trust service provider: its entry in the EU trusted lists shows qualified certificates for electronic signatures, electronic seals and website authentication, and qualified timestamping.
New Trust Services in eIDAS 2.0
eIDAS 2.0 adds four trust services to the list in Article 3(16) and sets rules for their qualified versions:
- Electronic attestation of attributes: “an attestation in electronic form that allows attributes to be authenticated” (Article 3(44)). An attribute is “a characteristic, quality, right or permission of a natural or legal person or of an object” (Article 3(43)). Annex VI lists attributes that member states must make verifiable against public authentic sources, among them “Age”, “Educational qualifications, titles and licences” and “Powers and mandates to represent natural or legal persons”. “A qualified electronic attestation of attributes and attestations of attributes issued by, or on behalf of, a public sector body responsible for an authentic source shall have the same legal effect as lawfully issued attestations in paper form.” (Article 45b(2))
- Electronic archiving: a service for the receipt, storage, retrieval and deletion of electronic data and documents “in order to ensure their durability and legibility as well as to preserve their integrity, confidentiality and proof of origin throughout the preservation period” (Article 3(48)). Documents kept in a qualified electronic archiving service “shall enjoy the presumption of their integrity and of their origin for the duration of the preservation period by the qualified trust service provider” (Article 45i(2)).
- Electronic ledgers: “a sequence of electronic data records, ensuring the integrity of those records and the accuracy of the chronological ordering of those records” (Article 3(52)). Records in a qualified electronic ledger “shall enjoy the presumption of their unique and accurate sequential chronological ordering and of their integrity” (Article 45k(2)).
- Management of remote signing devices: a “remote qualified electronic signature creation device” is one “managed by a qualified trust service provider in accordance with Article 29a on behalf of a signatory” (Article 3(23a)). As a qualified service, the provider “generates or manages electronic signature creation data on behalf of the signatory” under the conditions of Article 29a(1), and the service is recognised in every member state (Article 24a(3)).
Two more points matter to businesses. First, qualified certificates for website authentication “shall be recognised by providers of web-browsers” (Article 45(1a)).
Second, attestations move trust towards the issuer. When a company receives a PDF scan, much of the verification burden sits with the receiving organisation: Is the document genuine? Has it been altered? Is the information current? Does it belong to the applicant? With a verifiable attestation, the recipient can assess the issuer, the credential, its cryptographic validity and, where relevant, its status, rather than inferring authenticity from an image of a physical document.
What eIDAS 2.0 Means for Your KYC and Cross-Border Business
Cross-Border Identity Becomes More Practical
Interoperability across member states is one of the framework’s central aims: the regulation sets out to avoid “the fragmentation of and barriers in the internal market, due to diverging standards and technical restrictions” (recital 70 of Regulation (EU) 2024/1183). The wallet framework requires wallets to “support common protocols and interfaces” (Article 5a(5)(a)), and public sector bodies that require electronic identification must also accept wallets (Article 5f(1)). The transition will not remove every national or sector-specific requirement, but it can reduce some of the friction created by incompatible identity systems.
The Wallet Will Not Make Every KYC Process Disappear
It is tempting to read reusable digital identity as the end of onboarding, but regulated relationships involve questions that go beyond identity: beneficial ownership, sanctions exposure, source of funds, transaction monitoring, the authority to represent a legal entity and sector-specific information. Our articles on KYC, KYB and UBO and on why identity is not authority explain those layers.
What changes is the quality and portability of the foundational evidence. The EU’s Anti-Money Laundering Regulation, which applies from 10 July 2027 for most obliged entities (Article 90), lets them verify a customer’s identity through “the use of electronic identification means which meet the requirements of Regulation (EU) No 910/2014 with regard to the assurance levels ‘substantial’ or ‘high’ and relevant qualified trust services as set out in that Regulation” (Article 22(6)(b) of Regulation (EU) 2024/1624).
If an attribute has already been issued through a trusted framework and can be validated cryptographically, there is little value in pretending that the recipient must rediscover the same fact from scratch.
How to Prepare for eIDAS 2.0: A Checklist
- Check whether you must accept the wallet. Does a law or a contract require you to use strong user authentication for online identification? Are you a micro or small enterprise? (Article 5f(2))
- List the data each journey really needs. Your registration as a relying party names the data you will request, and you can’t ask for more (Article 5b(2)(c) and (3)).
- Plan your registration in the member state where you are established (Article 5b(1)).
- Decide which attestations and issuers you accept, and how you will validate them; validation is your responsibility (Article 5b(9)).
- Keep other routes open. Customers who don’t use a wallet must not be disadvantaged (Article 5a(15)).
- Sort out signatures now. Use a QES where you need the effect of a handwritten signature, a qualified seal for documents your organisation issues, and validate the electronic signatures you receive.
- Follow the implementing acts and your member state’s national rules as they appear.
FAQ
eIDAS 2.0 is the common name for Regulation (EU) 2024/1183, which amended the eIDAS Regulation (EU) No 910/2014 on electronic identification and trust services. The regulation itself doesn’t use the acronym; the European Commission’s eIDAS page labels it “eIDAS - electronic identification and trust services”.
Not for users: “The use of European Digital Identity Wallets shall be voluntary.” (Article 5a(15)) Public sector bodies and some regulated private services must, however, accept the wallet when a user chooses to use it (Article 5f).
Yes, for individuals: “The issuance, use and revocation of the European Digital Identity Wallets shall be free of charge to all natural persons.” (Article 5a(13))
Private relying parties that must use strong user authentication for online identification must accept it “no later than 36 months from the date of entry into force of the implementing acts referred to in Article 5a(23) and Article 5c(6)”, at the user’s voluntary request (Article 5f(2)). The regulation gives no calendar date. Microenterprises and small enterprises, as defined in Commission Recommendation 2003/361/EC, are exempt; if they choose to rely on the wallet, they register as relying parties like anyone else (Article 5b(1)).
No. A qualified electronic signature is based on a qualified certificate, which is “issued by a qualified trust service provider” (Article 3(15)), and wallets must support common protocols “for issuance of person identification data, qualified and non-qualified electronic attestations of attributes or qualified and non-qualified certificates to the European Digital Identity Wallet” (Article 5a(5)(a)(i)).
Yes. eIDAS 2.0 did not change Article 25(2): a QES “shall have the equivalent legal effect of a handwritten signature”. A QES is validated as of the time of signing (Article 32(1)). Netlock’s signing certificate is valid for 2 years, and renewal is one click and done in minutes.
On EUR-Lex. The consolidated eIDAS Regulation includes the eIDAS 2.0 amendments, and Regulation (EU) 2024/1183 is published separately. The consolidated text is “meant purely as a documentation tool and has no legal effect”; the version published in the Official Journal is authentic.
You don’t need to wait for a wallet to sign with legal effect. Sign up for free, get your qualified electronic signature in 1 minute and start with 15 free signatures.
Related Articles
Sources
- eIDAS Regulation (EU) No 910/2014, consolidated text of 18 October 2024 (02014R0910 — EN — 18.10.2024 — 002.003): https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02014R0910-20241018 (Article 2(3); 3(16), (23a), (42)–(44), (48), (52); 5a(1), (4)(a), (4)(e), (5)(a), (5)(g), (11), (13)–(15), (23); 5b(1), (2)(c), (3), (9); 5c(6); 5f(1)–(3); 24(1a)(a), (1c); 24a(1), (3); 25(2); 29a(1)–(2); 32(1); 45(1a), (2); 45b(2); 45i(2); 45j(2); 45k(2); 45l(3); 51(4); 52(2); Annex VI).
- Regulation (EU) 2024/1183 (eIDAS 2.0), title, recital 70, Article 1 (deletion of Article 25(3)) and Article 2; Official Journal L, 30.4.2024: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32024R1183
- Commission Implementing Regulations of 28 November 2024, Official Journal of 4 December 2024: (EU) 2024/2977 (person identification data and electronic attestations of attributes; recital 4 on the architecture and reference framework), https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32024R2977; (EU) 2024/2979 (integrity and core functionalities), https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32024R2979; (EU) 2024/2980 (notifications), https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32024R2980; (EU) 2024/2981 (certification, under Article 5c(6)), https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32024R2981; (EU) 2024/2982 (protocols and interfaces), https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32024R2982
- Regulation (EU) 2024/1624 (Anti-Money Laundering Regulation), Article 22(6)(b) and Article 90: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32024R1624
- European Commission, eIDAS Regulation page: https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation
- EU trusted lists, Netlock: https://eidas.ec.europa.eu/efda/trust-services/browse/eidas/tls/tl/HU/tsp/6 (Hungarian trusted list issued 2026-10-19)