Payment Recall: Requests, Returns, and Limits

A payment recall is a request to cancel or recover an earlier payment, subject to the payment’s status and the rules of the relevant payment system. It is a request for action, not an automatic reversal or a guarantee of recovery. The ability to revoke the original payment order and the possibility of obtaining a separate return of funds are different issues.

How a Payment Recall Works

Fedwire provides a specific example of the institutional workflow. After a Reserve Bank has accepted a payment order, the sending participant may submit a nonvalue cancellation or return request. The Reserve Bank transmits it to the receiver, asking the receiving institution to act on the earlier payment. “Nonvalue” is important: this communication requests action rather than transferring the payment amount back. Any actual return of money is a separate action; forwarding the request does not itself undo the accepted payment order.

A payment recall therefore involves more than the sender deciding that the money should come back. In the Fedwire example, the receiving institution may refuse the return request. A positive acknowledgement that the request reached its destination establishes delivery only, not recovery. The response to a request is also separate from the message that returns funds. When checking the outcome, distinguish three things: whether the request was delivered, what response was received, and whether the money was actually returned.

Acceptance is the key boundary in this example. A Fedwire order may no longer be revoked once a Reserve Bank has accepted it, even though a cancellation or return request can still be sent. That later communication seeks a separate action; it does not restore the participant’s ability to revoke the original order.

Recall, Revocation, and Return

• Timing: Before a Reserve Bank accepts a Fedwire order, revocation requires a cancellation notice to arrive with a reasonable opportunity to act. Real-time processing effectively eliminates that window in practice.
• Effect on the Original Order: A later request does not revoke an accepted Fedwire order; it asks for action without changing the original order’s irrevocability.
• Movement of Funds: A recall asks for action on an earlier payment, while a return actually sends funds back. The request and the return are separate events.
• Evidence of Outcome: A delivery acknowledgement is not proof of returned funds. A response to the request must also be distinguished from the actual payment return.

Payment recall concerns action requested on an earlier payment, not payment-identification information such as a payment reference. Nor is it settlement risk, which concerns settlement exposure rather than a request to recover a payment.

Fedwire ISO 20022 Messages and Limits

In Fedwire’s ISO 20022 framework, camt.056 is a return request for a previously settled payment. The response is camt.029, which is distinct from the payment-return message. The message that actually returns funds from a previously settled value message is pacs.004. These codes distinguish requesting action, responding to the request, and returning money; they should not be treated as interchangeable evidence of recovery.

Swift’s exceptions and investigations framework labels camt.056 a payment cancellation request and camt.029 a payment cancellation response. That terminology does not make a cancellation request proof of reversal. Neither framework establishes a universal payment recall remedy: message availability, legal effect, and recoverability depend on the rail, jurisdiction, and transaction status. A request, its delivery, and an actual return remain separate events.