An intermediary is an organisation that interacts with wallets on behalf of one or more relying parties, requesting and receiving user attributes for them. eIDAS 2.0 treats an intermediary as a relying party and forbids it from storing data about the content of the transaction.
Legal termReviewed 7 October 2026
On the relying party side, where data is requested and checked.
Issuer
Signs credentials: a member state, university, bank or employer
Issuance
EUDI Wallet
Belongs to the user, who decides what to share
Presentation
Relying party
The service that requests and checks the data
Trust layer: who is allowed to sign, and is it still valid?
Rules: the law and technical framework behind it all
Most businesses will not run their own wallet connector. An intermediary handles the protocol work, the wallet interaction and the trust and revocation checks, then passes the result to the relying party it serves.
Article 5b(10) sets two conditions. An intermediary acting on behalf of a relying party is deemed to be a relying party itself, so registration and data minimisation duties apply to it as well. And it may not store data about the content of the transactions it handles.
The details, such as how intermediaries register and how the relying party they act for is shown to the user, sit in the implementing acts and the ARF, and member state registration processes are still being set up.
Defined in
Regulation (EU) 2024/1183 Art. 5b(10); ARF Annex 1
If you use a provider to connect to wallets, ask how it meets the Article 5b(10) duties, including what it stores. Your own relying party obligations do not go away when someone else runs the technology.
Read next: EUDI Wallet integration guide →
Authbound handles the protocols, formats, trust lists and revocation checks behind these terms. See what people build with them.
