A payment recall is a request from the sending bank to the receiving bank to return a payment that has already been sent, usually because it was a duplicate, went to the wrong account, carried the wrong amount or was induced by fraud. The receiving bank need not return it, and often needs the payee's agreement first.
Why does a payment recall matter once AI agents act?
Speed decides many recalls. The sooner the request reaches the receiving bank, the more likely the money is still there. Agents can file recalls in minutes, at any hour, with the reason and evidence attached, and they can chase the response without anyone remembering to.
The risk is in what the agent tells the customer. A recall is a request, not a guarantee. An agent that says "your money is on its way back" has made a promise the bank cannot keep. Every message should say that the bank has asked for the money back and will report what happens. The full method is in how to process payment recall requests with an AI agent.
How does a recall work in practice?
- Establish the reason: duplicate, wrong account, wrong amount, or fraud.
- Check the timing and rules: each scheme sets how long after sending a recall may be made.
- Send the request: with a reason code and supporting details.
- Receiving bank acts: checks whether funds remain and, where needed, asks the payee.
- Outcome: the money is returned, partly returned, or the request is refused.
- Close the case: match any returned funds, update the customer, record the outcome.
Keep the facts in one place from the start. A payment investigation case template gives the fields.
What does that look like in an example?
A small manufacturer pays a supplier invoice of 4,200 twice by mistake and asks its bank to get the second payment back. The bank's agent confirms from the payment records that the two payments are identical and a day apart, files a recall with the reason "duplicate", and tells the customer it has asked for the return and will update them. Three days later the receiving bank returns the funds. The money arrives as a return, which the agent matches to the case before closing it, following how to handle payment returns with an AI agent.
Had the second payment gone to a fraudster, the same recall might have come back refused. Fraud recalls need a person involved from the start, because they lead to further decisions about the customer and the payee.
How is a payment recall different from a payment reversal?
A payment reversal undoes a payment from the sender's side: cancelling it before it settles, or a correcting entry by a party with authority to make it. A recall asks the other side to send the money back after it has arrived. Reversal is within your control; recall depends on someone else. That difference is why an agent may be allowed to file recalls more freely than it is allowed to reverse anything, as discussed in can an AI agent reverse a payment?
Which related terms should you know?
- Payment return: money sent back by the receiving bank, whether after a recall or because the payment could not be applied.
- Reason code: the standard category explaining why a recall is requested.
The wider limits on what agents may do with payments are in AI agents in banking.
Questions people ask
Can an instant payment be recalled?
A recall can be requested in the same way. The money may already have moved on, so success is less likely, and the customer should be told that plainly.
Should an agent decide whether to file a recall?
For clear errors proven by the bank's own records, such as a duplicate, an agent can file within its bounds. Fraud cases and disputed payments should involve a person before the recall is sent.