---
title: "eIDAS checklist and evidence pack for trust services, signatures, and EUDI Wallet relying parties"
canonical_url: "https://www.sorena.io/artifacts/eu/electronic-identification-and-trust-services-regulation/checklist-and-evidence"
source_url: "https://www.sorena.io/artifacts/eu/electronic-identification-and-trust-services-regulation/checklist-and-evidence"
author: "Sorena AI"
description: "Build an eIDAS evidence pack for qualified trust services, electronic signatures, trusted-list checks, certificate validation, supervisory records, and EUDI Wallet relying-party controls."
published_at: "2026-05-09"
updated_at: "2026-05-09"
keywords:
  - "eIDAS checklist"
  - "qualified trust service provider"
  - "qualified electronic signature"
  - "EUDI Wallet relying party"
  - "trusted lists"
  - "certificate validation"
  - "eIDAS"
  - "qualified trust services"
  - "EUDI Wallet"
---
**[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform

[Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io)

---

# 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.

*Evidence checklist* *EU eIDAS*

## eIDAS checklist and evidence pack

This checklist helps collect the records that prove how an eIDAS trust-service, e-signature, certificate, or EUDI Wallet relying-party decision was validated.

The focus is practical evidence: actor role, qualified status, trusted-list entry, certificate and revocation status, validation result, supervisory record, and implementation control.

An eIDAS evidence pack should show exactly what was relied on: the service type, the provider or relying-party role, the qualified or non-qualified status, the trusted-list and certificate evidence, and the controls that keep the decision current after launch.

## 1. Classify the eIDAS actor and service before collecting evidence

Start by naming the actor and service because the evidence differs for a trust service provider, a qualified trust service provider, a signatory, a certificate issuer, a website-authentication certificate user, a wallet provider, an attestation provider, or an EUDI Wallet relying party.

For each product flow, record whether the evidence concerns electronic identification, an electronic signature or seal, a certificate, validation or preservation, registered delivery, electronic attestation of attributes, electronic archiving, an electronic ledger, or a wallet presentation.

- Actor record: legal entity, establishment country, role under eIDAS, service owner, and whether the actor is providing, relying on, validating, or preserving a trust service.
- Service record: exact trust-service type, qualified or non-qualified claim, countries where the service is used, and whether a public-sector or private-sector relying party is involved.
- Wallet relying-party record: registration Member State, contact details, intended wallet use, requested data categories, and the user journey that displays the specific data request.
- Boundary record: what is outside the eIDAS claim, such as ordinary login, non-qualified document approval, or data processing controls that belong under GDPR rather than eIDAS.

Sources for this answer:

- [Regulation (EU) No 910/2014, consolidated eIDAS text](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX%3A02014R0910-20240520&ref=sorena.io) - Defines relying parties, qualified electronic signatures, trust services, qualified trust services, wallet functions, and electronic attestations of attributes.
- [European Commission - Wallet for service providers](https://ec.europa.eu/digital-building-blocks/sites/spaces/EUDIGITALIDENTITYWALLET/pages/881984674/Wallet+for+service+providers?ref=sorena.io) - Grounds the relying-party checklist: registration, requested data, user-facing identification, validation of PID and EAA data, and pseudonym handling.

## 2. Prove qualified status with trusted lists and supervisory records

Do not treat a provider's marketing page or certificate common name as proof of qualified status. For qualified trust services, keep the supervisory and trusted-list evidence that connects the provider, service type, service status, service digital identity, and relevant dates.

The evidence should make it possible for a reviewer to reproduce the qualified-status decision at the time the transaction, certificate, attestation, or signature was accepted.

- Trusted-list snapshot: Member State trusted list or EU List of Trusted Lists source, retrieval time, list signature or seal validation result, scheme operator, service type identifier, service current status, and service digital identity.
- Qualified-status check: whether the provider and the exact service are listed as qualified for the service being relied on, not merely present in a trust-service directory.
- Status-history check: service status start time, prior status entries when relevant, and whether the status was granted, withdrawn, ceased, suspended, or otherwise unsuitable for the transaction.
- Supervisory record: supervisory-body grant or withdrawal decision, conformity assessment report reference, audit or assessment request, and any termination-plan evidence needed if a qualified trust service ceases activities.

Sources for this answer:

- [Regulation (EU) No 910/2014, consolidated eIDAS text](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX%3A02014R0910-20240520&ref=sorena.io) - Requires supervisory bodies to grant and withdraw qualified status, analyse conformity assessment reports, and inform trusted-list bodies of status decisions.
- [ETSI TS 119 612 trusted lists](https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.03.01_60/ts_119612v020301p.pdf?ref=sorena.io) - Specifies trusted-list structure, including scheme information, TSP information, service type, service digital identity, current status, and status history.
- [European Commission - eSignature building block](https://ec.europa.eu/digital-building-blocks/sites/spaces/DIGITAL/pages/467109036/eSignature?ref=sorena.io) - Identifies the eIDAS Dashboard and Trusted List Browser as practical tools for finding qualified trust service providers and trusted-list information.

## 3. Validate signature, seal, certificate, and revocation evidence

For a qualified electronic signature, the evidence must support more than a cryptographic pass result. It must show that the supporting certificate was qualified and valid at signing time, the provider was qualified, the validation data matched the signed data, the signatory identity data was provided, any pseudonym was indicated, the signature creation device requirement was met, and the signed data remained intact.

Keep the validation policy, validation time, certificate chain, revocation data, timestamp evidence, and validation report together so the result can be reviewed after certificate expiry, revocation, or trust-list changes.

- Certificate evidence: qualified-certificate indication, issuing qualified trust service provider, signatory or seal-creator data, validity period, status-service location, and certificate path used for validation.
- Revocation and suspension evidence: OCSP or CRL response, response time, source endpoint, result, and proof that a revoked or suspended qualified certificate was not treated as valid after its effective status change.
- Signature validation evidence: format, signed data hash or identifier, validation time, best-signature-time where used, validation policy, validation report, and whether the final qualified-signature determination passed.
- QSCD evidence: proof used to determine that the private key was held in a qualified signature creation device or managed by a qualified remote signature creation service when the claim depends on qualified signature status.
- Preservation evidence: long-term validation material, timestamp records, and any evidence record added to a XAdES, CAdES, PAdES, or ASiC object.

Sources for this answer:

- [Regulation (EU) No 910/2014, consolidated eIDAS text](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX%3A02014R0910-20240520&ref=sorena.io) - Sets the validation conditions for qualified electronic signatures and the certificate revocation and suspension consequences.
- [European Commission - Digital Signature Service documentation](https://ec.europa.eu/digital-building-blocks/DSS/webapp-demo/doc/dss-documentation.html?ref=sorena.io) - Documents practical DSS validation outputs, trusted-list interpretation, revocation data, best-signature-time handling, and evidence-record support.
- [ETSI TS 119 612 trusted lists](https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.03.01_60/ts_119612v020301p.pdf?ref=sorena.io) - Supports using trusted-list service digital identities and service status as trust anchors in certificate path and signature validation.

## 4. Add EUDI Wallet relying-party and attestation controls

A relying party that requests wallet data should keep evidence for registration, data minimisation, user display, wallet authenticity checks, PID and EAA validation, and pseudonym handling. The record should show what was requested from the wallet, why it was needed for the service, and how the user saw and approved the request.

For attestations, keep separate records for Person Identification Data, qualified electronic attestations of attributes, public-body authentic-source attestations, and non-qualified electronic attestations of attributes because the validation and legal-effect evidence is not the same.

- Registration evidence: Member State registration record, relying-party identity, contact details, intended wallet use, requested attribute categories, and change-notification log.
- Data request evidence: attribute list shown to the user, purpose, minimum-data justification, user confirmation step, and whether pseudonymous authentication was accepted when legal identification was not required.
- Validation evidence: wallet authenticity check, PID validation result, EAA or QEAA validation result, issuer or authentic-source evidence, trust-list or certificate status, and error-handling outcome.
- Attestation evidence: attestation type, issuer, qualified or public-body status if claimed, revocation status, certificate supporting the issuer signature or seal, and the location where that certificate can be obtained.
- Implementation controls: API version, technical-specification version, logging fields, replay and tamper checks, incident escalation path, and evidence retention owner.

Sources for this answer:

- [Regulation (EU) No 910/2014, consolidated eIDAS text](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX%3A02014R0910-20240520&ref=sorena.io) - Defines wallet functions, relying-party validation responsibility, pseudonym treatment, qualified attestations of attributes, and authentic-source attestations.
- [European Commission - Wallet for service providers](https://ec.europa.eu/digital-building-blocks/sites/spaces/EUDIGITALIDENTITYWALLET/pages/881984674/Wallet+for+service+providers?ref=sorena.io) - Explains service-provider registration, wallet data requests, user confirmation, PID and EAA validation, trust-list checks, and certification status checks.
- [EUDI Wallet Architecture and Reference Framework](https://eu-digital-identity-wallet.github.io/eudi-doc-architecture-and-reference-framework/latest/architecture-and-reference-framework-main/?ref=sorena.io) - Provides ecosystem and architecture context for wallet providers, relying parties, attestations, trust model, certification, and implementation specifications.

## 5. Close the evidence pack only when controls are reproducible

The checklist is complete only when another reviewer can repeat the validation with the same sources, records, and timestamps. A screenshot without the underlying trusted-list source, certificate status response, validation report, or supervisory reference is not enough for a durable eIDAS evidence pack.

Reopen the pack when a service status changes, a certificate is revoked or suspended, a wallet provider or attestation provider loses certification, a relying-party registration changes, validation tooling or policy changes, or the product begins relying on a new qualified trust service.

- Store source URLs, retrieval timestamps, validation reports, trust-list files or references, certificate and revocation responses, supervisory records, approval notes, and implementation-control evidence in the same evidence package.
- Assign owners for legal classification, trust-list monitoring, certificate validation, wallet integration, incident response, supplier management, and evidence retention.
- Block release when qualified status is asserted but the exact provider-service pair is missing from trusted-list evidence, when certificate status is unknown, or when the relying party requests data not covered by its wallet registration record.
- Do not add penalties, market deadlines, or certification promises unless the cited eIDAS source and cited source material directly support them.

Sources for this answer:

- [Regulation (EU) No 910/2014, consolidated eIDAS text](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX%3A02014R0910-20240520&ref=sorena.io) - Supports release gates tied to qualified status, certificate validity, revocation, supervisory reporting, and wallet relying-party responsibilities.
- [ETSI TS 119 612 trusted lists](https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.03.01_60/ts_119612v020301p.pdf?ref=sorena.io) - Supports repeatable trusted-list monitoring through service current status, status starting time, service history, and trusted-list re-issuance practices.
- [ENISA - Guidelines on supervision of qualified trust services](https://www.enisa.europa.eu/publications/tsp-supervision?ref=sorena.io) - Provides supervisory context for qualified trust service oversight and Article 20 supervision practices.

*Recommended next step*

*Placement: before sources*

## Review qualified trust-service and wallet evidence before relying on it

Sorena can help organize eIDAS source checks, trusted-list evidence, certificate validation results, wallet relying-party records, and implementation controls into a reusable review pack.

- [Open Research Copilot for eIDAS evidence](/solutions/research-copilot.md): Ask cited questions about qualified trust services, electronic signatures, trusted lists, certificate status, and EUDI Wallet relying-party evidence.
- [Discuss an eIDAS evidence review](/contact.md): Review provider status, validation logs, relying-party registration, and source gaps before committing to an eIDAS implementation claim.

## Primary sources

- [Regulation (EU) No 910/2014, consolidated eIDAS text](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX%3A02014R0910-20240520&ref=sorena.io) - Primary legal source for eIDAS actor definitions, trust-service categories, qualified status, signature validation, wallet relying-party duties, attestations, and supervisory tasks.
  - Quote: "electronic identification and trust services"
- [European Commission - Wallet for service providers](https://ec.europa.eu/digital-building-blocks/sites/spaces/EUDIGITALIDENTITYWALLET/pages/881984674/Wallet+for+service+providers?ref=sorena.io) - Practical Commission guidance for relying parties that request data from EUDI Wallet users, including registration, data requests, validation, pseudonym, certification, and trust-list considerations.
  - Quote: "EU Digital Identity Wallets for service providers"
- [European Commission - eSignature building block](https://ec.europa.eu/digital-building-blocks/sites/spaces/DIGITAL/pages/467109036/eSignature?ref=sorena.io) - Commission building-block page identifying eSignature resources, DSS, the eIDAS Dashboard, the Trusted List Browser, and validation tests.
  - Quote: "Trusted List Browser"
- [European Commission - Digital Signature Service documentation](https://ec.europa.eu/digital-building-blocks/DSS/webapp-demo/doc/dss-documentation.html?ref=sorena.io) - Technical documentation for signature and certificate validation, revocation data, trusted-list use, qualification determination, and evidence records.
  - Quote: "Digital Signature Service"
- [ETSI TS 119 612 trusted lists](https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.03.01_60/ts_119612v020301p.pdf?ref=sorena.io) - Technical specification for trusted-list format, TSP and service information, service digital identity, service status, status history, and trusted-list use in validation.
  - Quote: "Trusted Lists"
- [EUDI Wallet Architecture and Reference Framework](https://eu-digital-identity-wallet.github.io/eudi-doc-architecture-and-reference-framework/latest/architecture-and-reference-framework-main/?ref=sorena.io) - Architecture and ecosystem source for EUDI Wallet roles, relying-party interactions, attestations, trust model, certification, and implementation specifications.
  - Quote: "Architecture and Reference Framework"
- [ENISA - Guidelines on supervision of qualified trust services](https://www.enisa.europa.eu/publications/tsp-supervision?ref=sorena.io) - Supervision-focused source for qualified trust service provider oversight and supervisory evidence context.
  - Quote: "supervision of qualified trust services"

## Related Topic Guides

- [eIDAS 2 deadlines and compliance calendar for EUDI Wallet and trust services](/artifacts/eu/electronic-identification-and-trust-services-regulation/deadlines-and-compliance-calendar.md): Calendar of official source eIDAS and eIDAS 2 milestones for EUDI Wallet delivery, implementing acts, annual supervision reports, QTSP transitions, pilots, and ARF evidence.
- [eIDAS 2.0 vs eIDAS: EUDI Wallet and trust-service changes](/artifacts/eu/electronic-identification-and-trust-services-regulation/eidas2-vs-eidas.md): 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/certificates-and-authentication.md): Official source guide to eIDAS qualified certificates, website authentication certificates, trusted lists, relying-party checks, and validation evidence.
- [eIDAS compliance guide for trust services, QTSPs, signatures, and EUDI Wallet relying parties](/artifacts/eu/electronic-identification-and-trust-services-regulation/compliance.md): 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/electronic-signatures-and-legal-effect.md): 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/penalties-and-fines.md): Official source guide to eIDAS Article 16 penalties, administrative fine mechanics, supervisory bodies, qualified-status withdrawal, and trusted-list evidence.
- [eIDAS QES validation checks for relying parties](/artifacts/eu/electronic-identification-and-trust-services-regulation/qes-validation.md): 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/qualified-trust-services-and-qtsp-selection.md): 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/remote-signature-and-cloud-hsm-controls.md): Official source 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/signature-legal-effect-selector-workflow.md): Select the right eIDAS signature level by legal effect, risk, qualified certificate status, QTSP evidence, QSCD use, validation result, and cross-border recognition.
- [eIDAS trust service role scoping workflow: TSP, QTSP, validator, relying party, or QTSP customer](/artifacts/eu/electronic-identification-and-trust-services-regulation/trust-service-role-scoping-workflow.md): 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/trust-list-validation.md): 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/eidas-vs-esign-and-ueta.md): 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/eidas-vs-etsi-en-319-401.md): 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/eidas-vs-gdpr-identity-data.md): 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/eidas-vs-nis2-trust-services.md): 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/electronic-attestations-of-attributes.md): 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/applicability-test.md): 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 attribute attestations: EAA, QEAA, wallet, and relying party checks](/artifacts/eu/electronic-identification-and-trust-services-regulation/faq/attribute-attestations.md): What electronic attestations of attributes mean under eIDAS, how QEAAs differ from public-sector and non-qualified attestations, and what issuers, wallets, and relying parties should verify.
- [EU eIDAS checklist for signatures, trust services, and wallets](/artifacts/eu/electronic-identification-and-trust-services-regulation/checklist.md): 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/faq.md): 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/qtsp-authorization-and-supervision.md): 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/qtsp-due-diligence-workflow.md): 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/requirements.md): 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.
- [EU eIDAS Trusted Lists FAQ: LOTL, QTSP status, and validation evidence](/artifacts/eu/electronic-identification-and-trust-services-regulation/faq/trusted-lists.md): 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 readiness for service providers under eIDAS](/artifacts/eu/electronic-identification-and-trust-services-regulation/eudi-wallet-readiness.md): 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 Parties under eIDAS](/artifacts/eu/electronic-identification-and-trust-services-regulation/faq/eudi-wallet-relying-party.md): What EUDI Wallet relying parties must do under eIDAS: register, declare intended wallet use and requested data, identify themselves to users, and keep request evidence.
- [EUDI Wallet Relying Party Onboarding Workflow under eIDAS](/artifacts/eu/electronic-identification-and-trust-services-regulation/wallet-onboarding-workflow.md): An official source onboarding workflow for organisations that want to request data from European Digital Identity Wallet users as eIDAS wallet relying parties.
- [EUDI Wallet Relying Party Registration Under eIDAS](/artifacts/eu/electronic-identification-and-trust-services-regulation/eudi-wallet-relying-party-registration.md): 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/eudi-wallet-technical-architecture-guide.md): Technical guide to the EUDI Wallet architecture: ARF roles, wallet units, PID and attestations, relying parties, trust model, certificates, protocols, privacy, and security controls.
- [QES vs AdES under EU eIDAS: legal effect, certificates, QTSPs, and validation evidence](/artifacts/eu/electronic-identification-and-trust-services-regulation/faq/qes-vs-ades.md): Compare qualified electronic signatures (QES) and advanced electronic signatures (AdES) under EU eIDAS, including legal effect, qualified certificates, QTSP status, QSCDs, and validation evidence.
- [QWACs under eIDAS: website authentication certificates](/artifacts/eu/electronic-identification-and-trust-services-regulation/qwacs.md): An official source 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](/artifacts/eu/electronic-identification-and-trust-services-regulation/what-eidas-covers.md): An official source 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.
- [What is a qualified trust service provider under eIDAS?](/artifacts/eu/electronic-identification-and-trust-services-regulation/faq/qualified-trust-service-provider.md): 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?](/artifacts/eu/electronic-identification-and-trust-services-regulation/faq/qwac.md): Plain-language FAQ on qualified website authentication certificates under eIDAS, including website identity, QTSP trusted-list checks, browser recognition, and validation evidence.


---

[Privacy Policy](https://www.sorena.io/privacy) | [Terms of Use](https://www.sorena.io/terms-of-use) | [DMCA](https://www.sorena.io/dmca) | [About Us](https://www.sorena.io/about-us)

(c) 2026 Sorena AB (559573-7338). All rights reserved.

Source: https://www.sorena.io/artifacts/eu/electronic-identification-and-trust-services-regulation/checklist-and-evidence