Payments AI Control Plane DORA | Moring
DORA applies to payment institutions and other EU financial entities from January 2025, and agents acting on payment systems fall inside its scope as ICT-supported functions. A payments control plane supplies what DORA expects: documented ICT risk management for agent boundaries, detailed logging of every agent action, resilience testing that can stop an agent, and third-party oversight of model and platform dependencies.
Short answer
DORA applies to payment institutions and other EU financial entities from January 2025, and agents acting on payment systems fall inside its scope as ICT-supported functions. A payments control plane supplies what DORA expects: documented ICT risk management for agent boundaries, detailed logging of every agent action, resilience testing that can stop an agent, and third-party oversight of model and platform dependencies.
How it works
DORA, the EU Digital Operational Resilience Act, has applied since 17 January 2025 to roughly twenty types of financial entities, including payment institutions and e-money institutions, plus the ICT third-party providers serving them. Regulatory guidance is direct about the consequence for agentic AI: if an agent changes a record, moves a payment, or touches critical infrastructure, it is an ICT-supported function, and its governance must survive the same scrutiny as any other part of the IT estate. A payments AI control plane is the infrastructure layer that makes that scrutiny answerable, because it concentrates the identity, logging, and enforcement records DORA examines.
The first pillar mapping is ICT risk management. DORA requires financial entities to identify all functions and information assets and classify data according to criticality, with detection mechanisms for anomalous activities and data integrity checking. Compliance analysis stresses that the exposure sits at the data infrastructure layer, in whether the platform can produce the audit evidence regulators ask for. For a payments control plane, that means documented risk assessment for each agent acting on payment systems, defined boundaries on what each agent can reach, and controls proportionate to the harm an agent could cause to settlement or customer funds.
The second pillar is logging and evidence. DORA requires detailed logging of events affecting ICT-supported functions, and agent-specific guidance translates this into a record of every action: what the agent proposed, what policy allowed, what a human approved, and what changed in the source system. Database-oriented DORA guidance for AI agents lists the infrastructure capabilities that make this defensible, including append-only audit storage, per-agent identity attribution on every write, and idempotency to prevent duplicate transactions. A control plane that generates these records continuously turns an incident classification exercise into a query, which matters because major ICT incidents involving payment agents must be classified and reported like any other.
The third pillar is resilience testing. DORA requires entities to test their digital operational resilience, and for agent workflows the operational translation is a drill: can you stop the agent, prove it stopped, and list what it did? Agent guidance makes the pointed observation that a deployment rollback is not a kill switch. A payments control plane supplies the stop controls and the evidence of stopping, and its enforcement path is what resilience testing exercises. Compliance guidance also observes that AI complicates matters by introducing tools, vendors, and failure modes that may fall outside existing inventories and monitoring yet remain within DORA's scope, and that the practical path is to fix visibility first.
The fourth pillar is third-party risk, which reaches every model provider and agent platform a payments control plane mediates. DORA governs ICT third-party providers, including critical providers under direct EU oversight, so vendor dependencies behind agent workflows carry data residency, exit plan, and contractual assurance requirements. A payments firm that routes all agent access to payment systems through the control plane has a single place to enumerate those dependencies, attach contractual evidence, and demonstrate to supervisors that oversight of third-party technology behind payment operations is functioning under DORA.
Frequently asked questions
Yes. DORA applies to financial entities including payment institutions from 17 January 2025, and agent-specific guidance states that an agent changing a record, moving a payment, or touching critical infrastructure is an ICT-supported function governed with the same scrutiny as any other part of the IT estate. The payments control plane is where the agent's risk assessment, boundaries, logging, and stop controls live in a form DORA supervisors can examine.
Detailed logging of events affecting ICT-supported functions: what the agent proposed, what policy allowed, what a human approved, and what changed in the source system. DORA database guidance for AI agents adds append-only audit storage and per-agent identity attribution on every write as infrastructure capabilities. A payments control plane generates this evidence continuously, so incident classification and reporting become queries rather than reconstruction projects.
As drills with provable outcomes: stop the agent, prove it stopped, and list what it did before the stop. Agent guidance observes that a deployment rollback is not a kill switch, which is why the control plane's stop controls and their evidence trail are what the test exercises. For payment-critical workflows, the drill should also confirm enforcement held throughout and that the resulting records satisfy incident reporting requirements.
As ICT third-party providers in scope. DORA's oversight framework covers third-party providers, including critical ones under direct EU supervision, so the model APIs and agent platforms behind payment workflows carry data residency, exit plan, and contractual assurance obligations. Compliance guidance notes that AI introduces vendors and failure modes outside existing inventories but inside DORA's scope, which is why the control plane should be the single register of those dependencies.