eIDAS 2 Corrected: What Changes for Digital Identity Companies

Key data

If your company is adapting its processes to the European digital identity framework, this corrigendum requires you to review what you already had planned. Regulation (EU) 2024/1183, known as eIDAS 2, amended the original eIDAS regulation (910/2014) to establish the obligation for all Member States to offer the European Digital Identity Wallet to their citizens. Now, a corrigendum published on 7 April 2026 introduces corrections to that text that may change specific technical or legal provisions already in the process of implementation.

This is not a fundamental reform, but rather corrections of material or drafting errors. However, in technical regulation, a corrected drafting error can alter an integration requirement, a deadline or a key definition. Ignoring it could mean that your company is implementing an already superseded version of the regulation.

What does this regulation establish?

This corrigendum corrects Regulation (EU) 2024/1183, which is the regulation that transformed the European digital identity framework by amending the original eIDAS regulation (Regulation (EU) No 910/2014). The regulatory chain is as follows:

The central obligation established by eIDAS 2, which this corrigendum does not eliminate but rather clarifies, is that Member States must offer digital identity wallets (European Digital Identity Wallet) to their citizens. Companies operating in regulated sectors or that must verify the identity of their users are obliged to integrate these systems when required.

The published corrections may affect the technical or legal requirements that trust service providers and technology companies were implementing. Without access to the exact detail of each correction in the published text, it is not possible to specify which specific articles are modified: it is essential to consult the full text in the Official Journal of the EU.

Economic and operational impact

The impact of this corrigendum is not direct in the form of new specific fees or sanctions published in this text. The impact is operational and compliance-related: companies that were already investing in adapting their systems to eIDAS 2 must verify that their technical and legal developments remain compliant with the corrected text.

The main vectors of operational impact are:

• Review of ongoing integration projects: If your company was developing or contracting the integration of the European Digital Identity Wallet, technical requirements may have changed.
• Update of contracts with technology providers: Contracts that reference the eIDAS 2 text must verify whether the corrections affect the agreed obligations.
• Review of identity verification policies: Trust service providers must ensure that their verification procedures comply with the corrected text.
• Public administrations: Public bodies implementing the digital identity wallet must review whether the technical or legal requirements of their specifications or projects are affected.

Who does it affect?

According to the data in the regulation, the directly affected parties are:

• Technology companies that develop or integrate digital identity verification systems in their products or services.
• Trust service providers (electronic signature, digital certificates, authentication) regulated under the eIDAS framework.
• Digital identity providers that are developing solutions compatible with the European Digital Identity Wallet.
• Public administrations of Member States required to implement and offer the digital identity wallet to their citizens.
• Digital services sector companies that must integrate identity verification processes for EU citizens into their platforms.
• EU citizens, as end users of the European digital identity system.

Practical example

A Spanish digital financial services company has been developing since 2025 the integration of the European Digital Identity Wallet into its customer onboarding process, following the technical requirements of Regulation (EU) 2024/1183 (eIDAS 2).

With the publication of this corrigendum on 7 April 2026, the legal and technical team must do the following before continuing development:

1. Download the corrigendum text from the Official Journal of the EU and compare it with the version of eIDAS 2 they were using as a reference.
2. Identify whether any of the corrections affect the articles that regulate the technical requirements for integrating the digital wallet they were implementing.
3. If there are relevant changes, assess the impact on the development schedule and contracts with technology providers.
4. Update internal compliance documentation to reflect the corrected text as the current reference version.

This process, although it does not necessarily imply a complete redesign, may involve days or weeks of technical and legal review if the corrections affect key provisions of the integration process.

What should companies do now?

1. Download the corrigendum text from the Official Journal of the EU and compare it with the version of eIDAS 2 (Regulation (EU) 2024/1183) that was being used as an internal regulatory reference.
2. Identify which technical or legal provisions are corrected and assess whether any of them affect ongoing integration projects, contracts or internal policies.
3. Update compliance documentation to reflect the corrected text as the current version, replacing any reference to the previous version of eIDAS 2.
4. Review contracts with technology providers that reference the eIDAS 2 text, especially if they include compliance clauses linked to specific articles of the regulation.
5. Verify the entry into force date of the corrigendum by consulting the official text, as it is not specified in the publication and may affect adaptation timelines.