top of page

RT

REGAL TECH GLOBAL DELIVERY SYSTEMS

Strategic IT & Quality Engineering Partner

INSIGHTS

Stablecoins are coming to UK payments. Has anyone tested the plumbing?

nipundhiman

.

23 Jun 2025

.

3

Mins

DORA is live. Is your payment infrastructure tested for what it requires?

Nov 10
3 min read

DORA has been in force since January 2025. Most UK financial institutions have documented their resilience posture. Documentation is not evidence. The regulation requires tested failure scenarios — and the distinction matters.


On 17 January 2025, the Digital Operational Resilience Act came into force across the EU and applied immediately to every UK financial institution with EU-connected operations. I have been in enough rooms since then to hear the same honest answer when technology leaders are asked whether they have met its requirements. Most have documented their resilience posture. Fewer have tested it. Almost none have done both at the depth the regulation now expects.


That gap — between a resilience document and tested resilience evidence — is where DORA enforcement will concentrate over the next twelve months.

What DORA actually requires from payment technology teams

DORA is not a data protection regulation or a compliance framework in the traditional sense. It is an operational regulation. It is specifically concerned with whether financial institutions can continue to function when their technology fails — and whether they can prove it.


For payment technology teams specifically, DORA introduces four categories of obligation that go beyond traditional risk documentation. ICT risk management frameworks must be demonstrably operational. Major ICT incidents must be reported within defined timeframes — initial notification within 4 hours of classification, intermediate report within 72 hours, final report within one month. Third-party ICT risk must be managed and evidenced, placing payment gateways, processing infrastructure, and cloud providers within scope. And threat-led penetration testing is mandatory for significant institutions — not a documentation exercise, but an actual test of operational resilience under realistic attack conditions.


The difference between documentation and evidence

Most UK financial institutions entered 2025 with resilience frameworks designed to satisfy the Bank of England's operational resilience policy statement — documenting important business services, mapping dependencies, and defining impact tolerances. That work is necessary but insufficient for DORA.


DORA's standard is higher. It expects that impact tolerances have been tested, not just defined. It expects that failure scenarios have been executed, not just enumerated. It expects that the results of those tests are structured, retained, and available for supervisory inspection. The distinction is the same one I draw in the QA Maturity Framework between Level 2 — foundations documented — and Level 4 — evidence is a by-product of delivery. You can have all the right policies and still have nothing to show a regulator when they ask what happened when the test was run.


The four resilience testing gaps most payment firms have not closed

Failover and recovery testing at production load. Most firms have tested their failover scenarios at reduced load or in isolated test environments. DORA expects that resilience can be demonstrated under production-representative conditions. The active-active architectures now expected in payment processing — where multiple data centres handle live traffic simultaneously — need to be tested in that actual configuration, not simulated.


Third-party incident simulation. Your payment gateway goes offline. Your cloud provider has an availability event. Your message broker has a performance degradation. These third-party failure scenarios need to be tested as live exercises, not documented as risks. DORA's third-party risk management requirements are explicit that operational dependency must be tested, not assumed.


Incident classification and reporting drills. The 4-hour initial notification requirement is operationally demanding. It requires that your incident detection, severity classification, and regulatory reporting processes can execute correctly under pressure. Most payment teams have never run a timed drill testing whether they can classify, document, and report a major ICT incident within regulatory timeframes. That drill needs to be on the calendar before a real incident makes it unavoidable.


Threat-led penetration testing. For significant institutions, TLPT under DORA is not optional. It is a structured, intelligence-led penetration test of operational resilience using realistic threat scenarios. The testing methodology, scope, and reporting all have specific requirements. Most internal penetration testing programmes do not meet the TLPT standard, and commissioning a compliant engagement requires planning lead time that firms are already running short of.


The practical path from documentation to evidence

The path from where most UK payment firms are today to where DORA expects them to be is not a three-year programme. It is a structured sequencing of testing work that most firms already have the building blocks for, but have not assembled in the right order.


A Delivery Risk Audit that maps your specific DORA obligations against your current testing posture gives you the prioritised picture. The gaps it identifies — the untested failure scenarios, the third-party dependencies that have never been stress-tested, the incident response drills that have never been run — become the testing programme. The output of that programme becomes the evidence your regulators are entitled to request.


Delivery Risk Audit Template
Download


 
 
 

Recent Posts

See All

Comments


bottom of page