DORA for FinTechs: What the EU Resilience Rules Require
DORA has applied to EU financial entities since January 2025, setting hard deadlines for incident reporting, testing and vendor oversight. What it means in practice.
Key takeaways
- DORA (Regulation (EU) 2022/2554) applies since 17 January 2025 to around twenty categories of EU financial entity, from banks and payment institutions to crypto-asset service providers.
- A major ICT incident must be reported within four hours of classification and no later than 24 hours after detection, with an intermediate report at 72 hours and a final report one month later.
- Financial entities must keep a register of every ICT contractual arrangement; the first EU-wide list of 19 critical ICT third-party providers was published in November 2025.
- Vendors are mostly bound through Article 30 contract terms — but designated critical providers face direct ESA oversight, including penalty payments of up to 1% of daily worldwide turnover.
A single rulebook for digital risk in EU finance
DORA — the Digital Operational Resilience Act, formally Regulation (EU) 2022/2554 — entered into force on 16 January 2023 and has applied since 17 January 2025. Its purpose is straightforward to state and difficult to deliver: make the EU financial sector able to withstand, respond to and recover from ICT disruption, and stop leaks and downtime from turning into systemic events.
Before DORA, digital resilience expectations were spread across supervisory guidelines and national rules. A payment institution operating in five member states could face five overlapping sets of cyber, outsourcing and reporting requirements. DORA replaced that with a single directly applicable regulation. National supervisors still set penalties and supervise day to day, but the substantive requirements are the same text everywhere in the EU.
The practical effect for compliance officers, product managers and founders is a shift from "we have a security policy" to "we can evidence a governed, tested and contracted resilience capability within fixed clocks."
Who is actually in scope
The regulation's scope list runs to around twenty categories of financial entity, set out in Article 2 of the official summary on EUR-Lex. In practice the ones most relevant to the FinTech sector are:
- credit institutions
- payment institutions and electronic money institutions
- investment firms, fund managers and account information service providers
- crypto-asset service providers, which sit in scope alongside the MiCA framework covered in our piece on EU and US reserve rules
- crowdfunding service providers and credit rating agencies
- insurers, insurance intermediaries and occupational pension institutions
- market infrastructure: central securities depositories, central counterparties, trading venues, trade repositories and securitisation repositories
Two categories of firm are often confused. A FinTech that holds a licence from a national authority is a financial entity and must comply with DORA itself. A software vendor selling to that FinTech is an ICT third-party service provider: not directly regulated, but pulled into the framework through the contracts its clients must sign under Article 30. The only providers that escape that indirect route are those the European Supervisory Authorities (ESAs — EBA, EIOPA and ESMA) later designate as critical.
DORA is EU law. Firms licensed outside the EU are not caught by it directly, and the ESAs cooperate with non-EU authorities through memoranda of understanding rather than by licensing vendors. The binding mechanism for a UK or US provider is commercial: the DORA clauses its EU clients are required to include in their contracts. The same pattern shows up in other EU rules, as in open banking under PSD2 and PSD3.
The five obligations that matter
1. ICT risk management (Articles 5 to 16)
This is the foundation chapter, and it is board-level. The management body must define, approve, oversee and take responsibility for the ICT risk management framework, and the framework itself must be documented with strategies, policies, procedures and tools. Concretely, entities must maintain a current inventory of ICT-supported business functions and their dependencies, classify the risk attached to each, review that classification at least annually, run a business continuity policy with backup, restoration and recovery procedures, and prepare a crisis communication plan.
Proportionality is built in. Microenterprises are exempt from the core risk management provisions, and a simplified framework applies to a defined set of smaller entities, including small and non-interconnected investment firms and certain payment and e-money institutions. The register of information described below, however, applies to every entity in scope — the ESAs have confirmed there is no carve-out.
2. Incident classification and reporting (Articles 17 to 23)
Classification comes before notification. An incident is major only if it affects services that are critical under Article 6 of Commission Delegated Regulation (EU) 2024/1772 and then meets one of two further conditions: either a successful, malicious and unauthorised access occurred that may cause data losses, or two or more materiality thresholds are breached. Those thresholds include more than 10% of the clients of the affected service or more than 100,000 clients, more than 30% of financial counterparts, more than 10% of the daily average number or value of transactions, impact in two or more member states, and an incident duration above 24 hours or downtime of critical-function ICT beyond two hours.
Once classified as major, the clock runs. The deadlines sit in Article 5 of Commission Delegated Regulation (EU) 2025/301:
| Report | Deadline |
|---|---|
| Initial notification | As early as possible, within 4 hours of classifying the incident as major, and no later than 24 hours after the entity became aware of it |
| Intermediate report | Within 72 hours of the initial notification, even if the status has not changed |
| Final report | Within one month of the intermediate report, or of the latest updated intermediate report |
Two details catch firms out. First, the four-hour clock runs from classification, not discovery, so the timestamped classification record is the first document a supervisor will ask for. Second, where a deadline falls on a weekend or public holiday, submission may be deferred to noon on the next working day — but credit institutions, central counterparties, trading venue operators and entities identified as essential or important under the NIS2 directive cannot use that extension for the initial notification or the intermediate report.
3. Digital operational resilience testing (Articles 24 to 27)
Entities outside the simplified framework must run a testing programme proportionate to their risk profile, covering vulnerability assessments, network security reviews, physical security reviews and scenario-based crisis simulations. Every three years, threat-led penetration testing (TLPT) is required, carried out against live production systems by testers who are certified, suitably experienced and hold professional indemnity insurance. The critical question for most firms is not whether to test but who signs off that the test covered the right systems.
4. ICT third-party risk and the register of information (Articles 28 to 30)
Outsourcing does not transfer responsibility. The financial entity remains accountable for compliance, must carry out due diligence before contracting, and must manage concentration risk and substitutability for services supporting critical or important functions, including written exit strategies.
Article 28(3) requires a register of information covering every contractual arrangement for ICT services, built on the standard templates of Commission Implementing Regulation (EU) 2024/2956. It must be kept at entity level and, for groups, at sub-consolidated and consolidated level, and reported to the competent authority at least annually. For the first EU-wide collection the reference date was 31 March 2025, with national authorities forwarding the data to the ESAs by 30 April, as set out in the EBA's register FAQ. Subcontractor chains supporting critical or important functions must be recorded, which is where most first drafts were found wanting.
Article 30 then fixes what contracts must contain: a clear description of the service and the functions supported, locations of data processing and storage, data protection and availability commitments, service levels, assistance during incidents, cooperation with supervisors, rights of access and audit, notice periods and termination rights, conditions for subcontracting, and exit arrangements that include the return of data.
5. Oversight of critical ICT providers (Articles 31 to 44)
Since 18 November 2025, the ESAs have designated a first list of 19 critical ICT third-party providers, published in full on ESMA's site. The list is dominated by cloud infrastructure, data vendors, IT services integrators, telecoms and colocation providers — a reminder that concentration risk can sit several layers below the contract a firm signs. Designation follows the two-step quantitative and qualitative assessment in Delegated Regulation (EU) 2024/1502, and providers not designated may ask to be assessed through the opt-in route in Article 31(11).
Designated providers come under a lead overseer drawn from the ESAs, which can request information, conduct investigations and inspections, and issue recommendations with follow-up reports. Periodic penalty payments of up to 1% of a provider's average daily worldwide turnover in the preceding business year can be imposed, accrue daily and run for no more than six months after at least 30 calendar days' notice of the required measures. Oversight is funded by fees charged to the designated providers themselves, per the ESAs' oversight guide. In a serious and persistent case, national authorities can ultimately require financial entities to suspend or phase out the affected service.
What it means for SaaS and ICT providers
If you sell software or infrastructure into EU financial services, DORA is already in your pipeline, whether or not you are on the designation list.
- Contract renewals are the pressure point. The Article 30 clauses come to you through your customers, not from a regulator. Audit and access rights, data location commitments, subcontracting notification and exit assistance are the provisions buyers cannot waive.
- Evidence beats certification. An ISO 27001 certificate or a SOC 2 report is useful but does not by itself answer DORA questions about exit support, data return, subcontractor chains or cooperation with authorities.
- Incident support matters. Your clients carry four-hour and 72-hour clocks. If you cannot supply incident facts quickly, you are transferring regulatory risk to your customers.
- Designation is not an award. A place on the critical list brings direct supervision, examinations and oversight fees.
- Enterprise sales cycles lengthen. Expect security and resilience reviews, contractual renegotiation and questions on substitutability before signature.
Where FinTechs stumble in practice
The failures are operational, not conceptual. Firms build the register once for the first submission and then let it drift as contracts change. Intra-group ICT arrangements and deep subcontractor chains get omitted. Classification decisions are made in the moment without a written record, so the four-hour clock starts without anyone being able to prove when. Contract templates with large vendors can take six to twelve months to renegotiate, which is why exit strategies for critical functions are often the last item finished and the first one a supervisor asks about. Payment firms also have to reconcile DORA reporting with their existing incident duties under the payment services framework, and a single event can trigger more than one notification.
Risks and costs
Nothing in DORA is free, and the costs are rarely one-off.
- Direct compliance costs: testing and TLPT with certified, insured testers; legal work to renegotiate vendor contracts; tooling and staff to keep the register current; and a reporting capability that can operate outside business hours, because major incidents do not respect a 4x5 rota.
- Oversight fees: designated critical providers fund the ESAs' oversight through fees, a cost that in a competitive market tends to reappear in pricing.
- Architecture costs: reducing concentration risk means multi-vendor and multi-region designs, which raise run costs and complexity even when they lower resilience risk.
- Enforcement exposure: for financial entities, penalties are set at national level and therefore differ by member state; for designated providers, periodic penalty payments can reach 1% of average daily worldwide turnover and last up to six months.
- Interpretation risk: under-reporting invites supervisory scrutiny, while reflexive over-reporting creates noise and reputational exposure, since penalties are published.
- Dependency risk: in some niches there may be no DORA-ready alternative, and switching costs in the short term can outweigh the theoretical benefit of substitution.
This is an explanatory overview, not advice. The detailed requirements sit in the regulation and its technical standards, and supervisory expectations are still developing through guidelines and published Q&As, so entities should confirm their position with their own competent authority and counsel.
Bottom line
DORA converted digital resilience from a national expectation into a single EU compliance discipline with hard clocks, a documented vendor inventory and a public oversight register. Licensed banks, payment firms, investment firms and crypto-asset service providers must show governed risk management, tested continuity, a current register of ICT arrangements and evidence-based incident reporting. Vendors that are not designated are still bound in practice, because the Article 30 terms land in every renewal. The 19 providers on the critical list now answer directly to the ESAs. For most teams, the recurring work is what defines success: an annual reporting cycle, triennial testing, contract terms that only tighten, and a classification decision that has to be right when the clock is already running.
Follow the shortlist
Following payments, banking and market-infrastructure change? Our global ETF and stock research watchlist is tracked daily. Premium members get the full list, the reasoning behind every entry and updates when entries change.
See premium accessInformation and education only, not investment advice.
Related
Stablecoin Regulation Compared: EU MiCA vs the US GENIUS Act
How MiCA and the GENIUS Act differ on who may issue payment stablecoins, what must back them, how redemption works and where depeg risk still sits.
FinTechTokenised Deposits vs Stablecoins: How Bank-Issued Money Differs
Tokenised bank deposits and reserve-backed stablecoins both move value on programmable rails, but they differ in legal claim, deposit insurance, balance-sheet treatment and risk.
FinTechInstant Payments for Small Business: FedNow, RTP, Zelle Compared
How FedNow, RTP and Zelle differ for US small businesses on speed, settlement finality, limits and cost, plus which emerging options fit SME cash flow.