The Plain-English Guide to eIDAS 2.0 and the EU Digital Identity Wallet

eIDAS 2.0 is the informal name for Regulation (EU) 2024/1183, the law that amends the original eIDAS Regulation (910/2014) and builds the European Digital Identity framework on top of it. It's not a replacement, it's an amendment. The three-tier e-signature system you already know (SES, AES, QES) stays exactly as it was. What eIDAS 2.0 adds is a new layer: a government-backed digital identity wallet every EU citizen and resident will be able to use, and a legal obligation for large swaths of the private sector to accept it.

The regulation was adopted on 11 April 2024, published in the Official Journal on 30 April 2024, and entered into force in May 2024. (You'll see a handful of sources cite slightly different days in that window; treat EUR-Lex as the authoritative source if you need the exact date for a legal filing.)

If you run a business that signs contracts, verifies customer identity, or operates in a regulated sector anywhere touching the EU, eIDAS 2.0 is worth understanding now, not in late 2027 when the mandatory-acceptance deadline actually lands.

eIDAS 1.0 was mostly a public-sector story. It let EU governments issue eID schemes and required cross-border recognition between member states, but it never forced private companies to accept anyone's digital ID. eIDAS 2.0 changes that scope in three concrete ways.

First, it extends acceptance obligations from the public sector into a defined list of private industries: banks, payment and e-money institutions, telecoms, transport, energy, healthcare, education, and very large online platforms (VLOPs) with more than 45 million EU users. Second, it standardizes cross-border interoperability through Implementing Acts and ETSI technical standards, so a wallet issued in Portugal has to work the same way when presented to a business in Germany. Third, it tightens privacy and data-minimization rules: a wallet has to let you share only the specific attribute a relying party actually needs (say, "is over 18") rather than handing over your entire identity record.

None of that touches the legal definitions of SES, AES, or QES under Article 25 of the amended regulation. A qualified electronic signature still carries the same "equivalent legal effect to a handwritten signature" status it always did. What's new is *how* the identity behind that signature gets proven, increasingly through a wallet credential instead of a one-off video call or ID-document upload.

The European Digital Identity Wallet (EUDI Wallet) is a free, government-issued app that stores your verified identity and lets you selectively share pieces of it (a driver's license, a diploma, proof of age, a bank KYC credential) with businesses and public services that need to check who you are.

Think of it less like a single ID card and more like a secure folder of verifiable credentials you control. You decide what to share, with whom, and for how long. Wallets get certified against the technical and security requirements set out in Implementing Acts, the first of which started appearing in December 2024, with more following through 2025 as ETSI standards work matures.

Here's the honest caveat: as of mid-2026, wallet rollout is still uneven across member states. Some governments are running large pilots (the EU-funded Large Scale Pilots consortiums have been testing wallet use cases like SIM registration, age verification, and diploma checks since 2023), while others are further behind on production deployment. The regulation gives every member state a hard deadline to have at least one certified wallet available, and the table further down maps out exactly when that deadline lands.

eIDAS 2.0 didn't arrive with a single flip-the-switch date. It's rolling out in stages, and the two dates that matter most for a business sit at the bottom of the table below. Miss the first one and you're not compliant with an offering obligation; miss the second and you're not compliant with an acceptance obligation.

According to the European Commission's EUDI regulation page, roughly 20 EU member states had already joined large-scale wallet pilots before the mandatory rollout clock even started, a sign this isn't a cold start for most of the bloc. Four consortiums (covering use cases like payments, travel, education credentials, and digital driving licenses) have been running cross-border tests since 2023, which is exactly the kind of groundwork that's supposed to make the end-of-2026 deadline realistic rather than aspirational.

Here's the question most people actually have: does eIDAS 2.0 change how e-signatures work? Short answer: no, not the legal mechanics. Longer answer: it changes how you prove identity behind the signature, and that's arguably the more useful part.

The three tiers are unchanged: SES, AES, and QES carry the exact same definitions and legal weight they did before. For the full breakdown of what separates a QES from AES and SES, and when QES is actually required, see our qualified electronic signature guide.

What's emerging, shaped by the Implementing Acts and ETSI standards rolling out through 2025–2026, is wallet-bound QES: identity-proofing for a qualified certificate increasingly relying on an EUDI Wallet credential instead of a one-off video-identification session or a physical ID scan. Practically, that could mean a signer authenticates 1x through their wallet and reuses that verified identity across multiple signing sessions with different vendors, rather than re-proving who they are every single time. This is a genuine improvement over the old flow, though it's still maturing. Treat it as an emerging practice enabled by eIDAS 2.0, not yet a universal, drop-in replacement for existing QES identity-proofing methods.

By end of 2027, wallet acceptance stops being optional for a specific, named list of sectors: banks and other financial institutions, payment and e-money providers, insurers, healthcare providers, and very large online platforms with more than 45 million monthly EU users. That 45-million threshold works out to roughly 10% of the EU's total population using a single service before wallet acceptance becomes mandatory for it, a high bar, but not an impossibly high one for a handful of major tech companies. If your business fits one of those categories, the wallet isn't a nice-to-have integration you can defer indefinitely. It's a legal acceptance obligation with a real date attached.

Everybody else (retailers, agencies, most SaaS companies, professional services firms) isn't currently named in the mandatory-acceptance list. That doesn't mean ignore it. Two things are worth planning for regardless: your customers or partners may start presenting wallet credentials voluntarily well before any deadline forces the issue, and B2B contracts increasingly ask vendors to confirm eIDAS 2.0 readiness as part of procurement due diligence, the same way GDPR compliance became a standard vendor-questionnaire line item a few years back.

You don't need a six-figure compliance project to get ahead of this. Five practical steps cover most of the ground.

1. 1
   Scope yourself honestly. Are you in a regulated sector, or approaching the VLOP user threshold? If not, your deadline pressure is lower, but not zero. See the point above about voluntary wallet presentation and procurement questionnaires.
2. 2
   Inventory your identity touchpoints. Where do you currently do identity proofing, KYC, strong customer authentication, or signature verification, and which of those flows genuinely need high assurance versus which are low-risk?
3. 3
   Watch the 2026–2027 technical roadmap. EUDI Wallets will likely authenticate through OIDC-like flows, and Qualified Trust Service Providers will expose APIs for AES/QES issuance tied to wallet credentials. You don't need to build this yourself, but you do need a signing vendor whose roadmap covers it.
4. 4
   Paperwork update: terms of service, privacy notices, and contract templates should recognize a wallet-based identity credential and a QES alongside your existing signature methods, not as a hypothetical future case.
5. 5
   Pilot before you're forced to. Test wallet acceptance in a non-production environment well before any deadline, the same way smart teams piloted GDPR data-subject request flows in 2017 instead of scrambling in May 2018.

None of this requires ripping out your current signing stack. It requires picking a vendor that's already tracking the Implementing Acts, so the wallet-acceptance work lands on their roadmap instead of yours.

Chaindoc is a document platform first: create a contract, get it signed, get paid, all without switching tools. Compliance is the trust layer underneath that workflow, not a separate product bolted on top.

Today, Chaindoc's signing workflow already supports SES and AES-level signatures with identity verification before document access, a cryptographic document hash generated at the moment of signing, and a tamper-proof, blockchain-anchored audit trail, the same non-repudiation mechanics our digital signature compliance guide covers for eIDAS, GDPR, and NIST side by side. Every signed document can be checked instantly through free online PDF verification, so a partner never has to take your word for it that a contract wasn't altered after signing.

As Implementing Acts finalize wallet-credential standards through 2026, that same audit-trail architecture is exactly what a wallet-bound QES needs underneath it: verified identity, an immutable hash, and a timestamped chain of custody. You don't need to rebuild your signing process from scratch when the wallet mandate lands. You need a vendor that already treats legal enforceability as a first-class feature instead of an afterthought. Chaindoc's Free plan costs €0/month, permanently, with no credit card required, so testing an eIDAS-ready workflow before 2027 doesn't need a procurement cycle of its own. Compare paid tiers on the Chaindoc pricing page once you're ready to scale past the free plan.

eIDAS 2.0 isn't a new signature law. It's a new identity law that sits next to the signature rules you already follow. SES, AES, and QES mean exactly what they meant under eIDAS 1.0. What's changing is who has to accept a government-issued digital wallet, and by when: every member state offers one by end of 2026, and named regulated sectors plus very large platforms must accept it by end of 2027.

If you're not in a regulated sector, you have time, but "time" isn't the same as "ignore it." Start with the readiness checklist above, keep an eye on the Implementing Acts as they finalize through 2026, and pick a signing vendor whose compliance roadmap already assumes wallet-bound credentials are coming. That's a smaller lift than most teams expect, and a much smaller one than scrambling in late 2027 would be.

For the fuller compliance picture across eIDAS, GDPR, and NIST together, our digital signature compliance guide is the natural next read.