What digital financial companies must know and do from January 2025 onwards.
The digital transformation of the European financial sector has enabled efficiency, scalability, and innovative business models. It has also increased technological dependency and exposure to digital risks. In response, the European Union adopted Regulation (EU) 2022/2554, known as DORA (Digital Operational Resilience Act), which has applied since 17 January 2025.
DORA is not guidance and it is not a directive awaiting national transposition. It is an EU regulation directly applicable in all Member States, establishing a harmonised framework for digital operational resilience across the financial sector.
If you operate a fintech, a payment institution, an investment platform, or provide critical ICT services to financial entities in the EU, DORA may directly affect your operating model. It goes beyond cybersecurity controls and introduces structural obligations relating to ICT risk management, incident reporting, resilience testing, and third-party oversight.
This article explains what DORA is, who it applies to, and what compliance means in practice for fintech companies operating in the European Union.
What Is DORA and What Is Its Objective?
DORA is Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. It forms part of the EU Digital Finance Package and aims to ensure that financial entities can withstand, respond to, and recover from ICT-related incidents.
Unlike previous fragmented requirements, DORA harmonises ICT risk management obligations across the EU financial sector. It introduces common rules on governance, incident handling and reporting, operational resilience testing, information sharing, and oversight of critical ICT third-party providers.
Its objective is not limited to strengthening cybersecurity. It seeks to guarantee the continuity of essential financial services even in the event of cyberattacks, system failures, or major digital disruptions.
Who Does DORA Apply To?
DORA applies to a broad range of regulated financial entities in the EU. These include credit institutions, payment institutions, electronic money institutions, investment firms, fund managers, insurance and reinsurance undertakings, and certain crypto-asset service providers, among others.
It also affects ICT third-party service providers that deliver critical services to financial entities. Even if a technology provider is not itself regulated as a financial institution, it may fall indirectly within DORA’s scope if its clients are subject to the regulation and pass down contractual requirements.
For fintech companies, this means two possible scenarios.
First, direct applicability if the company is itself a regulated financial entity.
Second, indirect impact if the company acts as a critical ICT provider within the digital supply chain of a regulated financial institution.
In both cases, DORA introduces obligations that go beyond basic data protection or perimeter security measures. It requires structured, documented, and supervised digital risk management.
What Does DORA Compliance Require in Practice?
DORA is structured around five core pillars that define the compliance framework.
The first pillar is ICT risk management. Financial entities must establish a comprehensive internal framework that includes identification of critical assets, continuous risk assessment, appropriate safeguards, and clearly assigned responsibilities at management level. The management body retains ultimate accountability for digital operational resilience.
The second pillar concerns ICT-related incident management and reporting. Entities must implement formal processes to detect, classify, record, and report major ICT incidents to competent authorities within the prescribed timeframes. This requires structured escalation procedures and regulatory reporting capabilities.
The third pillar is digital operational resilience testing. Entities must conduct regular testing proportionate to their size and risk profile. Certain significant institutions will be required to carry out advanced threat-led penetration testing (TLPT).
The fourth pillar addresses ICT third-party risk management. DORA introduces minimum contractual requirements for outsourced ICT services and obliges entities to assess, monitor, and document risks arising from third-party providers, particularly those supporting critical or important functions.
The fifth pillar enables voluntary information-sharing arrangements on cyber threats, subject to safeguards, with the objective of strengthening collective sector resilience.
For fintech companies, the key point is that DORA requires evidence that these mechanisms are not merely documented but effectively implemented, regularly reviewed, and continuously improved.
What Documentation and Evidence Must You Be Able to Demonstrate?
DORA establishes enforceable obligations. Competent authorities may request documentary and operational evidence demonstrating effective compliance.
This includes the ICT risk management framework, inventories of critical assets, business continuity and recovery policies, incident registers, resilience testing reports, third-party risk assessments, and contracts incorporating DORA-compliant clauses.
Entities must also be able to demonstrate management involvement, clear allocation of responsibilities, and periodic review of their digital resilience framework.
In practice, if you cannot show traceability between identified risks, implemented measures, and documented controls, your supervisory position will be weak.
What Are the Risks of Non-Compliance?
As an EU regulation, DORA is directly applicable and supervised by national competent authorities, such as central banks or financial market authorities, depending on the entity type.
Authorities have powers to request information, conduct inspections, impose remedial measures, and apply administrative sanctions under the relevant sectoral frameworks. Beyond potential financial penalties, non-compliance may result in operational restrictions, reputational damage, and difficulties in maintaining or securing contracts with regulated financial institutions.
In an environment where digital resilience is a strategic requirement, inability to demonstrate DORA alignment can directly affect a fintech’s commercial viability.
Common Mistakes When Approaching DORA
A frequent misconception is that DORA only applies to large banks or insurance companies. Many regulated fintechs and technology providers integrated into financial supply chains fall within scope.
Another common mistake is treating DORA as a purely technical project. The regulation requires governance structures, management accountability, and supervisory traceability, not just cybersecurity tooling.
Third-party risk management is often underestimated. DORA significantly strengthens contractual and oversight obligations for ICT providers and requires active monitoring and documentation.
Finally, drafting policies without operational testing is insufficient. Digital operational resilience must be demonstrable through records, simulations, and documented testing activities.
How PrivaLex Supports Fintechs with DORA
At PrivaLex Partners, we support fintechs, payment institutions, and ICT providers operating within the European financial ecosystem in aligning with Regulation (EU) 2022/2554.
Our approach begins with a structured gap assessment against DORA requirements. From there, we assist in designing or strengthening ICT risk governance frameworks, reviewing third-party contracts, structuring incident reporting processes, and preparing proportionate resilience testing programmes.
We do not sell software solutions. We provide legal, regulatory, and strategic expertise to ensure that compliance is robust, proportionate, and defensible before supervisory authorities.
Frequently Asked Questions About DORA
When did DORA become applicable?
DORA has applied since 17 January 2025 across all EU Member States, without the need for national transposition.
Does DORA apply to all fintech companies?
It applies to fintechs that fall within the categories of regulated financial entities defined in the regulation. It may also indirectly affect technology providers delivering critical ICT services to regulated financial institutions.
Does DORA require incident reporting?
Yes. Financial entities must establish procedures to classify and report major ICT-related incidents to competent authorities within the timeframes specified in the regulation and its regulatory technical standards.
Is ISO 27001 sufficient to comply with DORA?
ISO 27001 can support structured ICT risk management and control implementation. However, it does not by itself cover all DORA-specific regulatory obligations, particularly in relation to supervisory reporting and third-party oversight requirements.
Next Step
Understanding what DORA requires is the first step. The next is objectively assessing whether your fintech is aligned with Regulation (EU) 2022/2554 and identifying any structural gaps before supervisory scrutiny.
If you would like to validate your preparedness or structure a proportionate DORA compliance roadmap, schedule a strategic session with PrivaLex.
Free webinar on 20 May: Get audit-ready for NIS2, ISO 27001 and ENS with PrivaLex & Factorial IT.
View webinar