A report circulating in digital-identity trackers says Estonia's cabinet approved, on 1 October 2026, a bill requiring any EU Digital Identity Wallet offered in Estonia to hold EU certification and a licence from the Information System Authority (RIA). We could not confirm that date. We found nothing in ERR, the Riigikogu site or RIA's pages about a cabinet approval, and the government's draft-legislation portal refused automated access. What we can verify is the draft itself: a Justice and Digital Affairs Ministry explanatory memo dated 27 July 2026 for a bill amending the Electronic Identification and Trust Services Act, the State Fees Act and the Penal Code. This analysis covers that draft and treats the approval date as unconfirmed.
What the draft does
The memo says the bill's purpose is to align Estonian law with the revised eIDAS Regulation, Regulation (EU) 2024/1183, which established the European Digital Identity Framework. The memo's central design choices are these:
- RIA becomes the main competent authority, handling supervision, licensing, the register, notification and other state-level tasks.
- A new register of relying parties is created. The EU regulation requires such a register for parties that rely on wallets.
- A wallet provider needs a licence, issued through a procedure modelled on the one for qualified trust service providers. The licence rests on EU certification, and its validity follows the certificate's validity, which the memo gives as up to five years.
- Fines are capped at EUR 5 million or 1% of a company's prior-year global turnover, whichever is higher. The memo says authorities must set the amount proportionately to the Estonian context.
- The required liability insurance for qualified trust service providers rises from EUR 1 million to EUR 2 million.
The pages we read (1 to 12 of 26) match the reported licence-plus-certification requirement. We did not find in them whether the licence requirement distinguishes public from private providers, so we do not claim that.
The strongest case for the licence
The case for licensing is a good one. A wallet holds identity credentials and may eventually carry payment, health and signature functions. A badly secured or fraudulent wallet harms people who cannot easily assess it. The memo says a licence lets RIA verify compliance before a provider starts, and that it can bar a provider that does not meet the requirements. It explains the rationale as ensuring that only a provider meeting the requirements offers a service on which identity and personal-data processing depend. That is the same logic Estonia has long applied to qualified trust services, and the country's e-state depends on public trust in those services.
The design is also less restrictive than it might have been. The licence does not require a provider to prove national uniqueness or build a bespoke Estonian standard. The memo says it deliberately avoids duplicating EU implementing acts and that the licence tracks the EU certification, with only supervision and sanctions left to national law.
Where proportionality needs guarding
The risk is not the existence of a licence. It is licensing becoming a second, slower gate on top of EU certification. Three points deserve attention.
Certification should be the substance, the licence the formality. The EU framework already requires certification against common standards. If RIA treats licensing as an independent merits review, a provider certified elsewhere in the EU could face duplicate delay. The memo's text points the other way, tying the licence's life to the certificate. The ministry should keep that tie in the final text and in practice.
Market contestability matters more than the wallet itself. The state wallet is the centrepiece. RIA's own page says public-sector services must accept EUDI wallets from the end of 2026 and certain regulated or influential private-sector services from the end of 2027. A licensing regime that is fast and predictable lets private wallet providers compete on usability. One that is slow cements the state wallet by default. Citizens and banks would benefit from choice, particularly for services that go beyond Estonia's existing eID.
Open-source obligations should not become a barrier. The memo says the EU regulation requires wallet components' source code to be open-source licensed, with member states able to specify exceptions. It carries that requirement into Estonian law. Open code helps security review and trust, but commercial providers need clear guidance on what must be disclosed.
The state wallet is still unbuilt
The regulator will license wallets before the national wallet exists. RIA announced an international tender on 18 May 2026, and Biometric Update reported a EUR 21.65 million procurement covering development and five years of operation, run by competitive dialogue. RIA's page says that, absent disputes, concluding the contract could take about a year. We found no public award. The state is therefore writing the rules for a market in which it is not yet a participant, which is a reason for even-handed rules: RIA should not be able to license itself more lightly than it licenses others.
What to watch
Two things will decide whether this bill is a model or a drag. First, whether the final text keeps licence validity tied to EU certification and avoids requiring a separate review. Second, whether RIA publishes licensing timelines and criteria, so that applicants know what is required before applying. The memo promises proportionality in fines and says the bill needs a majority in the Riigikogu. Both can be tested in debate. The draft is a defensible application of EU law. Its quality depends on how narrowly RIA uses the gate it is being given.