01What the Regulation requires
Article 5b of the European Digital Identity framework requires a relying party that intends to rely on EUDI Wallets for public or private digital services to register in the Member State where it is established.
The registration includes information needed to authenticate the relying party, contact details and the intended use of the wallet, including an indication of the data to be requested from users. The Regulation also states that relying parties shall not request data beyond what they indicated during registration.
Registration becomes machine-readable trust information
The 2026 implementing framework strengthens the connection between registration and wallet behaviour. Registration certificates carry the intended use and data scope, and wallet software can warn users when a relying party asks for information outside that registered scope.
That makes registration metadata something verifier software has to understand and enforce, not a PDF that sits in an administration folder.
Why multi-tenant SaaS needs an RP model
A SaaS provider may have one technical product but many customer organisations that are each the service provider interacting with wallet users. Those organisations cannot simply be collapsed into one generic tenant label if their relying-party identities and permitted uses differ.
Adminyra therefore models relying parties as first-class records beneath the partner and application layer, with their own status, registration scope and certificate metadata.