Rarely, and not in the way people expect. An AI agent can cancel a payment that has not yet left, and prepare a recall request for one that has. It cannot pull back money that has settled elsewhere. Reversing a settled payment on a bank's own rail is an action that should be withheld from every agent, at every depth.
What does "reverse" mean in practice?
The word covers four different things, and the agent must know which one it is dealing with.
Cancelling before settlement. A scheduled transfer, a future-dated payment or a payment still in a queue can be cancelled. Nothing has moved. This is the customer's right, and the agent can do it on their instruction.
Recalling after settlement. Once the money has reached the receiving bank, the sender's bank can ask for it back. The receiving bank usually needs the recipient's agreement, unless fraud rules apply. A recall is a request, not a reversal. Our explainer on what a payment recall is covers how it works.
A return. The receiving bank sends the payment back itself, for example because the account is closed. This arrives as a new incoming payment.
A true reversal. An operator undoes a settled transaction on its own books or rail. Some systems technically allow it. That is the case for a hard line, set out in what a payment reversal is.
Why is reversing a settled payment withheld?
Settled money belongs to the recipient. Taking it back without their agreement or a legal basis takes money from someone who may have every right to it, and may already have spent it. A system that lets an agent do this has made the most dangerous action in payments available to anything that can talk the agent into it.
There is also no clean undo. If the agent reverses a payment wrongly, putting it right means another forced movement against the recipient. That is why the platform floor withholds it: the action exists, it works, and it is refused for every agent on purpose. Customers cannot configure it back.
What may the agent do, and where must it stop?
| Request | The agent | Where it stops |
|---|---|---|
| Cancel a scheduled or future-dated payment | Cancels at depth 3 on the customer's instruction | Payments already in a settlement cycle |
| Cancel a payment still queued for fraud checks | Cancels on the customer's instruction | Nothing routine |
| Recall a settled payment sent in error | Prepares the recall with the reason, depth 2 | A person submits and follows it up |
| Recall for suspected fraud | Prepares and routes urgently | Fraud team |
| Reverse an internal book transfer | Makes a new transfer back on instruction, with checks | Restricted accounts |
| Reverse a settled payment on the bank's rail | Withheld | Not available to any agent |
| Reverse a card payment | Explains refund and chargeback routes | Merchant or disputes process |
Accounting entries are a different world: a journal can be reversed by a matching entry. See whether an AI agent can reverse a journal entry.
An example: the wrong supplier
Take a small business customer who pays 4,800 to the wrong supplier on a Thursday afternoon: two suppliers with similar names, and the clerk picked the wrong one from the payee list. They notice an hour later and message the bank's agent: "Reverse the payment to Brightline, it should have gone to Brightside."
The agent checks the payment. It was an instant payment and settled within seconds. It explains that it cannot reverse a settled payment, but it can prepare a recall request. It records the details and the reason, and prepares the recall for the payments operations team, flagged as a misdirected payment rather than fraud. It also suggests the customer contact Brightline directly, since a supplier that knows the customer will often return money quickly.
A person submits the recall that afternoon. The receiving bank contacts Brightline, which agrees to return the money. It arrives the following Tuesday as an incoming payment, which the agent matches to the recall.
What controls make it safe?
- The reversal capability is withheld. No agent holds it, and attempts are filed as withheld verdicts with the guardrail named.
- Settlement status from the rail. Whether a payment can still be cancelled is read as a sealed fact from the payment system.
- Recalls prepared, not sent. The agent drafts recall requests; a person submits them.
- Cancellation only on instruction. The agent cancels payments the customer asks it to, not ones it thinks look wrong.
- Returns matched to recalls. Money coming back is linked to the original case.
Returns have their own process, covered in handling payment returns with an AI agent, and the technical limits of what an agent should be able to call are covered in connecting an AI agent to your payment gateway. The general limits are in AI agents in banking: what they may and may not do.
Questions people ask
Can the agent stop a payment the customer has just made?
Only if it has not yet settled. On instant payment schemes that is usually seconds, so the practical answer is often no.
What if the bank itself sent a payment twice by mistake?
The bank can usually recall the duplicate under scheme rules for operational errors. A person handles it, because the recipient's account is affected.
Does a recall always work?
No. If the recipient has spent the money or refuses, the recall can fail, and the customer may need to pursue the recipient directly.