We use privacy-by-default, cookieless analytics.

Optional analytics cookies are used only if you accept them.

Read our Terms of Use and Privacy Policy.

FAQEU

EU eIDAS Regulation Attribute Attestations

Electronic attestations of attributes are eIDAS trust-service objects that let a user prove specific attributes, such as age, address, qualifications, mandates, permits, or company data, without turning every attribute proof into electronic identification.

This FAQ explains the difference between EAA, QEAA, and public-sector authentic-source attestations, plus the wallet, issuer, legal-effect, revocation, and relying-party checks that matter.

Back to main artifactReview sources
Author
Sorena AI
Published
May 9, 2026
Updated
Jul 25, 2026
3 sections8 primary sources
Overview

Under the amended eIDAS Regulation, an is an electronic attestation that allows attributes of a natural person, legal person, or object to be authenticated. The regulation gives special treatment to qualified electronic attestations of attributes and to attestations issued by, or on behalf of, a public sector body responsible for an . A relying party should check the attestation category, issuer authority, wallet presentation, validity status, and whether the requested attributes are necessary for the service.

Search this module

Find a question or answer quickly

3 of 3 questions
Question 1

What is an electronic attestation of attributes under eIDAS?

An is a regulated way to prove facts about a natural person, legal person, or object through the eIDAS trust-service framework. eIDAS covers electronic attestation of attributes alongside signatures, seals, timestamps, electronic documents, registered delivery, website authentication, archiving, and electronic ledgers.

The attestation type controls the legal and validation checks. A non-qualified EAA can still have legal effect and evidentiary value, but a (QEAA) must meet Annex V requirements and be issued by a qualified trust service provider. A separate category covers attestations issued by, or on behalf of, a public sector body responsible for an ; those must meet Annex VII and the additional Article 45f requirements.

Commission Implementing Regulation (EU) 2025/1569 adds the operational rules for QEAAs and public-sector authentic-source attestations. Its issuance and revocation provisions have applied since 19 August 2025. Articles 6 to 9, which cover the public-sector provider list, attribute and scheme catalogues, and authentic-source verification mechanisms, apply from 19 August 2026. Commission Implementing Regulation (EU) 2026/1735 enters into force on 11 August 2026 and updates the applicable standards and technical specifications; its Article 1(3), which adds specifications for Article 9 verification mechanisms, applies from 1 January 2027.

  • Treat EAA as attribute proof, not automatically as electronic identification.
  • Classify the attestation as non-qualified EAA, QEAA, or public-sector authentic-source EAA before relying on it.
  • For a QEAA, verify that the attestation identifies the qualified trust service provider, the subject, the attested attributes and their scope, validity period, unique attestation identity code, qualified signature or seal, supporting certificate location, and validity-status service.
  • For a public-sector authentic-source EAA, verify the issuing public body, the authentic-source basis, the subject, the attested attributes, validity period, identity code, qualified signature or seal, supporting certificate, and status-check location.

Does eIDAS give electronic attestations of attributes legal and evidentiary effect?

Yes. eIDAS says an cannot be denied legal effect or admissibility as evidence only because it is electronic or because it is not qualified. It gives stronger treatment to QEAAs and public-sector authentic-source attestations: they have the same legal effect as lawfully issued paper attestations.

Question 2

Who can issue QEAAs and authentic-source attestations?

A QEAA is issued by a qualified trust service provider and must be able to show, in machine-processable form, that it is a . eIDAS also requires Member States to make measures available so qualified trust service providers can verify certain public-sector attributes electronically, at the user's request, against authentic sources or recognised intermediaries. Articles 6 to 9 of Commission Implementing Regulation (EU) 2025/1569 apply from 19 August 2026, while the specifications added to Article 9 by Commission Implementing Regulation (EU) 2026/1735 apply from 1 January 2027; availability before the relevant date can still depend on the Member State and .

A public-sector authentic-source attestation is different: it is issued by, or on behalf of, a public sector body responsible for the . The Member State must ensure those bodies meet a reliability and trustworthiness level equivalent to qualified trust service providers, notify them to the Commission, and make the public list available through a secure signed or sealed channel.

  • For QEAAs, check the qualified trust service provider identity and whether the service has qualified status for the relevant attestation service.
  • For public-sector authentic-source attestations, check whether the public body is responsible for the or designated to act on its behalf.
  • For attributes such as address, age, nationality or citizenship, educational and professional qualifications, mandates, permits, licences, and company data, check whether the attribute relies on a public-sector and whether electronic verification is available.
  • Do not accept issuer branding alone as proof of authority; check the attestation category, certificate, signature or seal, status information, and relevant trusted-list or registry information.
Question 3

How should wallets and relying parties use attribute attestations?

