---
id: trust-roles
title: "Trust Roles: Wallet Providers, Issuers and Relying Parties"
description: The roles of the EU Digital Identity Wallet trust framework, the ETSI list and certificate profile of each role, the "Used As" role of a trust anchor in the iGrant.io Organisation Wallet Suite, and the NXD Trust List for each role.
hide_title: false
sidebar_label: Trust Roles
keywords: [trust roles, wallet provider, PID provider, QEAA provider, PuB-EAA provider, EAA provider, mDL issuer, status issuer, access certificate, registration certificate, WRPAC, WRPRC, LoTE, ETSI TS 119 602, ETSI TS 119 412-6, Used As, NXD Trust List]
slug: /trust-roles/
---

> **Build this with an AI coding agent.** Install the iGrant.io Agent Skills, then ask your agent to build the integration:
>
> ```bash
> npx skills add L3-iGrant/skills
> ```

<head>
  <title>Trust Roles: Wallet Providers, Issuers and Relying Parties | iGrant.io DevDocs</title>
  <meta name="description" content="The roles of the EU Digital Identity Wallet trust framework, the ETSI list and certificate profile of each role, the 'Used As' role of a trust anchor in the iGrant.io Organisation Wallet Suite, and the NXD Trust List for each role."/>
</head>

import NoteBox from '@site/src/components/NoteBox';

<NoteBox title="Specifications:" variant="info">
<ul>
<li><a href="https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/blob/v3.0.0/docs/main/06-trust-model.md" target="_blank" rel="noopener noreferrer">ARF v3.0.0</a>, §6.2 to §6.4 (who is notified, registered and listed)</li>
<li><a href="https://www.etsi.org/deliver/etsi_ts/119600_119699/119602/01.01.01_60/ts_119602v010101p.pdf" target="_blank" rel="noopener noreferrer">ETSI TS 119 602 V1.1.1</a>, Annexes D to I (the EU profiles of lists of trusted entities)</li>
<li><a href="https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.04.01_60/ts_119612v020401p.pdf" target="_blank" rel="noopener noreferrer">ETSI TS 119 612 V2.4.1</a>, §5.5.1 (service type identifier)</li>
<li><a href="https://www.etsi.org/deliver/etsi_ts/119400_119499/11941206/01.01.01_60/ts_11941206v010101p.pdf" target="_blank" rel="noopener noreferrer">ETSI TS 119 412-6 V1.1.1</a> (certificate profiles of PID, wallet, EAA, QEAA and PuB-EAA providers), <a href="https://www.etsi.org/deliver/etsi_ts/119400_119499/11941108/01.01.01_60/ts_11941108v010101p.pdf" target="_blank" rel="noopener noreferrer">ETSI TS 119 411-8 V1.1.1</a> (access certificates) and <a href="https://www.etsi.org/deliver/etsi_ts/119400_119499/119475/01.02.01_60/ts_119475v010201p.pdf" target="_blank" rel="noopener noreferrer">ETSI TS 119 475 V1.2.1</a> (registration certificates)</li>
</ul>
</NoteBox>

## In short

* A **role** says what a party is trusted to do: provide wallets, issue PIDs, issue a kind of attestation, or issue the certificates of relying parties.
* The EU publishes **one list for each role**, and each list follows an ETSI profile. A trusted party is listed for its role, not in general.
* A trust check always asks for **one role**. A party that is listed for another role is not trusted for this check.
* In the iGrant.io Organisation Wallet Suite, each trust anchor has one role, shown as **Used As**. The NXD Trust List, which iGrant.io uses for demos, interoperability tests and other non-production use, has one list for each role.

## The roles

