Payment Recall

A payment recall is an attempt by the bank that originated a transfer to halt it while it is still on its way, or to retrieve the money once it has reached the beneficiary. Recalls are typically made because a payment was a duplicate, was sent for the wrong amount or to the wrong account, or was induced by fraud. A recall is a request, not a right: whether money comes back depends on where the payment is, the rules of the system used and, in most cases, the cooperation of the receiving bank and the consent of the beneficiary.

A recall is related to, but different from, a returned payment. A return is initiated by the receiving side, usually because the payment cannot be applied; a recall is initiated by the sending side because it wants the money back.

The sender's customer asks its bank to recall the payment, giving the reference, amount, date and reason. The bank then sends a cancellation request along the payment chain. On the SWIFT network this was traditionally an MT192 request for cancellation referencing the original MT103; in ISO 20022 it is the camt.056 payment cancellation request, answered by a camt.029 resolution of investigation. If the receiving bank agrees, it sends the funds back as a return.

The outcome depends on timing:

• Before settlement or crediting: if the payment is still queued at the sending bank or an intermediary, it can often be stopped.
• After crediting: once the beneficiary bank has credited its customer, the money belongs to that customer. The bank usually needs the beneficiary's authorization to debit the account, and in many jurisdictions cannot simply reverse the credit.
• After withdrawal: if the beneficiary has already moved or withdrawn the funds, there may be nothing left to return.

Because interbank settlement is normally final, a recall operates outside payment finality rather than undoing it; any refund is a new payment in the opposite direction.

Cross-border wires

For international transfers, SWIFT gpi added a Stop and Recall service that uses the UETR to deliver the request to whichever bank currently holds the payment, which improves the chance of stopping it in transit. A payment trace is often run at the same time to establish where the funds are.

SEPA

In the Single Euro Payments Area, the credit transfer rulebooks define a recall procedure for duplicates, technical errors and fraud, with time limits for sending the request and for the receiving bank to respond. A positive response returns the funds; the receiving bank may refuse, for example if the beneficiary does not consent or the account has insufficient funds.

Domestic US payments

A Fedwire transfer is final and irrevocable once sent, so recovery relies on a request to the receiving bank. In the ACH network, Nacha rules allow an originator to send a reversal within a short window, five banking days, but only for specific errors such as a duplicate, a wrong amount or a wrong account, and not simply because the sender has changed its mind.

Most urgent recall requests arise from payment diversion fraud and other authorized push payment fraud. Speed is decisive, since fraudsters move funds out of the receiving mule account within minutes or hours. Receiving banks that suspect fraud may freeze remaining funds and report the account, but the legal basis for returning money without the account holder's consent varies by country. Reimbursement schemes, such as the United Kingdom's mandatory APP fraud reimbursement introduced in 2024, give some victims a route to recovery that does not depend on the recall succeeding.

Recalls frequently fail or take weeks. Common obstacles include beneficiaries who do not respond, accounts that have been emptied, intermediary banks that do not act on free-format messages, and differences in law between the sending and receiving country. For this reason, verification before payment is far more effective than recall after it. Where a recall is unsuccessful, a payment investigation can at least document what happened for legal or insurance purposes.