Under the European Digital Identity framework, a service provider that relies on information presented from an EU Digital Identity Wallet has specific technical and registration responsibilities.
The Regulation requires a relying party that intends to rely on EUDI Wallets for digital services to register in the Member State where it is established. Registration includes information about the relying party and its intended wallet use.
The relying party must also indicate the data it intends to request. The Regulation states that relying parties shall not request users to provide data beyond what was indicated in that registration.
A complete rollout combines registration, authentication of the relying party, verifier infrastructure, trusted issuer validation, privacy controls and the business workflow that consumes the verified result.
Adminyra is designing the control plane around those separate concepts instead of reducing everything to a single API key.
A vertical SaaS company may have many end customers that are each the actual service provider. Those businesses can need their own relying-party records and policies even though they all use the same SaaS platform.
That multi-tenant model is the primary use case Adminyra EUDI is being built for.
In practical verifier terms, it is the service provider that requests and relies on attributes presented by a wallet user, subject to the user's approval and applicable law.
The European Digital Identity Regulation requires wallet-relying parties providing digital services to register in the Member State where they are established.
A platform can provide technical integration for multiple organisations, but each organisation's legal role, registration and permitted data requests must still be modelled correctly.
Model the relying party, define the minimum data request and integrate the application flow before production trust infrastructure is required.