A Fedwire transfer is a move of central bank money, and the Federal Reserve leaves the sanctions check on it to the banks. In the third quarter of 2026 Fedwire moved $4.83 trillion on an average day, according to the Reserve Banks' quarterly statistics.
In section 20.2 of Operating Circular 6 the Reserve Banks "assume no responsibility" for a participant's compliance obligations, economic sanctions among them. Each participant "is responsible for complying with such obligations when it sends or receives Messages". The sanctions screening on a Fedwire payment is the banks' own work: the sender screens before release, the receiver before it pays its customer.
What is Fedwire?
The Board describes the Fedwire Funds Service as "a real-time gross settlement system that enables participants to initiate funds transfer that are immediate, final, and irrevocable once processed" (Federal Reserve). Gross means each payment settles on its own, without netting. Every participant keeps a master account at a Reserve Bank, and one transfer can carry up to one penny less than $10 billion, according to the Reserve Banks' December 2025 disclosure.
Over 5,000 customers can send or receive payment orders, yet the disclosure calls its use "highly concentrated among the top 10 participants" by volume. In the third quarter of 2026 Fedwire settled 58.2 million transfers worth about $313.9 trillion, $5.39 million each on average. Participants can be looked up by name, place or routing number in the E-Payments Routing Directory, which is synchronized with the Fedwire and FedACH databases every day.
How does a Fedwire transfer work?
An illustrative case: an Ohio manufacturer asks its bank to wire a supplier $2.4 million at 6:30 p.m. ET on a Thursday.
- The sending bank screens both parties, then sends a pacs.008 customer transfer before the 6:45 p.m. cutoff.
- The Reserve Bank checks the security procedures and the message format. Orders that pass are generally accepted.
- It debits the sending bank's master account and credits the receiving bank's.
- The processed message carries an IMAD and an OMAD, the identifiers the Reserve Banks give as proof that a wire went through.
- The receiving bank screens the payment and credits the supplier.
Finality comes at step 3: the disclosure says the payment is final and irrevocable once credited to the receiving bank, or once the order is sent to it if that comes first. Regulation J subpart B, which brings Article 4A of the Uniform Commercial Code into Fedwire, governs the transfer.
To get money back, the sender can only ask: a camt.056 return request carries no value and asks the receiving bank to send the amount back. A camt.110 investigation request asks it to confirm the credit. Regulation E, the consumer rule for electronic fund transfers, excludes transfers through Fedwire.
On Fedwire, the sending bank's filter is the last point where a sanctioned wire can be kept from moving.
That filter reads the payment message. complead, formerly Sanction Scanner, offers one as payment screening, which covers Fedwire Funds Service payment messages in the same way as SWIFT MT and ISO 20022 messages: each message is parsed, every party field is extracted and screened against sanctions and watchlists in real time, and a match holds the payment before release.
Fedwire hours and cutoff times
The business day opens at 9:00 p.m. ET on the previous calendar day and closes at 7:00 p.m. ET, Monday to Friday (operating hours). Customer transfers stop at 6:45 p.m. Bank transfers, cover payments and return requests run until 7:00 p.m., tax payments only until 5:00 p.m. Weekends and Reserve Bank holidays are closed, and the Reserve Banks may extend a cutoff. Sundays and weekday holidays join the schedule no earlier than 2028.
How are Fedwire payments screened for sanctions?
| Rule | What it requires on a Fedwire payment | Threshold or clock | Source |
|---|---|---|---|
| Regulation J subpart B, with UCC Article 4A | Governs the transfer; final once credited to the receiving bank | At the credit | 12 CFR 210.25 (Board) |
| Operating Circular 6, section 20.2 | Each participant answers for its own sanctions, AML and fraud duties | Every message | Reserve Banks, edition effective 5 January 2026 |
| OFAC blocking, 31 CFR 501.603 | Blocked funds go into a separate account that earns interest, and are reported to OFAC | Report within 10 business days | eCFR 501.603 and OFAC FAQ 32 |
| OFAC rejects, 31 CFR 501.604 | A rejected wire transfer is reported to OFAC | Report within 10 business days | eCFR 501.604 |
| Recordkeeping Rule, 31 CFR 1020.410(a) and 1010.410(e) | Banks and nonbank institutions collect and keep the transfer's information | $3,000 or more | Federal Register, 9 November 2026 |
| Travel Rule, 31 CFR 1010.410(f) | The transmittor's details travel with the order; a Fedwire carve out for the address is still in the text | $3,000 or more | eCFR 1010.410 |
| OFAC FAQ 116 | A bank that knows or has reason to know a party is blocked has to block the wire, intermediaries included | Once the bank holds that information | OFAC FAQ 116 |
Table 1. The rules a Fedwire payment meets (eCFR title 31 current to 6 November 2026, title 12 to 12 November 2026; all read 15 November 2026).
OFAC's FAQ 116 covers the bank in the middle. An intermediary with no direct relationship to a party and no reason to know its blocked status is not expected to research non account parties absent from the SDN List. Once it has reason to know, say that an entity is owned 50 percent or more by a listed person under the OFAC 50 percent rule, it answers for a wire it did not block.
Under the Travel Rule, the eCFR text still lets a Fedwire order leave out the transmittor's address "until such time as the bank that sends the order to the Federal Reserve Bank completes its conversion to the expanded Fedwire format".
What did ISO 20022 change for Fedwire?
On 14 July 2025 the Reserve Banks moved the Fedwire Funds Service to ISO 20022 and retired the proprietary FAIM format. A customer transfer now travels as a pacs.008; a bank transfer or a cover payment as a pacs.009. The Reserve Banks said the richer data "will facilitate banks' and other entities' compliance with sanctions" and AML rules (release of 15 July 2025).
For an ISO 20022 screening filter, the parties now sit in named elements such as the debtor and the debtor agent. The next release, due on 22 November 2027, adds a hybrid postal address format and keeps the unstructured one (scope document of 6 November 2026).
How is Fedwire different from CHIPS, FedNow and SWIFT?
| System | Operated by | How a payment settles | When it runs | Message format |
|---|---|---|---|---|
| Fedwire Funds Service | Federal Reserve Banks | One payment at a time, gross; final once credited | 22 hours each business day, 9:00 p.m. to 7:00 p.m. ET | ISO 20022 since 14 July 2025 |
| CHIPS | The Clearing House Payments Company | Some payments one by one, others netted by an algorithm that saves liquidity; final when released from the queue | Set by CHIPS's own rules | ISO 20022 changes on 22 November 2027, in tandem with Fedwire and SWIFT |
| FedNow | Federal Reserve Banks | Instant payments, sent and received in real time | Around the clock, every day of the year | ISO 20022 |
| SWIFT (FINplus) | SWIFT | Does not settle: it carries the instruction, and the money moves elsewhere | Not a settlement system | ISO 20022 for cross border payments between banks since 22 November 2025 |
Table 2. Fedwire beside CHIPS, FedNow and SWIFT (Reserve Banks' disclosure and pages, SWIFT's ISO 20022 FAQ; read 15 November 2026).
SWIFT carries the instruction between banks, each identified by its SWIFT/BIC code, while the money settles in Fedwire, CHIPS or a correspondent bank's own books. Fedwire and CHIPS are the two US large value payment systems, and Fedwire settles about twice the value CHIPS does on an average day.
FedACH, the Reserve Banks' ACH service, runs "batched payment services" for debit and credit transactions instead.
Where does Fedwire sit in an AML program?
- Sanctions screening of every party. Before release, and again before the customer is credited; the Reserve Banks take on none of it.
- Records and Travel Rule data. At $3,000 or more, the transfer's information is collected, kept and passed to the next bank.
- Wire monitoring. One customer paying a dozen new beneficiaries in a week (illustrative) is a pattern no single wire shows, and transaction monitoring for wire transfers looks across them.
- Correspondent due diligence. A bank without a master account at a Reserve Bank sends its dollar wires through a correspondent bank, and OFAC expects each bank to do due diligence on its own direct customers, ownership included.
What changed for Fedwire in 2026?
- 27 August 2026. The Fedwire release planned for November 2026 moved to November 2027.
- 9 November 2026. FinCEN and the Board withdrew their 2020 proposal to cut the threshold from $3,000 to $250 for transfers that begin or end outside the United States, so the $3,000 rules stay.
- 12 November 2026. 2027 prices: $0.98 per Tier 1 transfer before incentive discounts from 1 January 2027, up from $0.97.
Fedwire leaves your payments and compliance teams one decision: where the sanctions check sits relative to release. Before the Fedwire order goes out, a hit stops the money at your bank. After it, the funds are final at the receiving bank, and what is left is a block or a reject and a report to OFAC within 10 business days.
Related terms
- Correspondent banking. Accounts one bank keeps for another, through which the respondent bank's payments run.
- Travel rule. The duty to send originator and beneficiary details with a transfer to the next institution.
- SWIFT/BIC code. The identifier that names a bank on a SWIFT message.
- Wire fraud. Fraud carried out over wire communications, such as a fake payment instruction that sends a transfer to the wrong account.
- Bank Secrecy Act. The US law behind the recordkeeping and reporting rules that apply to wires.
- Electronic funds transfer. Money moved between accounts by electronic means, ACH payments included.