For wallet use, eIDAS requires providers of electronic attestations of attributes to let EUDI Wallet users request, obtain, store, and manage attestations regardless of the Member State where the wallet is provided. Providers of QEAAs and public-sector authentic-source attestations must provide an interface with EUDI Wallets.

Cryptographic verification alone does not complete a relying-party check. The EUDI Wallet Architecture and Reference Framework describes an ecosystem in which wallets let users request attestations from trusted issuers, store them, and present them to relying parties with user control, selective disclosure, relying-party authentication, issuer authorisation checks, and revocation/status checks.

  • Authenticate the relying party before the wallet presents attributes, and show the user whether the relying party is registered to receive the requested attributes.
  • Request only attributes needed for the service, because selective disclosure and user approval are core wallet controls.
  • Verify the issuer is authorised to issue the relevant attestation type; where available, inspect the issuer registration certificate or query the relevant registry.
  • Check whether the attestation or its signing certificate has been revoked, because revoked QEAAs and public-sector authentic-source attestations lose validity from revocation and status must not revert.
  • Keep the relying-party purpose, requested attributes, user approval, issuer authority check, certificate and status-check result, attestation validity period, and revocation outcome together as evidence of the relying decision.

Can an eIDAS attribute attestation replace electronic identification for public online services?

Not by default. eIDAS says that where national law requires electronic identification and authentication to access an online public-sector service, person identification data in an does not substitute electronic identification unless the Member State specifically allows it. If that allowance exists, QEAAs from other Member States must also be accepted.

What should a relying party check before accepting an attribute attestation from an EUDI Wallet?

A relying party should verify the wallet presentation, issuer identity and authorisation, attestation category, attested attribute and scope, subject binding or pseudonym indication, validity period, signature or seal, supporting certificate, status-check location, and revocation status. It should also check that the requested attributes match its registered purpose and are limited to what the service needs.

Recommended next step

Turn eIDAS attribute-attestation checks into implementation evidence

Sorena can help translate EAA and QEAA requirements into issuer checks, wallet presentation controls, relying-party validation steps, and evidence fields tied to the sources on this page.

Research workflow
Open Research Copilot for EU eIDAS Regulation

Ask questions tied to cited sources about EAA, QEAA, EUDI Wallet, trusted lists, issuer checks, and relying-party validation using the cited sources on this page.

Explore next step
Talk to Sorena
Talk through implementation

Review your attribute-attestation flow, source gaps, and EUDI Wallet relying-party checks with Sorena.

Explore next step
Primary sources

References and citations

Regulation (EU) No 910/2014 (eIDAS), consolidated with the European Digital Identity amendments
eur-lex.europa.eu4 citations
Referenced sections
  • Primary legal source for EAA legal effects, QEAA requirements, authentic-source attestations, wallet interfaces, revocation, and Annex V to VII data requirements.
  • Supports the legal effect of EAAs and the Annex V and Annex VII content requirements for QEAAs and public-sector authentic-source attestations.
  • Supports issuer distinctions for QEAAs, authentic-source public-sector attestations, revocation effects, and the minimum list of attributes in Annex VI.
Show 1 more
  • Supports wallet-interface duties, public-service substitution limits, revocation effects, and the separation rules for EAA service providers.
"electronic attestation of attributes"
More quoted passages
"Verification of attributes against authentic sources"
"Issuing of electronic attestation of attributes to European Digital Identity Wallets"
Commission Implementing Regulation (EU) 2025/1569 on electronic attestations of attributes
eur-lex.europa.eu3 citations
Referenced sections
  • Current operational rules for QEAA and public-sector authentic-source attestation issuance, revocation, provider lists, catalogues, and verification mechanisms.
  • Sets issuance, revocation, public-sector provider-list, catalogue, and authentic-source verification rules, with Articles 6 to 9 applying from 19 August 2026.
  • Defines the phased operational framework for QEAA and authentic-source verification, including the 19 August 2026 application date for Articles 6 to 9.
Commission Implementing Regulation (EU) 2026/1735 amending Implementing Regulation (EU) 2025/1569 as regards applicable standards and specifications
eur-lex.europa.eu3 citations
Referenced sections
  • Amends Regulation (EU) 2025/1569 from 11 August 2026, with one amendment applying from 1 January 2027.
  • Amends the standards and technical specifications in Regulation (EU) 2025/1569 from 11 August 2026, with its Article 1(3) applying from 1 January 2027.
  • Adds specifications for the Article 9 verification mechanisms that apply from 1 January 2027.
Commission Implementing Regulation (EU) 2024/2977 on PID and electronic attestations of attributes for EUDI Wallets
eur-lex.europa.eu2 citations
Referenced sections
  • Implementation source for wallet-issued PID and EAA data handling, interoperability, validity status, and revocation-management details.
  • Supports wallet requirements for requesting, storing, deleting, sharing, and presenting PID and EAAs, plus validity-status and revocation-management details.
