Join our Newsletter — 33% off our NHI Course
Home› Guides› eIDAS 2.0 and the European Digital Identity Framework…
Guide Regulations & Frameworks

eIDAS 2.0 and the European Digital Identity Framework Guide: Wallets, Trust Services and Deadlines

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 13 min read
On this page

Regulation (EU) 2024/1183, usually called eIDAS 2.0, turns digital identity wallets from a pilot into a legal obligation: every EU Member State must offer one, and many public and private services must accept it. It amends the original eIDAS Regulation (EU) No 910/2014, adds the European Digital Identity Wallet (EUDI Wallet), registers the organisations that rely on it, and creates new qualified trust services such as electronic attestations of attributes, electronic archiving and electronic ledgers. This guide sets out who is covered, the obligations that matter to relying parties and trust service providers, the deadlines as they stand, how enforcement works, and what the framework means for machine and agent identities. It is written for identity, security and compliance teams at banks, platforms, utilities and public bodies. Status checked on 27 October 2026 against EUR-Lex and the Commission's EUDI Wallet pages; implementing acts are still being amended, so confirm current text before acting.

Key takeaways

  • Wallets are due by the end of 2026. Article 5a(1) gives each Member State 24 months from the entry into force of the core implementing acts to provide at least one wallet. Those acts entered into force on 24 December 2024, which puts the deadline at 24 December 2026.
  • Acceptance is mandatory for many relying parties. Public sector bodies that accept electronic identification must also accept EUDI Wallets. Private relying parties in listed sectors that are required by law or contract to use strong user authentication, and very large online platforms, must accept them when a user asks, with the private sector deadline falling 36 months after the implementing acts, around the end of 2027.
  • Relying parties must register. Article 5b requires registration in the Member State of establishment. Registered parties receive access certificates and registration certificates, and wallets check that a relying party asks for no more data than it registered.
  • Trust services grow and fines are harmonised. New qualified services cover electronic attestations of attributes, archiving, ledgers and remote signature devices, and Article 16 sets minimum maximum fines of EUR 5 000 000 or 1% of worldwide turnover for trust service providers.
  • The technical stack is fixed by implementing acts and the ARF. SD-JWT VC and ISO/IEC 18013-5 mdoc formats, OpenID4VP and OpenID4VCI protocols, and the HAIP profile are what relying parties will actually integrate.

Scope: who and what is covered

Regulation (EU) 2024/1183 was adopted on 11 April 2024, published in the Official Journal on 30 April 2024 and entered into force on 20 May 2024. It does not replace eIDAS; it amends Regulation (EU) No 910/2014 so the two are read together as one consolidated text.

PartyRole under the frameworkMain articles
Member StatesProvide at least one EUDI Wallet, notify wallets and schemes, superviseArt. 5a, 5c, 5d
Wallet providersBuild and operate certified wallet solutions, free of charge for natural personsArt. 5a, 5c, 5e
PID providersIssue Person Identification Data to wallets at assurance level highArt. 5a; CIR 2024/2977
Attestation providersIssue qualified, public sector or non-qualified electronic attestations of attributesArt. 3(16)(g); CIR 2025/1569
Wallet-relying partiesRegister, then request and verify wallet dataArt. 5b, 5f; CIR 2025/848
Very large online platformsAccept and facilitate wallets for user authentication on requestArt. 5f(3)
Qualified and non-qualified trust service providersSignatures, seals, time stamps, registered delivery, website authentication, attestations, archiving, ledgersArt. 3(16), 19a, 20, 21, 24

The amended definition of trust service now includes the issuance of electronic attestations of attributes, electronic archiving and the recording of data in an electronic ledger, and the Regulation defines remote qualified signature creation devices managed by a qualified trust service provider on behalf of a signatory. For the trust service side in depth see the eIDAS Qualified Trust Services Guide.

Key obligations

For Member States and wallet providers

  • Provision: at least one wallet per Member State within 24 months of the implementing acts referred to in Articles 5a(23) and 5c(6) (Article 5a(1)).
  • Free of charge: issuance, use and revocation of wallets must be free of charge to all natural persons (Article 5a(13)).
  • Assurance: onboarding to the wallet at assurance level high, or substantial combined with additional remote onboarding procedures, with reference standards set by implementing act (Article 5a(24); remote onboarding in CIR 2026/798).
  • Certification and breach response: wallets are certified and listed (Article 5d, CIR 2024/2981), and can be suspended or withdrawn after a security breach (Article 5e, CIR 2025/847).

