eIDAS 2.0 Explained: The EU Digital Identity Wallet and What It Changes for E-Signing

The original eIDAS regulation, Regulation (EU) No 910/2014, did two big things. It created a common EU framework for electronic identification (so that an eID recognised in one member state could be recognised in others) and it defined a layered set of trust services, including the three tiers of electronic signature that practitioners still use today: the simple electronic signature (SES), the advanced electronic signature (AES), and the qualified electronic signature (QES). That structure has not been thrown away. eIDAS 2.0 builds on it.

The eIDAS regulation update, Regulation (EU) 2024/1183, amends the 2014 text rather than replacing it. The headline addition is the European Digital Identity Wallet, a personal identity and credential app that member states must make available. Where the original eIDAS left identity largely in the hands of national schemes that were optional to notify and unevenly adopted, eIDAS 2.0 makes a wallet a baseline expectation across the Union and obliges certain relying parties to accept it.

Practically, this means the legal scaffolding for electronic signatures, seals, timestamps and qualified trust services carries forward, while a new, user-controlled identity layer is added on top. The signature tiers (SES, AES, QES) and their legal meaning are unchanged in substance; what changes is how a person proves who they are and how they may carry the credentials needed to sign.

The EU Digital Identity Wallet (often abbreviated EUDI Wallet) is the practical heart of eidas 2. The idea is a single, government-recognised app on a person's phone that can hold a verified identity plus other digital attributes and credentials, then present exactly the information a service needs, no more. A user might confirm they are over 18, prove a professional qualification, or authenticate to a public service, while keeping unrelated data private. The design intent is user control and data minimisation, not a central database of everyone's activity.

For signing, the wallet is significant because it is meant to let citizens create qualified electronic signatures. Today, obtaining a QES often involves a separate qualified trust service provider and an identity-proofing step. The wallet is designed to streamline that: a verified identity already held in the wallet can support the issuance and use of qualified signing credentials, lowering friction for individuals who need the highest legal tier.

It helps to keep two things separate. The wallet is an identity and credential container that member states issue and govern. Trust services such as qualified signature creation remain the domain of qualified trust service providers operating under supervision. The regulation connects them, but they are distinct roles. A platform like DokDesk is neither a wallet issuer nor a qualified trust service provider; it is the contract workflow where signatures created through eIDAS-conformant methods are captured into a court-ready evidence base.

The legal effect of signatures under eIDAS is set out in the regulation and is not weakened by the update. Article 25 establishes that a qualified electronic signature has the equivalent legal effect of a handwritten signature, and that an electronic signature cannot be denied legal effect simply because it is electronic. Article 26 defines the four requirements an advanced electronic signature must meet: it is uniquely linked to the signatory, capable of identifying the signatory, created using signature-creation data the signatory can use under their sole control, and linked to the signed data so any later change is detectable.

Within that framework, the three tiers continue to map to risk. A simple electronic signature (SES) suits low-risk, high-volume agreements. An advanced electronic signature (AES) adds the Article 26 guarantees of identity linkage and tamper-evidence, which is why it is common for commercial contracts. A qualified electronic signature (QES) is an AES backed by a qualified certificate and a qualified signature-creation device, and it carries the Article 25 equivalence to a wet-ink signature. eIDAS 2.0 does not collapse these tiers; it gives more people an easier route to the higher ones via the wallet.

For the Baltics, this is a natural fit. Estonia, Latvia and Lithuania already have mature national eID ecosystems and citizens accustomed to strong electronic identity for signing and authentication. The wallet is intended to interoperate across borders, so a credential issued in one member state should be usable when dealing with a service in another, which matters for cross-border trade. This is general guidance; the legal weight required for any specific document is a matter for your own legal advisers.

eIDAS 2.0 entered into force in 2024, but a regulation entering into force is not the same as wallets being in every pocket. The framework sets obligations for member states to make a wallet available to citizens and residents, supported by a body of implementing and technical specifications that define how wallets, issuers and relying parties interoperate. This detailed layer is being developed and refined, which is why precise availability dates differ by country and continue to move.

The honest summary is that this is a phased, multi-year rollout rather than a single switch-on. Member states are working toward making national wallets available, large-scale pilots have tested real-world use cases, and certain categories of relying parties are expected over time to accept the wallet where a user chooses to present it. Rather than fixate on a specific calendar date, businesses should track their own national implementation, because that is where timing and practical detail will be confirmed.

The strategic takeaway is direction of travel, not a deadline. The EU is moving toward a widely available, state-backed identity wallet that supports cross-border identification and easier access to qualified signing. Treating it as an inevitability to prepare for, rather than a date to wait on, is the more useful posture for any organisation that signs documents at scale.

The first preparation is conceptual: keep matching signature tiers to transaction risk. eIDAS 2.0 does not require everything to be qualified. Most routine agreements are well served by SES or AES, and the wallet's main effect on signing is to make stronger identity assurance more accessible when a document genuinely warrants it. A clear internal policy on which tier applies to which document type remains the single most valuable thing you can put in place, and it is worth confirming that policy with your legal advisers.

The second is evidence. Whatever signature method is used, the durable question in a dispute is what you can prove: who signed, when, on which exact version, and that the document has not changed since. A contract workflow that locks negotiation onto one live version and assembles a complete, tamper-evident evidence base is what makes a signature defensible later. That value holds today under the existing eIDAS tiers and carries forward as wallet-based signing becomes more common.

The third is to choose tooling that is built for where the regulation is heading. DokDesk supports SES and AES signing today using national eIDs such as Smart-ID and Mobile-ID, with data kept in the EU under GDPR, and it is architecture-ready for QES, meaning it is designed so that qualified trust providers and devices can plug in. To be precise: DokDesk is not itself a qualified trust service provider and does not issue QES. Picking a workflow with that design intent now means you are positioned for the wallet era without betting on a single rollout date.