Relying party checklist: what you need to accept EUDI Wallets
A relying party is an organisation that asks a wallet for data – a shop that checks an age, a bank that opens an account. This checklist goes through what has to be in place, in the order you meet it. It is a practical overview, not legal advice; the rules are in Regulation (EU) 2024/1183 (eIDAS 2.0) and in Implementing Regulation (EU) 2025/848 on the registration of wallet-relying parties.
The checklist
- Decide what you really need. Write down each use case and the fewest attributes that serve it – “over 18” instead of a birth date, a city instead of an address.
- Register as a wallet-relying party with the registrar of the Member State where you are established. You state who you are, what you intend to ask for and why.
- Get your access certificate (WRPAC). It identifies you to the wallet, and you sign every request with its key. A wallet refuses a request whose certificate is on no trusted list.
- Get your registration certificate (WRPRC) where your Member State issues one. It lists the attributes you registered; send it with each request.
- Ask only for what you registered. CodeB Wallet compares the request with the registration certificate and warns the person when a request goes beyond it.
- Publish a privacy policy and a contact. Their addresses are part of your registration and are shown to the person in the wallet, together with the data-protection authority to complain to.
- Check what you receive: the issuer’s signature and its place on the trusted lists, validity and revocation status, and that the answer was made for your request (nonce and key binding).
- Keep only what you need, for as long as you need it. A yes/no answer needs no copy of the credential.
- Test before you go live – with test credentials and with more than one wallet.
What the person sees in CodeB Wallet
- Your name from the access certificate, marked as verified – or the request is blocked when the certificate is on no trusted list.
- Every item you ask for, one by one, before anything is shared.
- A warning when the request asks for more than your registration certificate lists.
- Share and Cancel. When the person cancels, you receive nothing.
Where CodeB helps
The CodeB EUDI Gateway takes the technical steps – signed requests, trust and revocation checks, the answer – and gives your application a normal OpenID Connect sign-in. Registration itself stays with you and your Member State.
Building it yourself? The OpenID4VP verifier guide has the request rules and DCQL examples. The use-case demos show the person’s side, including a request that asks for more than it is registered for.