For relying parties

  • Register first: a relying party that intends to rely on wallets registers in the Member State where it is established (Article 5b(1)), under the procedures in CIR 2025/848, which was amended by CIR 2026/1730 (in force 11 August 2026).
  • Declare intended uses: under the ARF trust model, each registration lists intended uses and the attributes each needs. Wallets authenticate the relying party instance with its access certificate and check the registration certificate to detect over-asking.
  • Accept when obliged: public sector bodies (Article 5f(1)); private relying parties in transport, energy, banking and financial services, social security, health, drinking water, postal services, digital infrastructure, education or telecommunications that must use strong user authentication by law or contract (Article 5f(2)); very large online platforms as defined in Article 33 of the Digital Services Act that require user authentication (Article 5f(3)).
  • Voluntary for the user: the private sector and platform obligations apply only upon the voluntary request of the user, and platforms must limit requests to the minimum data needed for the service.
  • Exemption: microenterprises and small enterprises are excluded from the Article 5f(2) obligation.

For trust service providers

  • Security and breach notification: Articles 19a (non-qualified) and 24 (qualified) set risk management and notification duties, with detailed rules for non-qualified providers in CIR 2025/2160 and for qualified providers in CIR 2025/2530.
  • Identity verification: qualified certificates and qualified attestations require verified identity and attributes under the reference standards in CIR 2025/1566.
  • Website authentication: reference standards for qualified certificates for website authentication are in CIR 2025/2527.

Timeline and current status

Dates below are taken from EUR-Lex and the Commission's EUDI Wallet pages. Deadlines expressed as "months after implementing acts" have been calculated from the in-force date of the first batch of implementing acts; national authorities may communicate them slightly differently.

DateEventStatus on 27 October 2026
11 April 2024Regulation (EU) 2024/1183 adoptedDone
30 April 2024Published in the Official JournalDone
20 May 2024Entry into forceIn force
21 November 2024Deadline in Article 5a(23) for the reference standards implementing actsAdopted 28 November 2024 (CIRs 2024/2977, 2979, 2980, 2981, 2982)
24 December 2024First batch of wallet implementing acts in forceIn force; several amended in 2026 by CIRs 2026/1730, 2026/1731 and 2026/1735
May to December 2025Further implementing acts: registration of relying parties (2025/848), security breaches (2025/847), trust service standards (2025/1566 to 1572, 2025/1929, 1942 to 1946, 2025/2160, 2162, 2527, 2530 to 2532)Adopted
7 April 2026CIR 2026/798 on remote onboarding to the walletAdopted
21 July 2026ARF 3.0.0 aligned with the amending implementing actsPublished (technical guidance, not law)
24 December 2026Member States provide at least one wallet; public sector acceptanceUpcoming; the Commission describes this as "by the end of 2026"
About 24 December 2027Private relying parties in Article 5f(2) sectors must accept wallets on requestUpcoming
24 months after deploymentCommission assesses demand, availability and usability (Article 5f(5))Future

Proposals to watch: the Commission's Digital Omnibus package of 19 November 2025 includes proposed amendments to Regulation (EU) No 910/2014, and a separate European Business Wallet proposal was presented in November 2025. Both were proposals still in the legislative process when this page was checked; neither changes the obligations above unless and until adopted. Re-check EUR-Lex before relying on any date.

Enforcement and penalties

  • Trust service providers: Article 16(2) requires Member States to provide administrative fines with a maximum of at least EUR 5 000 000 where the provider is a natural person, and for legal persons at least EUR 5 000 000 or 1% of total worldwide annual turnover in the preceding financial year, whichever is higher. This covers qualified and non-qualified providers.
  • Supervision: national supervisory bodies oversee trust service providers and wallet providers; qualified providers are audited by accredited conformity assessment bodies (CIR 2025/2162).
  • Wallets: a compromised wallet solution or its certification can be suspended or withdrawn (Article 5e).
  • Relying parties: the Regulation text we reviewed does not set fixed fine amounts for relying parties that fail to accept wallets; consequences depend on national implementing law, sector regulators and the registration regime. Check the law in each Member State where you operate.
  • Data protection: processing of wallet data by relying parties remains subject to the GDPR, so over-collection is also a data protection issue. See the GDPR Compliance Guide for Security Teams.

What it means for AI agents and non-human identities

