Send a Fedwire camt.056 return request to recall funds from a previously settled wire and interpret the receiving bank's camt.029 response
domain: frbservices.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Send a camt.056 (Return Request) message to request return of the amount of a previously settled Fedwire payment order, such as a pacs.008 customer credit transfer or pacs.009 FI credit transfer; Fedwire imposes no restriction on the date a return request may be sent
Populate the Originator element in the camt.056 with the party that originated the return request
Wait for the receiving institution's camt.029 (Return Request Response), which indicates whether it will honor the return
If the camt.029 response is affirmative, expect the receiving institution to separately initiate a pacs.004 (Payment Return) message to actually move the funds back
Do not send an investigation request (camt.110) to request a fund return; camt.110/camt.111 are reserved for exceptions and investigations, and Fedwire Funds Service participants must not use them in place of camt.056
Track successful camt.056 submission via the admi.007 positive acknowledgement, and handle any camt.029 business-error response containing the rejection reasons
Known gotchas
A camt.056 only requests a return; Fedwire payments are final upon settlement, so recovery of funds depends entirely on the receiving institution's willingness, expressed via camt.029, to originate the pacs.004, not on any unilateral recall right of the sender
Fedwire imposes no timing restriction on when a return request or payment return may be sent, so return-eligibility logic should not assume a fixed window such as same-day only
camt.110 (Investigation Request) replaced the old FAIM service message type 90 for general inquiries, but participants must not use camt.110 in place of camt.056 to request a return, since the two message types serve different purposes
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?