A payment reversal is the undoing of a payment so that the money returns to the payer, by cancelling it before it settles or through a reversing entry by a party with authority. It is not a refund, which is a new payment, and not a recall, which only asks the other side for the money back.
Why does a payment reversal matter once AI agents act?
Reversal is what makes an action reversible in practice. An agent that can pay but whose mistakes can be reversed cheaply is a much smaller risk than one whose payments are final at once. That is why the time during which reversal is possible, the reversal window, shapes how far an agent may be trusted to act.
The power to reverse is also a risk in its own right. An agent able to reverse payments could undo legitimate ones, credit the same customer twice, or be talked into reversing a payment by someone with a convincing story. So the ability to reverse needs bounds of its own, decided per action, as covered in can an AI agent reverse a payment?
How do reversals happen in practice?
The method depends on where the payment has got to. Before settlement, a payment can usually be voided or cancelled with one step. A card authorisation not yet captured can be released through the payment gateway, which is why an agent's gateway permissions matter, as set out in how to connect an AI agent to your payment gateway. An error inside one institution can be corrected with a reversing entry. Once the money has settled at another bank, reversal is usually no longer possible from your side, and you are left with a recall, a refund or a dispute.
How is a reversal different from related terms?
| Term | Who starts it | Needs the other side to agree? |
|---|---|---|
| Reversal | The sender's side, before settlement or with authority | No |
| Refund | The payee, as a new payment | It is the payee's choice |
| Recall | The sending bank, as a request | Yes |
| Return | The receiving bank, sending money back | It is their act |
| Chargeback | The card issuer, through the card network | No, but the merchant can contest |
Returns have their own handling, covered in how to handle payment returns with an AI agent.
What does that look like in an example?
A payment gateway's merchant support agent receives a message from a café owner: a customer's card was charged twice for 45 a few minutes ago. The second charge is still an authorisation that has not been captured. The agent voids it at depth 3, inside the window the gateway allows, and tells the café owner. The next day the same café reports another duplicate, this time already settled. The agent cannot reverse it. It drafts a refund for the café owner to approve and explains why the route is different.
Where Pryme fits
Some reversals are withheld at the platform floor for every agent at every depth: reversing a settled payment on Pryme's own rail is one. The action exists and works, but no agent is allowed it. Customers can narrow other reversal rights further through their own limits, recorded in a reversal window policy. The broader limits are in AI agents in banking.
Questions people ask
Will the customer see a reversal?
Often, briefly. A voided authorisation may show as pending and then disappear. Tell the customer what they will see so they do not report it as a second problem.
Is a reversed payment recorded anywhere?
It should be. The original payment, the reversal, who or what decided it and why should all be filed so the history can be reconstructed.