The EUDI Wallet is built for natural and legal persons, not for software agents, but the framework still shapes machine identity in four ways.

  • Relying party systems are machines with credentials: each relying party instance holds an access certificate and signs presentation requests with a private key. Those keys are high-value non-human credentials and belong in an HSM with rotation and inventory. See the Machine Identity, PKI and Certificate Lifecycle Guide.
  • Electronic seals identify organisations, often in automated processes: qualified electronic seals belong to legal persons and are routinely applied by servers to invoices, statements and API payloads. Remote qualified seal creation devices are now a defined qualified trust service (CIR 2025/1567).
  • Attestations of attributes can describe more than people: qualified electronic attestations of attributes give a legal basis for signed claims about a business, a mandate or a role. Expect them in agent delegation designs, where an agent presents proof that a person or company authorised it, rather than impersonating the person.
  • Agents should not hold citizens' wallets: PID is device bound and the wallet's holder binding exists to stop someone else presenting it. Agentic flows should use a separate, scoped delegation credential or an OAuth-based authorisation, never a copied PID. See the Delegation Chains and Attenuated Authority for AI Agents.

Compliance steps

  1. Classify your obligation: determine whether you are a public sector body, a private relying party in an Article 5f(2) sector with a legal or contractual strong authentication duty, a very large online platform, or outside scope, and whether the micro or small enterprise exemption applies.
  2. Map use cases to attributes: list each journey (onboarding, login, age check, signature) and the minimum attributes each needs. This becomes your registration and your DCQL queries.
  3. Register in your Member State under CIR 2025/848 as amended, and obtain access and registration certificates for each relying party instance.
  4. Choose an integration path: build to the ARF and HAIP profile (OpenID4VP for remote presentation, ISO/IEC 18013-5 for proximity) or use a certified verifier service. See the OpenID for Verifiable Presentations Guide and the Relying Party Integration with Digital Identity Wallets Guide.
  5. Pilot with national test wallets in shadow mode alongside existing KYC or login, comparing outcomes and drop-off. Keep the existing route available as rollback.
  6. Update risk and data protection documents: DPIA, records of processing, retention, and your strong customer authentication mapping. See the PSD2/PSD3 Strong Customer Authentication Guide for banking.
  7. Go live before your deadline and monitor wallet acceptance, failures and fraud signals.

Small organisations often meet obligations through an identity provider or verifier service; large banks and platforms typically need their own registration, multiple relying party instances and cross-border testing.

Detection and measurement

  • Wallet acceptance coverage: share of in-scope journeys that offer the wallet option. Target 100% by your deadline.
  • Attribute over-asking: attributes requested beyond those registered for the intended use. Target zero; wallets may warn users or block.
  • Verification failure rate by Member State, wallet and failure reason (untrusted issuer, revoked, expired, binding failure).
  • Certificate health: days to expiry of access and registration certificates, and request-signing key rotation age.
  • Fraud and fallback rate: wallet journeys abandoned to legacy routes, and fraud cases per journey type.

Framework mapping

FrameworkReferenceRelevance to eIDAS 2.0
NIST CSF 2.0GV.OC-03Legal and regulatory requirements, including identity obligations, are understood and managed
NIST CSF 2.0PR.AA-02Identities are proofed and bound to credentials
NIST SP 800-53 Rev. 5IA-8, IA-12Authentication of non-organisational users; identity proofing
NIST SP 800-53 Rev. 5SC-12Management of relying party and trust service keys
ISO/IEC 27001:2022 Annex A5.31, 5.34Legal, statutory, regulatory and contractual requirements; privacy and protection of PII

Practitioner checklist

  • Record whether Article 5f(1), 5f(2) or 5f(3) applies to each legal entity, and whether the micro or small enterprise exemption applies.
  • Diary 24 December 2026 (wallets and public sector) and about 24 December 2027 (private relying parties), and re-check status quarterly.
  • Register as a wallet-relying party in each Member State of establishment and track certificate expiry.
  • Document intended uses and minimum attributes for every journey before writing any request.
  • Protect request-signing and access certificate keys in an HSM with rotation and inventory.
  • Integrate to the ARF and HAIP stack and pass conformance testing.
  • Keep the wallet optional for the user where the Regulation makes acceptance voluntary on request.
  • Update DPIA and retention so raw presentations are not stored by default.
  • Watch the Digital Omnibus and European Business Wallet negotiations for changes.

Standards and references

Related NHI Mgmt Group resources: Digital Identity Wallets Guide · EUDI Wallet Architecture and Reference Framework Guide · eIDAS Qualified Trust Services Guide · SD-JWT and SD-JWT VC Guide · Identity Security Regulatory Map. This guide summarises Regulation (EU) 2024/1183 and its implementing acts as of 27 October 2026 and is not legal advice.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.