
A wire looks simple. Money leaves one bank and arrives at another the same day. But once a wire settles, it is final. A mistake or a fraud can become a permanent loss. This is how I take a wire change from idea to live, safely.
New here? Start with How a US Payment Works: 15 Steps Inside a Bank, then come back for the detail.
How a US wire moves
Read from left to right. Each box is one step, from the customer who asks for the wire to the person who receives it. The band at the bottom shows the checks that must happen before release. After Step 3, the payment is final.
Fedwire and CHIPS in one minute
US banks send domestic dollar wires through two systems. Fedwire is run by the Federal Reserve. In 2025 it handled 217.3 million transfers worth about $1.15 quadrillion, about $5.28 million each on average. CHIPS is run by The Clearing House. It moved about $2.014 trillion a day in 2025, mostly large business and cross-border payments.
| Topic | Fedwire | CHIPS |
|---|---|---|
| Settlement | Real-time gross settlement (RTGS): each wire moves on its own, straight away, and is final at once | Netting: banks put money in first, wires are matched against each other, and each is final when released |
| Message format | ISO 20022 (a newer, richer format for payment messages) since July 14, 2025 | ISO 20022 since April 8, 2024 |
| Customer cutoff | 6:45 p.m. ET | Check the current CHIPS schedule |
Fedwire is open from 9:00 p.m. ET the evening before to 7:00 p.m. ET, Monday to Friday. The Federal Reserve plans to move to 22 hours a day, Sunday to Friday, around 2028 or 2029. Plan your support hours for it now.
The one rule that changes everything
A wire is final once it settles. Unlike ACH, there is no return window. If money goes to the wrong account, you can only ask the receiving bank to send it back. So every important check happens before the wire leaves: a call-back to a number you already trust when bank details are new or changed, a second approver, limits, an OFAC sanctions check, fraud checks, and a check that the same wire isn’t sent twice.
The biggest wire fraud risk is a fake email from a “supplier” asking you to pay new bank details. This is called business email compromise, or BEC. The fix is a habit, not a tool: always confirm changes by calling a number you already have, never the one in the email.
Building it: short cycles, firm checkpoints
The work is the same as any payment change: requirements, design, build, testing, release and deployment, done in overlapping two-week cycles. Three things are special for wires:
- Test every kind of wire message, not just customer payments (pacs.008). Include bank-to-bank transfers (pacs.009), returns (pacs.004), status updates, drawdowns and rejections.
- Plan around fixed dates: Federal Reserve and CHIPS release and test dates, holidays, and the year-end change freeze.
- Prove it live with small pilot wires before customers use it. Send $1 to an account you control at another bank. Check the tracking numbers (IMAD and OMAD) both ways. Receive a wire, send one back, and make sure every record matches.
| Gate | Done when |
|---|---|
| E2E exit | All planned tests run, 95% or more passed, no Sev 1 or Sev 2 bugs (the most serious) open, every message type works, all records match |
| UAT exit | Business scenarios signed by the owner; operations procedures tested by the people who use them |
| Go-live | Federal Reserve and CHIPS testing passed, pilot wires checked, alerts and the backup site (disaster recovery, or DR) tested |
Running it live
L1: the wire operations team watches the queues and fixes wires. L2: app support handles system problems. L3: engineers and vendors fix the code. The clock that matters is the cut-off, so raise anything that could make a wire miss the day. Send alerts to Slack or Teams when the bank link drops, a bank reply is missing, wires pile up near cut-off, a certificate is about to expire, or records don’t match.
If the main site goes down, the goal is simple: no lost wires, and back up before the Fedwire cut-off, using a tested backup FedLine link. After switching sites, check every wire before resending anything, so you never pay twice.
Download the full runbook (PDF, 15 pages)
Every phase in detail, with Fedwire and CHIPS facts, ISO 20022 messages, rules, exit criteria and sign-off, a live pilot plan, controls, alerts, incident runbooks, disaster recovery, audit checklists and a go-live checklist.
The files behind this runbook
Every part of this runbook touches the same handful of files. Here is where each one shows up. For what is inside each file, with samples and a step-by-step checklist, see Fedwire, file by file and CHIPS, file by file.
| File or moment | Where it matters in this runbook |
|---|---|
| pain.001 (URGP), portal or API | How a US wire moves |
| pacs.008 / pacs.009 and pacs.002 | Fedwire and CHIPS in one minute |
| Sanctions holds and maker-checker | The one rule that changes everything |
| pacs.004, camt.056 and camt.029 | Running it live: returns and recalls |
| Fed account statement | Running it live: daily reconciliation |
More payment runbooks
- ACH payments
- Instant payments (RTP and FedNow)
- Card payments (debit, credit, prepaid)
- Checks and remote deposit capture
- Cross-border payments over SWIFT
- Zelle for banks
- PayPal integration
- Embedded payments
The bottom line
With wires, the safest moment is before release. Put strong checks there, test every message type, prove the live path with small pilot wires, and run support against the cut-off clock.
Working on a payments project?
I help banks and fintechs deliver real-time payments, ISO 20022, and AI-driven AML and compliance change, from strategy to go-live.
Connect on LinkedInSee how I can help