eIDAS is the EU framework for cross-border electronic identification, European Digital Identity Wallets, and trust services used in electronic transactions.
Use this page to separate eIDAS-covered services from adjacent login, certificate, document, and identity workflows that may be governed mainly by contract, sector rules, GDPR, or national law.
Structured answer sets in this page tree.
Cited legal and guidance references.
The EU eIDAS framework covers two linked areas: electronic identification used for access to online or offline services, and trust services that give legal and technical reliability to electronic transactions. The 2024 European Digital Identity Framework amendments add the European Digital Identity Wallet, electronic attestations of attributes, electronic archiving, electronic ledgers, and updated trust-service rules. A useful scope review starts with the service being offered or relied on, not with the technology label used by a supplier.
Article 1 sets the basic perimeter: eIDAS covers recognition of electronic identification means under notified Member State schemes, provision and recognition of European Digital Identity Wallets, rules for trust services, and the legal framework for specified electronic transaction services.
Article 2 narrows that perimeter. The Regulation applies to electronic identification schemes notified by a Member State, to European Digital Identity Wallets provided by a Member State, and to trust service providers established in the Union. Trust services used exclusively inside closed systems created by national law or agreements between a defined set of participants are outside eIDAS trust-service scope.
Electronic identification under eIDAS is not every login method. It is the use of person identification data in electronic form that uniquely represents a natural or legal person, or a representative, and is used for authentication. The cross-border recognition rules are tied to electronic identification schemes notified by Member States.
Relying parties are the organisations that rely on electronic identification, EUDI Wallets, other electronic identification means, or trust services. A normal account login, password reset, or customer identity check should be marked as eIDAS-relevant only when it uses a notified eID scheme, a wallet, or a regulated trust service.
eIDAS trust services are electronic services normally provided for remuneration and listed in Article 3. The list includes certificates, validation, creation and preservation services for signatures and seals, remote signature or seal creation-device management, time stamps, registered delivery, electronic archiving, electronic attestations of attributes, and electronic ledgers.
The qualified status of a trust service is not a marketing description. A qualified trust service must meet the applicable eIDAS requirements, and a qualified trust service provider must be granted qualified status by the supervisory body. For qualified services, trusted-list status is central to validation and evidence.
Trusted lists are where EU Member States publish information about supervised qualified trust service providers and their qualified trust services. They are essential for checking whether a provider or service had qualified status at the time relevant to a signature, seal, certificate, delivery service, attestation, or other trust-service event.
The European Commission publishes a central List Of Trusted Lists with links to the Member State trusted lists. Systems that validate qualified signatures, seals, website certificates, or other qualified trust services should treat trusted-list retrieval, signature or seal verification, service status, service history, and certificate validity status as evidence, not as a one-time procurement check.
The EUDI Wallet is now part of the eIDAS framework. The Regulation defines it as an electronic identification means that lets the user securely store, manage, and validate person identification data and electronic attestations of attributes for presentation to relying parties and other wallet users, and to sign or seal with qualified electronic signatures or seals.
Attribute attestations are also within scope. A qualified electronic attestation of attributes is issued by a qualified trust service provider and must meet Annex V. Attestations issued by or on behalf of a public sector body responsible for an authentic source have a separate path and must meet Article 45f and Annex VII requirements. Implementations should therefore track the attestation type, issuer role, authentic source, revocation status, wallet interface, and whether the presentation request is limited to attributes needed for the use case.
Use this checklist when a product, procurement, legal, identity, PKI, or security team needs to decide whether a workflow belongs on the eIDAS register. The aim is to classify the actual service and preserve the validation material needed later.
Avoid broad labels such as digital identity, e-signing, certificate, wallet, or secure delivery without naming the eIDAS category and the provider role.
No. eIDAS defines electronic signatures and gives legal effects to electronic, advanced, and qualified electronic signatures, but a signature is qualified only when it is an advanced electronic signature created by a qualified electronic signature creation device and based on a qualified certificate for electronic signatures.
Not as ordinary TLS certificates. eIDAS covers certificates for website authentication and qualified certificates for website authentication; the qualified category must be issued by a qualified trust service provider and meet Annex IV requirements.
Check the provider, service type, qualified status, and status history in the relevant Member State trusted list, using the Commission List Of Trusted Lists as the EU entry point, and keep the validation evidence with the transaction record.
Use the categories on this page to classify eID schemes, wallet integrations, trust services, QWACs, trusted-list checks, and attribute-attestation flows before assigning legal, product, PKI, and security work.
Ask source-linked questions about eIDAS scope, trust-service categories, wallet integrations, and validation evidence using the cited sources on this page.
Review whether a signature, seal, delivery, certificate, wallet, or attribute-attestation workflow is covered by eIDAS and what evidence should be kept.
"electronic attestations of attributes"
"General Policy Requirements"
"qualified status and the status history"
"Trusted Lists"
"Architecture and Reference Framework"
"European Digital Identity Framework"
"certificate for website authentication"