Regulation (EU) 2024/1183 amended the eIDAS framework and established the European Digital Identity Wallet framework. For software providers, the important question is how existing services will connect to wallets as relying parties.
The amended framework establishes interoperable European Digital Identity Wallets and sets requirements around wallet providers, issuers, relying parties, certification and trust.
For service providers, the practical impact is a common wallet channel through which users can present identity data and electronic attestations for public and private services.
Member States are required to provide wallets by the end of 2026. Waiting for mass consumer adoption before designing the integration leaves little time to understand registration, attribute minimisation and sector-specific requirements.
A sandbox-first project lets product teams identify where wallet verification fits into onboarding, login, checkout or access-control flows before production certificates and trust infrastructure are involved.
Adminyra is building the relying-party integration layer, not a competing citizen wallet. The service is intended to provide a stable API, multi-tenant control plane and verifier orchestration for software platforms and individual relying parties.
The goal is to make EUDI an application feature instead of a separate identity infrastructure project for every SaaS customer.
Yes. Regulation (EU) 2024/1183 entered into force in May 2024 and the associated implementing framework has continued to develop since then.
The European Commission states that Member States are required to provide EU Digital Identity Wallets by the end of 2026.
No. Acceptance duties depend on the type of service and the applicable legal conditions. Businesses should assess their own relying-party role and timeline rather than assuming a universal immediate obligation.
Model the relying party, define the minimum data request and integrate the application flow before production trust infrastructure is required.