Partner register โ Key concepts
The register uses the vocabulary of the European texts (CIR 2025/848 and 2026/1730, the ARF, EUDI TS5 and TS6, ETSI TS 119 475 and TS 119 411-8). This page explains each term the way the partner space uses it.
Register, registrar, wallet-relying party
- Wallet-relying party
- An organisation that relies on the wallet: it requests data from it (a verifier), or puts attestations into it (an issuer, also called a PID or attestation provider). Both register.
- Register
- The public list of wallet-relying parties and their services. Anyone can search it, in the web page or through the TS5 API.
- Registrar
- The body that runs the register and issues its certificates. On the playground, the sandbox registrar is France Identitรฉ.
- Partner space
- Where your team registers and manages its organisations and services:
/espace.
Organisation and services
- Organisation
- The legal entity that registers. It has a legal name, a trading name, a SIREN number and an identifier in the register,
FR-RCS.Sandbox.B.<SIREN>. In certificates it is identified by NTRFR-<SIREN>.
- Service
- What talks to the wallet. An organisation can have several services, of three kinds:
| Kind |
In the partner space |
What it declares |
What it gets |
| Verification service |
Verify data |
Its intended uses: the data it requests and why |
An access certificate, one registration certificate per intended use |
| Intermediary service |
Verify for other organisations |
No data of its own |
An access certificate; its clients' registration certificates name it |
| Issuance service |
Issue an attestation |
Its issuer address, the attestations it issues, its signing certificate |
An access certificate, one registration certificate for the attestations it issues, its signing certificate in the trusted lists |
- Intended use
- One reason a verification service requests data: a purpose shown to the user, a privacy policy, and the attestations and data items requested for that purpose. A service can have several intended uses, for example check the guest's identity at check-in and apply the club member rate.
- Entitlement
- The role an organisation holds in the register, written as an ETSI URI. The partner space sets it for you.
| Role |
Given when |
ETSI entitlement |
| Service provider |
You declare a verification service |
https://uri.etsi.org/19475/Entitlement/Service_Provider |
| PID provider |
You choose PID provider for an issuance service |
โฆ/Entitlement/PID_Provider |
| Qualified attestation provider |
You choose Qualified attestation provider |
โฆ/Entitlement/QEAA_Provider |
| Public body issuing attestations |
You choose Public body issuing attestations |
โฆ/Entitlement/PUB_EAA_Provider |
| Non-qualified attestation provider |
You choose it, or you declare an attestation that is not a PID without holding an attestation role |
โฆ/Entitlement/Non_Q_EAA_Provider |
Roles only grow: declaring a new attestation can add a role, never remove one.
Certificates
flowchart TB
subgraph R["Registrar (France Identitรฉ, sandbox)"]
CA["WRPAC CA<br/>/pki/ca.cer"]
RS["Registrar signing certificate<br/>/pki/registrar-signing-ca.cer"]
TL["Trusted-list signer<br/>/pki/trust-list-signing.cer"]
end
CA -- issues --> WRPAC["Access certificate (WRPAC)<br/>X.509, your key"]
RS -- signs --> WRPRC["Registration certificate (WRPRC)<br/>JWT and CWT"]
RS -- signs --> SL["WRPRC status list"]
TL -- signs --> LOTE["Lists of trusted entities<br/>and XML trusted lists"]
WRPRC -. "wrpac_binding" .-> WRPAC
IACA["Your IACA (issuers)"] -- issues --> DS["Your signing certificate<br/>(document signer)"]
LOTE -. "lists" .-> IACA
- Access certificate (WRPAC)
- An X.509 certificate that authenticates your service to the wallet. Your service signs its presentation requests (or its issuer metadata) with the matching private key. One per service, valid 730 days. The partner space calls it the access certificate. See Certificates.
- Registration certificate (WRPRC)
- A signed statement by the registrar of what a service is registered for: for a verifier, one per intended use, listing the purpose and the data it may request; for an issuer, one listing the attestations it may issue. Valid at most 12 months, published as a JWT (
rc-wrp+jwt) and a CWT (rc-wrp+cwt). The wallet uses it to show the user who is asking and why, and to warn about requests beyond it. See Certificates.
- IACA and signing certificate
- An issuer signs its attestations with a signing certificate (the document signer), issued by its own certificate authority, the IACA. The register publishes the IACA (or the signing certificate) in its trusted lists so that wallets accept the attestations. The register never issues these for you, except when you let the sandbox generate them.
- CSR
- A certificate signing request: the public request your team creates with its own private key, so the register can issue your access certificate without ever seeing the key.
- Proof of possession
- A short message, prepared by the register and signed with your issuer key, that proves you hold the key of the signing certificate you declare.
Publications
- Trusted lists
- What the register publishes for wallets: four ETSI TS 119 602 lists of trusted entities (PID providers, WRPAC providers, WRPRC providers, public-body EAA providers) and two ETSI TS 119 612 XML trusted lists. See Trusted lists.
- Status list
- A signed, compressed list giving the status of every registration certificate: valid, suspended or revoked. Each WRPRC points to its entry.
- Publication
- Every change in the register produces a new signed publication. Suspended and withdrawn services stay visible in the TS5 register (with their status) but leave the trusted lists and the wallet lookups.
Statuses
| Status |
What it means |
Reversible |
| Active |
The service is published; wallets accept its requests within what it declared. |
โ |
| Certificate required |
No valid access certificate, and no intermediary presents it. |
Yes: get a certificate or choose an intermediary |
| Suspended |
Left out of register answers; its registration certificates read suspended. |
Yes: Reactivate |
| Withdrawn / Revoked |
Final: certificates revoked. Register a new service, or declare a new intended use. |
No |
Other terms
- Intermediary
- An organisation that queries the wallet on behalf of other registered services, with its own access certificate. Its clients' registration certificates name it (
act.sub, intermediary). See Intermediaries.
- Prepared request
- A set of attestations, data items and a suggested purpose that an intermediary publishes for its clients to start from.
- Attestation catalogue
- Every attestation type that registered issuers deliver today, with exactly the data each declares. Verifiers pick their data from it. See the catalogue.
- Over-asking
- Requesting data beyond what the registration certificate states. The register does not pre-authorise requests: the wallet checks them at presentation time, against the WRPRC (ARF v3.0.0, RPRC_21), and warns the user.