Partner register โ Intermediaries¶
An intermediary queries the wallet on behalf of other registered organisations, its clients. It signs every request with its own access certificate and attaches the client's registration certificate, which names the intermediary. The wallet shows the user the client (who the data is for) and records the intermediary.
sequenceDiagram
participant C as Client (relying party)
participant R as Partner register
participant I as Intermediary
participant W as Wallet
I->>R: Register an intermediary service (access certificate)
I->>R: Publish prepared requests (optional)
C->>R: Register a verification service, choose the intermediary
R-->>C: No access certificate for the client's service
R-->>I: Client's registration certificate, naming the intermediary (act.sub)
I->>W: Request signed with the intermediary's WRPAC + client's WRPRC
W->>W: Checks that the WRPRC names the WRPAC holder as intermediary
W-->>I: Response, shown to the user as the client's request
Intermediaries exist for verification only. An issuer's trust rests on its own issuer address and signing chain, so the register offers no intermediaries to issuers.
For intermediaries: get started¶
Register an intermediary service¶
From the dashboard, click Declare a service, then Verify for other organisations.
- The service: the Service name and Service address of the platform that queries the wallet for your clients. The wallet shows your client's name and yours.
- The certificates: sandbox-generated, or from your CSR. See Certificates.
- Review: tick the confirmation and click Register the service.
Your organisation is declared an intermediary and its access certificate is issued. You declare no data for yourself. You land on the Intermediary page; the .p12 file is on the service's Certificates tab.
Already have a verification service? Under your services on the dashboard, Declare yourself an intermediary opens the Intermediary page: Act as an intermediary turns your organisation into one, with your existing access certificate.
Prepare requests for your clients¶
On the Intermediary page, under Requests prepared for your clients, click Prepare a request.

- Request name, as your clients will see it, for example Identity of the customer.
- Attestations and data: the same editor as for an intended use.
- Suggested purpose: shown to the user once your client takes the request.
- Save the request.
A prepared request belongs to your organisation, not to a service: one platform can serve all your clients. You can prepare up to 20. Each save creates a new Version; clients who took an earlier one keep it and are told a new one is available. Delete removes it for new clients only.
Prepared requests are public: they appear in your entry of the register (requestTemplates), so a client in another Member State or using the API can read them too.
Your clients¶

Your clients' services lists the services that chose you, with their purpose and since when. A client chooses you without any approval on your side. For each:
- Registration certificate (.jwt) downloads the client's WRPRC that names you: attach it to every request you send for that client.
- End stops acting for the client. The registration certificate naming you is revoked, and wallets refuse your requests for that service.
Your dashboard also shows Your clients' services. Stop acting as an intermediary is available once no client remains.
Present a request for a client¶
- Sign the request (for example an OpenID4VP request object) with your access certificate's key, your certificate in
x5c. - Attach the client's registration certificate, the one for the intended use you request, in
verifier_info. - Request only the data that registration certificate lists.
The wallet checks that the registration certificate names your organisation (act.sub and intermediary.sub equal the organizationIdentifier of your access certificate), shows the client to the user, and records you as intermediary. See Use your certificates.
Automate it¶
Everything above is available through the intermediary API (Automate with the API on the Intermediary page):
- find your clients:
GET /wrp?usesIntermediary=<your identifier>; - fetch every registration certificate to attach:
GET /api/registry/registration-certificates?accessCertificateSha256=<your WRPAC SHA-256>returns yours and your clients', markedonBehalfOf; - manage prepared requests and associations.
See APIs and automation.
For clients: use an intermediary¶
At registration¶
When you register a verification service, the step Who sends requests to the wallet? offers A registered intermediary. Choose it under Registered intermediary.
- Your service gets no access certificate: the intermediary's is the one presented to the wallet.
- If the intermediary has several services, choose under Intermediary's service the one whose access certificate presents your requests. With a single service, it is chosen for you. The summary shows Requests presented by intermediary, service.
- If the intermediary published prepared requests, Choose a request prepared by it. The data and purpose are copied into your intended use: untick what you do not need, adapt the purpose. You cannot add data to a prepared request; choose Define my own request for that. Define my own request is always available.
- Your registration certificate names the intermediary and is issued straight away.


After registration there is nothing for you to install: the intermediary picks up your registration certificate from its space or the register.
After registration¶
On the service's Data tab, each intended use shows who presents it:

- From "request", prepared by intermediary: where its data came from. When the intermediary publishes a newer version, See the new version opens it in the editor; your intended use keeps its version until you publish.
- Presented to wallets by the intermediary X, since date with Stop using this intermediary. The registration certificate naming it is revoked. If your service has its own access certificate, a new registration certificate is issued for it; otherwise the intended use is no longer presented until you choose another intermediary or get an access certificate.
- Use an intermediary: choose one for an intended use your service presented itself, and its service when it has several.
Each intended use has at most one intermediary at a time. To present requests yourself as well, get your own access certificate from the Certificates tab with Get an access certificate.
What ends an association¶
An association ends, and the registration certificate naming the intermediary is revoked, when:
- either party clicks End or Stop using this intermediary;
- the client withdraws the service or the intended use;
- either organisation is withdrawn.
An intended use that nobody presents (no access certificate of its own, no intermediary) has no valid registration certificate.