eur-lex.europa.eu
Referenced sections
- Binding QEAA and public-sector authentic-source attestation rules; Articles 6 to 9 apply from 19 August 2026.
By Sorena AIPublished Updated
eIDAS
EU eIDAS
Understand eIDAS , qualified signatures and seals, time stamps, trusted lists, QWACs, QTSPs and EU Digital Identity Wallet relying-party readiness.
- Providers
- Web certs
- Attributes
- Identity
Understand EU eIDAS
Use this hub to apply Regulation (EU) No 910/2014 as amended by Regulation (EU) 2024/1183. It separates notified electronic identification, and qualified status, and European Digital Identity Wallet roles instead of treating every digital identity or e-signature workflow as the same eIDAS question.
Start with the actor and regulated service. Article 2 covers Member State-notified eID schemes, EUDI Wallets provided by or on behalf of Member States, and trust service providers established in the Union. It excludes used exclusively in closed systems created by national law or agreements among a defined set of participants. It also leaves national or Union rules on contract formation, validity, legal obligations, and procedural form requirements untouched.
Follow the grouped guides in order: decide scope and role, classify the service and legal effect, verify qualified status, map implementation evidence, and only then assign deadlines and monitoring.
Quick scan
Trust services
Start with the regulated service: signature, seal, time stamp, registered delivery, website authentication certificate, electronic attestation of attributes, archiving, ledger, or validation.
Provider checks
Use qualified status, certificate type, revocation and validity information, trusted lists, and supervisory-body context before relying on a certificate or service.
Wallet context
For use cases, distinguish wallet providers, PID providers, attestation providers, relying parties, service providers, and technical relying-party instances.
EU eIDAS questions this hub helps resolve
- 1
Scope and role
Identify the notified eID scheme, role, or exact trust service. Record whether the organisation provides the service, seeks qualified status, issues or validates an artefact, or relies on the result.
- 2
Legal effect and qualified status
Separate electronic, advanced, and qualified signatures or seals, then prove any qualified claim through the specific service, certificate, creation device, QTSP status, trusted list, and validation evidence.
- 3
Implementation and dates
The 2024 amendment entered into force on 20 May 2024. Member States must provide at least one wallet by the end of 2026, and the harmonised relying-party registration rules apply from 24 December 2026. Keep those legal dates separate from ARF versions, pilot milestones, and acceptance duties that depend on the actor and trigger.
Key eIDAS dates for trust services and wallets
Track the original trust-services framework, the 20 May 2024 entry into force of the European Digital Identity Framework, implementing acts, the end-of-2026 wallet rollout, and later transition items. A timeline date does not by itself establish that a particular provider must accept a wallet; Article 5f ties private-sector acceptance to strong-authentication triggers, excludes microenterprises and small enterprises, and makes wallet use voluntary for the user.
Loading timeline...
Choose the next eIDAS decision
New to eIDAS? Start with scope, the regulated service, and your role. If those decisions are already documented, jump to legal effect, qualified status, wallet implementation, evidence, dates, or a focused comparison.
Start here: scope, roles, and the amended framework
Decide whether the facts concern notified electronic identification, an eIDAS trust service, or the ecosystem, and distinguish the original 2014 framework from the 2024 amendments.
EUDI Wallet, identity, and attribute flows
Map wallet ecosystem roles, relying-party registration and data requests, person identification data, attestations, architecture, certification dependencies, and onboarding evidence.
- EUDI Wallet readiness for service providers under eIDAS
- EUDI Wallet Relying Party Registration Under eIDAS
- EUDI Wallet Technical Architecture Guide under eIDAS
- EUDI Wallet Relying Party Onboarding Workflow under eIDAS
- Electronic Attestations of Attributes under EU eIDAS: EAA, QEAA, issuers, wallets, and validation
Trust services, signatures, and legal effect
Select the service and assurance level, then connect signatures, certificates, website authentication, remote signing, and qualified-service claims to their legal and technical evidence.
- eIDAS electronic signatures: SES, AES, QES legal effect and evidence
- eIDAS signature legal effect selector: SES, AES, AES-QC, or QES
- eIDAS Qualified Trust Services: QTSP Selection
- eIDAS Certificates and Authentication: qualified certificates, QWACs, and validation checks
- QWACs under eIDAS: website authentication certificates
- eIDAS remote signature and cloud HSM controls for QTSPs
Provider status, supervision, and validation
Verify the exact qualified service, supervisory decision, conformity evidence, trusted-list status, certificate path, revocation information, and retained validation result.
- EU eIDAS QTSP authorization and supervision guide
- EU eIDAS QTSP Due Diligence Workflow for Trusted Lists, Certificates, and Evidence
- eIDAS trusted list validation: LOTL, QTSP status, and evidence
- eIDAS QES validation checks for relying parties
- EU eIDAS Requirements for Trust Services, Signatures, Seals, Wallets, and Evidence
Implementation, evidence, dates, and enforcement
Translate the classified role and service into owned controls, evidence packs, fixed or dependent dates, reassessment triggers, supervisory consequences, and national penalty checks.
- EU eIDAS checklist for signatures, trust services, and wallets
- eIDAS checklist and evidence pack for trust services, signatures, and EUDI Wallet relying parties
- eIDAS compliance guide for trust services, QTSPs, signatures, and EUDI Wallet relying parties
- eIDAS 2 deadlines and compliance calendar for EUDI Wallet and trust services
- eIDAS penalties and fines for trust service providers
Compare adjacent rules or answer a focused question
Separate eIDAS from privacy, cybersecurity, ETSI operational standards, and US electronic-signature law, or use the FAQ when you already know the question to resolve.
- eIDAS vs GDPR for identity data: wallet, trust-service, and privacy obligations
- eIDAS vs NIS2 for trust service providers: QTSP and cybersecurity obligations
- eIDAS vs ETSI EN 319 401: legal supervision and TSP policy requirements
- eIDAS vs ESIGN and UETA: EU qualified signatures vs U.S. e-signature laws
- EU eIDAS FAQ: signatures, QTSPs, trusted lists, QWACs, wallets, and validation
Sources
eur-lex.europa.eu
Referenced sections
- Binding validation reference standards in force since 20 October 2025 for qualified signatures and seals and advanced signatures and seals based on qualified certificates.
eur-lex.europa.eu
Referenced sections
- Binding harmonised rules, applicable from 24 December 2026, for national relying-party registers, registration information, certificates, suspension, cancellation, and registrar recordkeeping.
digital-strategy.ec.europa.eu
Referenced sections
- Supports the hub's practical framing of eIDAS as a cross-border digital identity and trust-services framework, including signatures, seals, time stamping, registered delivery, website authentication, and qualified trust services.
"The eIDAS regulation facilitates secure cross-border transactions"
ec.europa.eu
Referenced sections
- Supports visitor navigation to eSignature resources, DSS, validation tooling, the eIDAS Dashboard, trusted-list browser, and qualified trust service provider lookup.
"creation and verification of electronic signatures"
ec.europa.eu
Referenced sections
- Supports relying-party and service-provider navigation: requesting wallet data, PID and EAA validation, registration, obligations, certification context, and wallet ecosystem trust lists.
"request data from wallet users"
eur-lex.europa.eu
Referenced sections
- Primary amending regulation for the European Digital Identity Framework and EU Digital Identity Wallet context used by the wallet and relying-party readiness sections.
"establishing the European Digital Identity Framework"
eur-lex.europa.eu
Referenced sections
- Primary eIDAS legal text for electronic identification, trust services, electronic signatures, electronic seals, time stamps, registered delivery, website authentication certificates, trusted lists, and qualified provider concepts.
"on electronic identification and trust services for electronic transactions"
Next steps
Plan trust-service and wallet implementation
This hub is the shared entry point for eIDAS role mapping, trust-service selection, QTSP and certificate evidence, wallet relying-party readiness, and follow-up research tied to cited sources.
- Start with the role: trust service provider, , relying party, wallet service provider, issuer, verifier, or internal product owner.
- Use Assessment Autopilot to request certificate, trusted-list, QTSP, validation, incident, privacy, and wallet-registration evidence from the right owner.
- Use Research Copilot for cited questions about qualified signatures, seals, time stamps, QWACs, electronic attestations of attributes, archiving, ledgers, and wallet relying-party obligations.
- Keep source interpretation, product requirements, security architecture, vendor evidence, and approval history attached to the same eIDAS work item.
- Open Assessment Autopilot
Turn eIDAS trust-service, certificate, QTSP, wallet, and relying-party readiness questions into owned tasks and review checkpoints.
- Open Research Copilot
Answer eIDAS scope, trust-service, wallet, QWAC, trusted-list, and interpretation questions with cited outputs from official sources.
Align sourced eIDAS and milestones across product, security, legal, procurement, and operations teams.
- Talk through implementation
Review the trust-service, wallet, relying-party, certificate, and evidence questions that are blocking implementation.