An agent executes a payment it was never meant to make — wrong counterparty, wrong amount, a limit crossed. The money has moved. When the error surfaces, the first question is uncomfortable but unavoidable: who pays? In regulated finance this is not a philosophical puzzle; it is a question of mandates, evidence and design. The answer depends less on blame and more on whether the system was built so that responsibility can be traced at all.

The chain behind one instruction

Behind a single agent operation there are usually several parties, each with a distinct role:

  • the principal — the person or company legally standing behind the operation;
  • the agent platform or developer embedding the unit;
  • the model developer whose model produced the intent;
  • the payment provider executing on the rails.

Each sits somewhere along the same instruction. Liability follows the mandate and the evidence, not the loudest party.

Where responsibility is decided

Authority is defined by the mandate: limits, approved counterparties and approval thresholds. When an agent exceeds its mandate, the useful question is where the design failed. Was policy applied below the model, where the agent cannot argue with it? Was the agent's identity verifiable and attributable? Was the operation validated once, against reliance, sanctions and profile fit, before funds moved? A ledger that records principal, agent and policy version turns an argument into a reconstruction.

Making liability workable

A few design choices do most of the work:

  • keep policy below the model, so it cannot be persuaded;
  • turn an over-limit operation into a human approval request, with the invoice and counterparty attached, rather than a hard rejection;
  • record every operation against the exact policy version it executed.

None of this removes the need for clear contracts between the parties. It does, however, give those contracts something concrete to point at.

In short

  • Liability follows the mandate and the traceable evidence.
  • Several parties share the chain; design decides what each can show.
  • Policy below the model makes exceeding it visible.
  • Records turn disputes into reconstructions.

This is general information, not legal or financial advice.

For how institutions frame these responsibilities, see institutions.