| Role | Who it is | Where the EU lists it | Certificate profile | NXD Trust List |
| --- | --- | --- | --- | --- |
| **Wallet provider** | Signs the wallet instance attestations (WIA) and key attestations of its wallet units | Wallet Provider LoTE: TS 119 602 Annex E, type `EUWalletProvidersList` | TS 119 412-6 | `NXD-TL-WalletProviders.xml` |
| **PID provider** | Issues person identification data | PID Provider LoTE: TS 119 602 Annex D, type `EUPIDProvidersList` | TS 119 412-6 | `NXD-TL-PID.xml` |
| **QEAA provider** | Issues qualified attestations of attributes | National trusted lists: TS 119 612, a qualified trust service provider with an EAA service | TS 119 412-6 | `NXD-TL-QEAA.xml` (TS 119 612) |
| **PuB-EAA provider** | Issues attestations for a public sector body | PuB-EAA Provider LoTE: TS 119 602 Annex H, type `EUPubEAAProvidersList` | TS 119 412-6 | `NXD-TL-PubEAA.xml` |
| **EAA provider** | Issues non-qualified attestations of attributes | Not on an EU list: these providers are not notified (ARF §6.3.2) | TS 119 412-6 | `NXD-TL-EAA.xml` (TS 119 612) |
| **mDL issuer** | Issues mobile driving licences (ISO/IEC 18013-5) | Not on an EU list. Relying parties use the IACA certificate of the issuing authority. | ISO/IEC 18013-5 (IACA and document signer) | none |
| **Status issuer** | Signs the status list of a credential | In a list of trusted entities, the revocation services of PID and PuB-EAA providers give this role. A trusted list (TS 119 612) cannot be used as status issuer. By default, the credential signer may sign the status list. | | none |
| **Access certificate provider** | Issues the access certificates (WRPAC) of providers and relying parties | Access Certificate Authority LoTE: TS 119 602 Annex F, type `EUWRPACProvidersList` | TS 119 411-8 | `NXD-TL-WRPAC.xml` |
| **Registration certificate provider** | Issues the registration certificates (WRPRC) of providers and relying parties | Registration Certificate Provider LoTE: TS 119 602 Annex G, type `EUWRPRCProvidersList` | TS 119 475 | `NXD-TL-WRPRC.xml` |
| **Registrars and registers** | Register providers and relying parties in a Member State | TS 119 602 Annex I, type `EURegistrarsAndRegistersList` | | `NXD-TL-Registrars.xml` |

The type URIs start with `http://uri.etsi.org/19602/LoTEType/`. The NXD lists are at `https://trustlist.nxd.foundation/trust-lists/`, followed by the file name. The six TS 119 602 lists are also published in JSON, for example `nxd-wallet-providers-lote.json`.

<NoteBox title="A relying party is not on a list:" variant="note">
A relying party is registered in the register of its Member State, not listed in a trusted list. Wallets trust it through its access certificate, which an access certificate authority on the Access Certificate Authority LoTE issued.
</NoteBox>

## In the iGrant.io Organisation Wallet Suite

On the **Trust Anchors** page, each trust anchor has exactly one role, **Used As** (`usedFor` in the API). A national trusted list that serves several roles therefore needs one trust anchor for each role.

Each check asks for one role, and its accepted list offers only the trust anchors of that role:

| Check | Role it asks for |
| --- | --- |
| The issuer checks the WIA and the key attestations (credential definition) | Wallet provider |
| The verifier checks who signed a credential (credential query), and the organisation wallet checks who signed a credential it receives (holder configuration) | PID provider for a PID, mDL issuer for an mDL, otherwise any issuer role: PID provider, QEAA provider, PuB-EAA provider, EAA provider or mDL issuer |
| The verifier or the organisation wallet checks who signed the status list | Status issuer |
| The organisation wallet checks the signed metadata of an issuer, or the request of a relying party | Access certificate provider |

### The role of an entry

* **In a list,** the service type of the entry gives its role (ETSI TS 119 612 §5.5.1, TS 119 602 §6.6.1), or else the list type. In a trusted list (TS 119 612), only the service types of attestations of attributes (`http://uri.etsi.org/TrstSvc/Svctype/EAA`, `EAA/Q` and `EAA/Pub-EAA`) give a role, and also `http://uri.etsi.org/TrstSvc/Svctype/WRPAC`, which some pilot lists use for access certificates (it is not a type of TS 119 612). The list names no role for its other services.
* **A trust anchor uses only the entries for its role:** the entries that have its role, and the entries whose list names no role. An entry with no role takes the role of the trust anchor, but never **Status issuer**. The other entries are not used. The **Entries** column of the Trust Anchors page and the entries of a trust anchor show which entries it uses; see [Manage Trust Anchors](/docs/trust-anchors/#look-at-the-entries).
* **For a CA (X.509) trust anchor,** its **Used As** role applies to each of its CA certificates.

When an entry matches, the check also checks the role of the entry. An entry for another role does not make the signer trusted: the result is `not_trusted` with the reason `wrong_role`.

## Support notes

* **Registration certificate provider:** you can add trust anchors with this role, but no check uses it yet. The Organisation Wallet Suite does not yet check registration certificates (WRPRC).
* **Registrars and registers:** there is no **Used As** role for this list.
* **QEAA, PuB-EAA and EAA providers:** no credential type selects these roles on its own. A check asks for any issuer role, unless the credential is a PID or an mDL.

## Related pages

* [Who Trusts Whom: The EU Digital Identity Wallet Trust Model](/docs/trust-model/)
* [Trusted Lists and Lists of Trusted Entities](/docs/trust-etsi-lists/)
* [Certificates and Certificate Chains](/docs/trust-pki/)
* [Key Management: certificate presets for each role](/docs/openid4vc-key-management/#credential-categories-and-key-usage-types)
* [Register Your Organisation on a Trust List](/docs/trust-relying-party-registration/)
