EU identity wallet launch by country: the EUDI Wallet tracker
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.
The European Digital Identity Wallet (EUDI Wallet), established under eIDAS 2, requires EU Member States to provide at least one certified digital identity wallet by 24 December 2026, although national rollout progress varies substantially. As of 5 October 2026, Italy’s IT-Wallet and Denmark’s AltID are among the most developed public applications, France Identité has exceeded five million users, and Germany plans to launch its d-you wallet on 2 January 2027, while many countries remain in pilot, sandbox, planning, or undeclared stages. From 24 December 2027, regulated private-sector organizations that require strong online authentication, including those in banking, transport, energy, health, and telecommunications, must accept a wallet when users voluntarily request it, though micro and small businesses are exempt. Wallets are intended to let users selectively share verified identity data and other credentials, with remote presentations using standards such as OpenID4VP and ISO/IEC 18013-7. Certification requires conformity and cybersecurity assessments, with certified wallets to be listed by the European Commission, and businesses are advised to retain national eID and document-based alternatives because availability and certification will remain uneven during the transition.
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.