"person identification data and electronic attestations of attributes"
More quoted passages
"electronic attestations of attributes issued to European Digital Identity Wallets"
ETSI - Certification Authorities and other Trust Service Providers
portal.etsi.org2 citations
Referenced sections
  • Trust-service-provider source for eIDAS qualified services, trusted-list context, and conformity-assessment ecosystem terminology.
  • Explains the trust-service-provider and trusted-list context used to check qualified trust services under eIDAS.
"Certification Authorities and other Trust Service Providers"
ETSI TS 119 612 V2.4.1 trusted lists
etsi.org2 citations
Referenced sections
  • Current trusted-list specification for relying-party verification of trust-service status through signed trusted lists and the EU List of Trusted Lists model.
  • Defines the current trusted-list structure used to authenticate and interpret EU trusted lists and the Commission List of Trusted Lists when checking trust-service status.
"Trusted Lists"
European Commission - EUDI Wallet Architecture and Reference Framework
eu-digital-identity-wallet.github.io2 citations
Referenced sections
  • Technical architecture source for wallet roles, attestation providers, relying parties, selective disclosure, registration checks, and revocation/status checks.
  • Supports relying-party, wallet, issuer-authorisation, selective-disclosure, user-control, and attestation-revocation checks in the EUDI Wallet ecosystem.
"Architecture and Reference Framework"
More quoted passages
"Relying Parties"

Related guides

EU eIDAS Trusted Lists FAQ: LOTL, QTSP status, and validation evidence

How EU eIDAS Trusted Lists and the Commission LOTL support QTSP and qualified trust-service validation, with practical evidence checks for relying parties.

EUDI Wallet Relying Parties under eIDAS

What EUDI Wallet relying parties must do under eIDAS, when the harmonised registration rules apply, and how to control requested data, identification, validation, and evidence.

QES vs AdES under EU eIDAS: legal effect, certificates, QTSPs, and validation evidence

Compare qualified electronic signatures (QES) and advanced electronic signatures (AdES) under EU eIDAS, including legal effect, qualified certificates, QTSP status, QSCDs, and validation evidence.

What is a qualified trust service provider under eIDAS?

How to verify QTSP status under eIDAS using the qualified service, supervisory body decision, trusted list entry, conformity assessment evidence, and service-specific records.

What is a QWAC under the EU eIDAS Regulation?

Plain-language FAQ on qualified website authentication certificates under eIDAS, including website identity, QTSP trusted-list checks, browser recognition, and validation evidence.

eIDAS 2 deadlines and compliance calendar for EUDI Wallet and trust services

eIDAS 2 calendar separating binding EUDI Wallet, reporting, and trust-service dates from implementation milestones and technical programme updates.

Show all related guides (35)

eIDAS 2.0 vs eIDAS: EUDI Wallet and trust-service changes

Compare the original eIDAS electronic identification and trust-service framework with the eIDAS 2.0 amendments for EUDI Wallets, relying parties, attestations, QWACs, and supervision.

eIDAS Certificates and Authentication: qualified certificates, QWACs, and validation checks

Official source guide to eIDAS qualified certificates, website authentication certificates, trusted lists, relying-party checks, and validation evidence.

eIDAS checklist and evidence pack for trust services, signatures, and EUDI Wallet relying parties

Build an eIDAS evidence pack for qualified trust services, electronic signatures, trusted-list checks, certificate validation, supervisory records, and EUDI Wallet relying-party controls.

eIDAS compliance guide for trust services, QTSPs, signatures, and EUDI Wallet relying parties

Official source eIDAS compliance guide for trust-service classification, QTSP supervision evidence, qualified signatures, seals, time stamps, certificates, trusted-list validation, and EUDI Wallet relying-party records.

eIDAS electronic signatures: SES, AES, QES legal effect and evidence

An official source guide to eIDAS electronic-signature legal effect: SES, AES, QES, qualified certificates, QTSP trusted-list checks, validation, recognition, and evidence records.

eIDAS penalties and fines for trust service providers

Guide to eIDAS Article 16 fine floors, national penalty rules, supervisory action, qualified-status withdrawal, and trusted-list evidence.

eIDAS QES validation checks for relying parties

How to validate a qualified electronic signature under eIDAS: certificate, QTSP, trusted-list, QSCD, integrity, validation result, and evidence records.

eIDAS Qualified Trust Services: QTSP Selection

How to select an EU eIDAS qualified trust service provider: identify the qualified service type, verify trusted-list status, review supervision evidence, and retain certificate-policy records.

eIDAS remote signature and cloud HSM controls for QTSPs

Source-grounded guide to eIDAS remote signature controls: remote QSCD scope, server-side signing, QTSP evidence, signer authentication, certificate validation, and trusted-list checks.

eIDAS signature legal effect selector: SES, AES, AES-QC, or QES

