Partner register โ Standards and compliance¶
The register implements the European texts on wallet-relying parties as a sandbox. This page lists the texts it follows, how it maps them, and what it does not claim.
What this register is not
It is not a designated national register, a notified service, a qualified trust service or an official France Identitรฉ or French State service, and this page is not a legal opinion. Its certificates and trusted lists are a standalone test scheme: no production wallet or legal trust decision may rely on them.
Texts followed¶
| Text | Version | What the register takes from it |
|---|---|---|
| Commission Implementing Regulation (EU) 2025/848 | 2025/848 | Registration of wallet-relying parties, the register's content and API (Annex II), the WRPRC (Annex V) |
| Commission Implementing Regulation (EU) 2026/1730 | 2026/1730 | The amendments to 2025/848: information collected (Annex I), WRPRC issuance (Art. 8), intermediaries |
| EUDI Architecture and Reference Framework | v3.0.0 (23 July 2026) | Registration, over-asking control (RPRC_21), intermediaries |
| EUDI TS5, common formats and API for relying-party registration | v1.5 (20 August 2026) | The /wrp register API and its data model |
| EUDI TS6, common set of relying-party information | v1.0.1 (January 2026) | What is collected per party, service and intended use |
| ETSI TS 119 475 | V1.2.1 (March 2026) | Registration certificates (WRPRC): claims, rc-wrp+jwt and rc-wrp+cwt |
| ETSI TS 119 411-8 | V1.1.1 (October 2025) | Access certificates (WRPAC): NCP/QCP profiles, subject, extensions |
| ETSI EN 319 411-1 | V1.4.1 (October 2023) | Baseline certificate practices, where applicable |
| ETSI TS 119 602 | โ | Lists of trusted entities for EUDI wallets |
| ETSI TS 119 612 | v2.4.1 (TSL v6) | XML trusted lists |
| ETSI TS 119 472-2 and -3 | โ | Carrying registration certificates in presentation requests and issuer metadata |
| RFC 5280, RFC 7515/7519, RFC 8392 | โ | X.509, CRL, OCSP; JWS and JWT; CWT |
| IETF Token Status List | draft | WRPRC status lists |
| ISO/IEC 18013-5, OpenID4VP 1.0 (DCQL), OpenID4VCI, W3C Digital Credentials API | โ | The protocols the certificates are used in |
Transparency is not pre-authorisation¶
Under CIR 2026/1730, the data a service requests and why (Annex I, points 7 to 10) are collected for transparency: the registrar publishes them, it does not approve them. The register therefore publishes your intended uses as soon as you declare them. Over-asking is controlled by the wallet, at presentation time, against your registration certificate (ARF v3.0.0, RPRC_21): a request beyond it is shown to the user with a warning.
How the register maps the regulation¶
| Requirement | Status in the sandbox |
|---|---|
| Information about the party and its services (Annex I, points 1โ6 and 11โ16) | Collected. Accuracy checks (Art. 6(3)(a)) are simulated: identity is declared, not verified. |
| Data requested and purposes (Annex I, points 7โ10) | Collected and published without approval (Art. 6(3a)). |
| Registration certificates issued automatically, without undue delay (Art. 8(1)) | Implemented. |
| Registration certificates only for registered parties; suspension and withdrawal reflected (Art. 8(2)(a)) | Implemented, through the status list. |
| One registration certificate per intended use (Art. 8(2)(b)) | Implemented. |
| Privacy policy for every intended use (Art. 8(2)(g)) | Implemented: required. |
| Intermediaries (Annex I, point 16) | Implemented: published as TS5 servedWRPServices, named in the client's WRPRC (act.sub). |
| WRPRC profile (Annex V) | Implemented: JWT and CWT, x5c, at most 12 months. |
| WRPAC content (Annex IV, 3(k)) | Partial: the register's reference is linked from the WRPRC (wrpac_binding.register_uri), not written in the WRPAC, pending ETSI guidance. |
| Register API (Annex II) | Implemented: public search without authentication, OpenAPI 3, signed answers, per-client rate limit, no physical address published. |
| Informing users of requests beyond registration (Art. 8(2)(d)) | A wallet obligation: see Test your registration. |
Sandbox choices¶
- Sandbox-generated keys. For convenience, the sandbox can generate your keys and keep a copy. A production registrar never holds subscriber keys: use your own keys to rehearse production.
- One trust scheme for everything. The register runs its own WRPAC CA, registrar signing certificate and trusted-list signer, all self-signed and published. None is a national or EU trust anchor.
- No identity checks yet. SIREN, address and domain are declared. Being registered does not prove an organisation's identity.
- Extensions. Register entries and registration certificates carry a few compatibility fields beyond TS5 and TS 119 475 (for example
serviceIdentifier,rpAccessCertificateSha256). Wallets should ignore what they do not know.
Policies¶
The register publishes its policies under /policies/: the register policy, the WRPAC certificate policy and practice statement, the WRPRC policy and practice statement, the trusted-list and LOTL policies, and the sandbox runtime policy. See Endpoints.