Build a Fedwire Funds Service outbound wire and understand the ISO 20022 migration timeline and coexistence period
domain: banking-general · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Submit a Fedwire outbound wire via your bank's API or SWIFT FileAct with the required fields: sender ABA, receiver ABA, amount, sender reference, beneficiary name and account, and optionally OBI (originator-to-beneficiary information) line
During the ISO 20022 coexistence period (Fedwire's migration is multi-year; check current Fed guidance for active phase), your bank's gateway translates between legacy Fedwire format and ISO 20022 pacs.008 automatically
For new integrations targeting ISO 20022 native, compose a pacs.008 FIToFICstmrCdtTrf with SttlmMtd=INDA (settlement via Fedwire) and use the Fed's published translation tables for field mapping
Include the UETR in the pacs.008 GrpHdr for end-to-end tracking; this is mandatory in ISO 20022 native mode and recommended during coexistence
Receive the outbound confirmation (IMAD — Input Message Accountability Data) from the Fed; store it as the authoritative settlement reference for the wire
For inbound wires, parse the OMAD (Output Message Accountability Data) from your bank's notification and match it to open receivables using amount, sender reference, or beneficiary account
Known gotchas
Fedwire operates on a same-day settlement cycle with defined opening and closing times (roughly 9pm ET Sunday through 7pm ET weekday); wires submitted after the cutoff settle the next business day — verify current Fed operating hours as they are periodically updated
The ISO 20022 migration for Fedwire is happening in phases over several years; during coexistence, translation between old and new formats happens at the Fed but field truncation is possible — structured address fields in pacs.008 may be truncated when translated to legacy format for recipients on old systems
IMAD/OMAD are only issued for settled wires; a wire that is rejected before settlement will not have an IMAD — use the rejection reason code returned by your bank, not an IMAD lookup, for failed-wire debugging
Give your agent this knowledge — and 15,600+ 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?