How do organisations register as a wallet-relying party?

An organisation registers as a wallet-relying party with the registrar of the member state where it is established (Art. 5b(1) eIDAS). It provides company data, identifiers such as a business register number, VAT number or LEI and, for each intended use, the data requested and the purpose. After successful registration it receives its access certificate, which it needs for every wallet request, and a registration certificate.

The EU framework is fixed: Implementing Regulation (EU) 2025/848 applies from 24 December 2026 (Art. 11) and was amended by Implementing Regulation (EU) 2026/1730. National implementation is not. As of 12 October 2026, several member states have not formally designated a registrar, and most registration portals are not yet open. This page is general information, not legal advice.

The EU framework in brief

• One registration, in the member state of establishment. Each member state keeps at least one national register and designates at least one registrar (Art. 3 of Regulation 2025/848). Registrars check that the relying party is not already registered in another national register (Art. 6(3)(d)).
• Published registration policy. Each member state publishes the rules of its registration procedure, including the supporting documents required (Art. 4).
• Simple, verified procedures. Registrars set up easy, electronic and, where possible, automated procedures, verify the identity and company information and reject registrations they cannot verify (Art. 6).
• Transparency rather than pre-approval. Contact details, service description, requested data and the description of the intended use are collected for transparency only, with no pre-authorisation process, without prejudice to sector-specific law (Art. 6(3a), inserted by Regulation 2026/1730; Art. 5b(4) eIDAS).
• Public registers with a common API. From 24 December 2026, each register is published in human- and machine-readable form through a common REST API and a national website, signed by or on behalf of the registrar (Art. 3, Annex II).
• Suspension and cancellation. Registrations can be suspended or cancelled, for example for inaccurate information or for requesting more attributes than registered; the certificates are then revoked (Art. 9).
• Retention. Registrars keep the registration records for ten years (Art. 10).

Who the registrar is, by country

The Commission will publish a signed, machine-readable list of all registrars and registers, based on member states’ notifications (Art. 5(1) of Implementing Regulation (EU) 2024/2980). The eIDAS dashboard announces this list, but as of 12 October 2026 it has not been published. Until then, the national designations below are the best available indication.

We will update this table when the Commission list is published. The status of each country’s wallet is tracked in the EUDI index.

What information is registered

Annex I of Regulation 2025/848 sets out what goes into the register. TS6 translates it into a common data set. It includes:

• official name and a user-friendly trade name
• identifiers such as business register number, VAT number, EORI or LEI (TS5 uses the EUID as default identifier where available)
• address, website and contact details
• a description of the services offered
• for each intended use: which data are requested and for what purpose
• whether the organisation is a public sector body
• entitlements, such as acting as a service provider (Service_Provider) or as a provider of person identification data (PID_Provider)
• whether an intermediary is used, and which one

Most of this becomes publicly visible. The API responses contain the Annex I information except the item the regulation refers to as “the contact information in Annex I point 4”; point 4 is the physical address of establishment (Annex II). Anyone can check which organisation requests which data and why.

Registration in seven steps

1. Define intended uses. For each process, decide which data are strictly needed. Less is better: you may only request what you have registered (Art. 5b(3) eIDAS).
2. Identify the competent registrar. Use the table above and the national authority’s website and registration policy.
3. Gather the information. Register data, identifiers, contact, service description, intermediary details.
4. Test the integration. Some member states offer sandboxes; Germany, for example, makes sandbox participation a precondition for production use. The Commission also runs a public test registry for its reference implementation.
5. Apply for registration. The registrar verifies your identity and company data and rejects what it cannot verify (Art. 6). Where applicable, it also checks the power of attorney of representatives under national law (Art. 6(3)(b)).
6. Obtain certificates. You then receive the access certificate and a registration certificate showing your registered data per intended use. Since Regulation 2026/1730, every member state must provide registration certificates, issued automatically and without undue delay after registration (Art. 8(1)).
7. Report changes. New purposes or company changes must be reported without delay (Art. 5b(6) eIDAS, Art. 5(3) of Regulation 2025/848).

Intermediaries

If a technical service provider connects the wallet for you, it is itself a relying party (Art. 5b(10) eIDAS) and must not store data about the content of the transaction. Your registration states whether you use an intermediary and which one (Annex I points 14 and 15). Whether a service provider may also file the registration on your behalf, as an authorised representative, depends on national law and the national registration policy; the regulation only provides that registrars check powers of attorney where applicable (Art. 6(3)(b)).

Costs and effort

Fees are set nationally; the regulation only requires a cost-effective, risk-proportionate procedure (Art. 5b(2) eIDAS). We have not found published fees for any member state.

As one indication of internal effort, the German draft law estimates about 40 hours (around EUR 2,300) for a first registration in the launch phase and about 32 hours (around EUR 1,850) later. It expects around 4,200 registrations in Germany in the launch phase and around 550 per year after that, and calls this a model estimate. Figures for other member states are not available to us.

For developers

The register API is specified in TS5 (version 1.5 of 20 August 2026, aligned with Regulation 2026/1730, with an OpenAPI description). GET /wrp returns the full list of registered relying parties as a signed JWS, with cursor-based pagination. Each intended use lists credential formats (dc+sd-jwt, mso_mdoc) and the claim paths requested. The data model changed several times in 2026, so expect further revisions.

Preparation tips

• Plan for data minimisation. Every intended use is public. Requests that ask for more than needed will be noticed by customers, consumer groups and supervisors.
• Check whether you must accept the wallet. See Mandatory acceptance and the Small business exemption.
• Assign responsibilities for registration, certificates and change notifications.
• Involve data protection. Purposes and data scope should match your records of processing activities under the GDPR.

Still unclear

• When the Commission’s registrar list will be published
• When national portals open and how long verification takes
• Whether fees apply, and how much
• How often access certificates must be renewed

Dates are tracked in the deadlines overview.