Skip to main content

Register as a Wallet-Relying Party

Registering as a wallet-relying party gets your service onto the iGrant.io recognised Trust List, so the Data Wallet shows a verified badge for your organisation instead of the "Service provider not verified" warning. This guide covers the test network, where the recognised Trust List is operated by iGrant.io for development and piloting.

Test network scope: This is a test-network onboarding for developing and piloting against the Data Wallet. It mirrors the wallet-relying party registration pattern from eIDAS, but it is not the legal registration with a Member State national register. The recognised Trust List used here is operated as a test network by iGrant.io. Use it to make your service trusted during development, then follow your national register's process for production.

Background: What a wallet-relying party is​

Under eIDAS, a relying party that wants to request credentials from EU Digital Identity Wallets registers as a wallet-relying party. Commission Implementing Regulation (EU) 2025/848 defines it as:

"'wallet-relying party' means a relying party that intends to rely upon wallet units for the provision of public or private services by means of digital interaction"

In production this registration is with a national register operated by a Member State registrar, providing the information in Annex I of the regulation. The test network mirrors that pattern so your service can be recognised during development.

Step 1: Prepare your certificate​

To register you need an X.509 certificate. Which certificate depends on the actor you register as:

ActorCertificate to provide
Wallet ProviderTrust anchor (root CA): the CA certificate your wallet unit attestation signing certificates chain to
PID IssuerTrust anchor (root CA): the CA certificate your PID credential signing certificates chain to
EBWOID IssuerTrust anchor (root CA): the CA certificate your EBWOID credential signing certificates chain to
QEAA IssuerTrust anchor (root CA): the CA certificate your QEAA credential signing certificates chain to
EAA IssuerTrust anchor (root CA): the CA certificate your EAA credential signing certificates chain to
Relying PartyAccess certificate (WRPAC): the end-entity certificate you authenticate with when requesting credentials from wallets

For issuers and wallet providers, the trust list carries your root CA as the trust anchor: wallets validate the credentials you issue by chaining the credential signing certificate up to it. For relying parties, the trust list carries your access certificate, so wallets can recognise you when you request credentials.

You can provide your own certificate, or generate a test one with the Certificate Generator:

  • Open the Certificate Generator, fill in your organisation details, choose the service type, and provide your CSR.
  • It generates the right certificate profile for your service type (root CA for issuers and wallet providers, access certificate for relying parties) and a trust-list entry in JSON with the certificate embedded. Copy the entry into the form in Step 2.

Using the Certificate Generator is optional. If you already have a suitable certificate, use that.

Subject to verification: Everything you submit is reviewed and verified by iGrant.io before your service is added to the recognised Trust List. If you use the Certificate Generator, note that it produces a self-signed test certificate. Please ensure the data you enter is real and aligned with your official records.

Step 2: Submit your registration request​

Fill in the form below and choose Submit registration request. This opens your email client with the request, including your certificate and trust-list entry, pre-filled to [email protected]; review it and send. After verification, the iGrant.io team adds your entry to the recognised Trust List for you.

Your details Fill in your organisation details

Email preview

Opens in your email client, addressed to [email protected]
Subject: Trust List registration request (Relying Party): (organisation)
Please register this service on the iGrant.io recognised Trust List (test network).

Contact name: 
Organisation (legal name): 
Registration number: 
Country: 
Address: 
Contact email: 
Service type: Relying Party
Certificate type: Wallet-relying party access certificate (WRPAC)

Certificate and trust-list entry:

Your certificate and entry are included in the email, so there is nothing to attach. If your email client shortens long messages, attach them as a file instead.

Note: For the test network, iGrant.io handles the trust-list update on your behalf, so there is no pull request for you to raise. Self-service submission is planned for a later release.

Step 3: Confirm you are recognised​

Once iGrant.io has added your entry and the Data Wallet has refreshed its trust lists, your organisation is matched against the recognised Trust List. Users then see the verified badge for your service instead of the "Service provider not verified" popup.