EUDI Wallet relying party: registration, certificates and duties
Blog post from Didit
Excluded from normalized aggregate trends after staff review: 3056 posts were attributed to March 2026; 671 shared March 14, 2026. The preceding six-month median was 13.5 posts.
Review evidence: 3,056 posts in March 2026; 671 shared March 14, 2026; preceding six-month median 13.5. Reviewed August 9, 2026.
This company's pages remain public, but its content is excluded from normalized aggregate trends. Unfiltered raw trends and advanced filtering are available to Accelerate and Lead accounts.
An EUDI Wallet relying party is a public or private organization that requests data from a European Digital Identity Wallet to provide digital services and must register in the EU Member State where it is established, declare each intended use and requested attributes, and receive an access certificate to authenticate itself to wallets. Under eIDAS 2, Member States must make wallets available by 24 December 2026, while private organizations legally or contractually required to use strong user authentication, except micro and small enterprises, must accept wallets at a user’s request by 24 December 2027; public-sector requirements depend on national rules. Relying parties may request only registered data, must identify themselves to users, validate identity credentials through signature, revocation, and device-binding checks, preserve alternative access methods, and accept pseudonyms where identification is not legally necessary. Access certificates are mandatory, while registration certificates depend on national implementation and wallet checks of these certificates begin on 11 August 2028. The framework supports OpenID4VP and ISO/IEC mdoc presentation methods, emphasizes selective disclosure and data minimization, and notes that some information, such as tax numbers or optionally issued address and portrait data, may require separate verification routes.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.