Compare eIDAS signature levels by legal effect, governing form rules, qualified certificate status, QTSP evidence, QSCD use, validation, and public-service recognition.

eIDAS trust service role scoping workflow: TSP, QTSP, validator, relying party, or QTSP customer

Classify an eIDAS role by evidence: trust service provider, qualified trust service provider, signature or seal validator, EUDI Wallet relying party, relying party, or customer of a QTSP.

eIDAS trusted list validation: LOTL, QTSP status, and evidence

How to validate EU eIDAS trusted-list evidence: start from the Commission LOTL, confirm QTSP and qualified-service status, check certificate path and revocation data, and retain validation reports.

eIDAS vs ESIGN and UETA: EU qualified signatures vs U.S. e-signature laws

Compare eIDAS with ESIGN and UETA for electronic signatures, qualified certificates, trust services, cross-border recognition, validation evidence, and source gaps.

eIDAS vs ETSI EN 319 401: legal supervision and TSP policy requirements

Compare eIDAS and ETSI EN 319 401 for trust services: legal scope, QTSP supervision, conformity assessment, audits, incident evidence, and operational controls.

eIDAS vs GDPR for identity data: wallet, trust-service, and privacy obligations

Compare eIDAS identity, trust-service, and EUDI Wallet rules with GDPR duties for personal-data processing, minimisation, lawful basis, evidence, security, and user rights.

eIDAS vs NIS2 for trust service providers: QTSP and cybersecurity obligations

Compare eIDAS trust-service and QTSP duties with NIS2 cybersecurity risk-management, incident reporting, supervision, and evidence duties for trust service providers.

Electronic Attestations of Attributes under EU eIDAS: EAA, QEAA, issuers, wallets, and validation

Official source guide to electronic attestations of attributes under amended EU eIDAS: EAA, QEAA, public-sector authentic-source attestations, wallet use, issuer checks, relying-party validation, revocation, and legal effect.

EU eIDAS Applicability Test for Trust Services, Wallets, and Certificates

An official source eIDAS scope test for QTSPs, trust services, electronic signatures, seals, timestamps, QWACs, EUDI Wallet relying parties, and cross-border recognition evidence.

EU eIDAS checklist for signatures, trust services, and wallets

Checklist for eIDAS trust-service and EUDI Wallet controls: qualified status, trusted lists, certificates, signatures, seals, timestamps, validation evidence, and relying-party records.

EU eIDAS FAQ: signatures, QTSPs, trusted lists, QWACs, wallets, and validation

FAQ on eIDAS trust services and the European Digital Identity framework, covering advanced and qualified electronic signatures, QTSP status, trusted lists, QWACs, EUDI Wallet relying parties, attestations of attributes, and validation evidence.

EU eIDAS QTSP authorization and supervision guide

How qualified trust service providers obtain and keep qualified status under eIDAS, including conformity assessment reports, supervision, trusted lists, incidents, and evidence.

EU eIDAS QTSP Due Diligence Workflow for Trusted Lists, Certificates, and Evidence

Check a qualified trust service provider under eIDAS by validating trusted-list status, qualified service scope, certificates, policies, supervision, audits, and retained evidence.

EU eIDAS Requirements for Trust Services, Signatures, Seals, Wallets, and Evidence

Official source guide to core eIDAS requirements for trust service providers, qualified trust services, electronic signatures, seals, time stamps, trusted lists, and EUDI Wallet relying parties.

EUDI Wallet readiness for service providers under eIDAS

Readiness guide for organisations preparing to request or verify data from European Digital Identity Wallets: roles, registration, ARF alignment, selective disclosure, implementing acts, and evidence.

EUDI Wallet Relying Party Onboarding Workflow under eIDAS

Prepare an eIDAS wallet-relying-party registration, intended-use record, access-certificate controls, attribute request, validation evidence, and intermediary safeguards.

EUDI Wallet Relying Party Registration Under eIDAS

What eIDAS Article 5b and the EUDI Wallet ARF say about wallet relying party registration, intended uses, attribute requests, certificates, evidence, and Member State gaps.

EUDI Wallet Technical Architecture Guide under eIDAS

Technical guide to the EUDI Wallet architecture: ARF roles, wallet units, PID and attestations, relying parties, trust model, certificates, protocols, privacy, and security controls.

QWACs under eIDAS: website authentication certificates

A source-grounded guide to qualified website authentication certificates under eIDAS, covering Annex IV data, trusted lists, browser recognition, validation evidence, and QTSP checks.

What eIDAS Covers: eID, Trust Services, EUDI Wallet, and QWACs

A source-grounded guide to the systems and services covered by EU eIDAS: notified electronic identification, trust services, signatures, seals, time stamps, registered delivery, website authentication, trusted lists, the EUDI Wallet, and attribute attestations.