Fedwire or CHIPS: When the Rail Behind a USD Wire Matters to an Operator

Direct answer

You cannot put a payment on either rail yourself. Only a Fedwire Funds Participant or a CHIPS Participant can submit one, and neither rulebook gives a bank's customer any role in picking between them. The law behind the payment is less absolute. Under UCC Article 4A, a bank that takes your payment order must follow an instruction naming a funds-transfer system, unless it decides in good faith that following it is not feasible or would hold the payment up. But that rule can be written out by agreement, and some banks' published wire terms do write it out — one names the point directly, telling customers its selection "may differ from that indicated in your payment instructions". So the question is not whether the rails allow you a say. It is what your own bank's agreement says. Either way the rail reaches you in three places: who holds the settlement record you will need when a payment goes missing, what "sent" means when you read a status, and which cutoff you actually missed. This reference covers those three, states what the two operators publish about each, and is explicit about what the public record does not establish.

Why you see the rail at all

A USD wire runs from your instruction to your bank, then bank to bank. The Federal Reserve Banks operate one large-value system, the Fedwire Funds Service; The Clearing House operates the other, CHIPS. Your bank is on one or both, or reaches one through a correspondent. When a payout fails to arrive, when a treasury sweep lands a day late, or when a counterparty asks you to prove a payment was made, the rail decides which institution has the record, what that record proves, and how late in the day it could have moved.

That is the whole reason to care. The rest of this page is the mechanics behind those three effects, from the two operators' own documentation.

Who can be on each rail — and what that does to routing

The eligibility rules differ in kind, not degree.

The Board of Governors describes Fedwire eligibility in one sentence: "Depository institutions and certain other financial institutions that hold an account with a Federal Reserve Bank are eligible to participate in the Fedwire Funds Services." The account is necessary, not sufficient: Operating Circular 6 adds that "Eligibility to become a Funds Participant is further limited by Federal Reserve policies and the Administrative Reserve Bank's discretion in providing access to the Fedwire Funds Service." The Board's page gives a participant count, but for 2008, so this reference states the rule rather than a number.

CHIPS is narrower by design. The Clearing House's current page states "43 direct participant banks", and then the sentence that matters for routing: "FIs that do not participate directly in CHIPS may also access CHIPS payment capabilities through correspondent or respondent banking relationships with CHIPS participants." So for most institutions CHIPS is reached through someone else. That is ordinary correspondent banking, and it has an operational consequence that is easy to miss until a payment goes wrong: if your bank is not a direct participant, the institution that actually submitted your payment to CHIPS is someone else — and that is where the rail-level record sits.

The Board classifies the two accordingly. Fedwire is a Reserve Bank service. CHIPS "is a real-time, multilateral payment system typically used for large dollar payments"; its operator, The Clearing House Payments Company, is a designated financial market utility on the basis of that role, and "The Board is the Supervisory Agency for CHIPS under Title VIII of the Dodd-Frank Wall Street Reform and Consumer Protection Act of 2010." It must comply with Regulation HH and is examined under the FFIEC and by the New York State Department of Financial Services. None of that changes your payment; it tells you the two rails are not two flavours of one thing.

Operator consequence. When you instruct a bank to send a high-value USD payment, ask which rail it will use and, for CHIPS, whether your bank is a direct participant. If it is not, your investigation path has an extra hop before it reaches the rail's own record.

What "sent" means on each rail

This is the difference an operator feels most, and it is the one the two operators describe in the most different terms.

Fedwire. The Board's description is compact: Fedwire is "a real-time gross settlement system that enables participants to initiate funds transfer that are immediate, final, and irrevocable once processed." Gross means each transfer is settled individually across the participants' Reserve Bank master accounts; there is no waiting for other payments to offset it. Operating Circular 6 ties settlement to acceptance directly: "In connection with a payment order that a Reserve Bank accepts, the Reserve Banks (i) settle the payment order by debiting the amount of the payment order from the Master Account of the sender of the payment order and crediting the amount of the payment order to the Master Account of the Funds Participant identified by the sender as the receiver of the payment order". Accepted is settled. The circular's timing provision (section 10.2) adds that the obligation is met if the Reserve Bank executes or pays "on the same Fedwire Funds Service Funds Transfer Business Day that it received the payment order even if it is not the same calendar day."

What Fedwire does have is a step before acceptance. A message not yet received by the service "may be queued indefinitely", and a Reserve Bank "may for any reason reject or impose conditions that must be satisfied before it will process or accept a Message from a Funds Participant, including a payment order." So the question on Fedwire is whether the payment order was accepted — not, once it was, whether it has settled.

And processed leaves a mark. The Federal Reserve Financial Services FAQ answers "How can I confirm that a wire payment was sent successfully?" with: "All successfully processed messages will contain the Input Message Accountability Data (IMAD) and Output Message Accountability Data (OMAD) identifications." If your bank cannot give you an IMAD for a Fedwire payment, you do not yet have evidence that Fedwire processed it — whatever the bank's own screen says.

CHIPS. The Clearing House describes a different mechanism, and its FAQ is precise about the point at which settlement happens: "CHIPS is not an end-of-day settlement system. CHIPS provides continuous intraday settlement with finality. Payments are settled when they are released under CHIPS rules and available liquidity conditions." Release is the event. The service page explains why release and submission are not the same moment: "For many payments, settlement may occur in near real time, depending on value, liquidity, and participant-configured prioritization and liquidity controls." Others may wait, because the system is looking for offsets — TCH describes "a liquidity-saving mechanism that helps participants settle large payment volumes with substantially less funding than traditional gross-settlement models", and reports "~26:1 liquidity efficiency ratio in 2025". Finality, once reached, is the same kind: "Once a payment is released and settled, settlement is final and irrevocable."

Operator consequence. On Fedwire, once a payment order is accepted it is settled; the only open question is acceptance, and IMAD/OMAD answers it. On CHIPS, per The Clearing House, a submitted payment settles on release, and release is a function of the participant's liquidity and its prioritisation settings — neither of which you can see. If a counterparty tells you a CHIPS payment "went out this morning", the question is whether it has been released. On Fedwire there is no gap between acceptance and settlement to ask about.

Hours and cutoffs

Fedwire's clock is published to the minute, on the page most people find first. The CHIPS clock is published too — just not where most people look.

Fedwire. The funds-transfer business day "begins at 9:00 p.m. ET on the preceding calendar day", so Monday's day opens on Sunday evening. The service "stops processing online messages at the cutoff times shown below and closes at 7:00 p.m. ET." The cutoffs that matter to an operator, from the Reserve Banks' schedule:

The Board states the same 6:45 p.m. deadline in plain language: "The deadline for initiating transfers for the benefit of a third party (such as a bank's customer) is 6:45 p.m. ET each business day." A customer payment — which is what an operator's payout or supplier payment is — has fifteen minutes less than a bank-to-bank transfer. The Reserve Banks may extend cutoffs and the closing time.

CHIPS. The Clearing House states that "CHIPS operates on a 21-hour processing window", and the clock behind that figure is published — not on the service page or the FAQ, but in the rulebook and the PFMI disclosure. The CHIPS Rules and Administrative Procedures effective 4 June 2026 open the system at 9:00 p.m. and close it at 6:00 p.m. "for the delivery by Participants of payment messages". TCH's public disclosure states the same and adds the calendar convention: the service opens at 9:00 p.m. ET on the calendar day preceding each operating day, "even if the preceding calendar day is a holiday or weekend", and does not operate on weekends or certain designated holidays. 9:00 p.m. to 6:00 p.m. is the 21 hours. Two qualifications matter. The 6:00 p.m. close applies to delivery of payment messages generally — there is no separate customer or third-party cutoff in the CHIPS rules, as there is on Fedwire. And the schedule is not fixed by publication: the rules state that the hours given for performance are for guidance only and may be varied, and provide for emergency extensions.

Operator consequence. For a Fedwire customer payment, 6:45 p.m. ET is the number to build into a payout calendar, not 7:00 p.m. On a day both systems are open, the published CHIPS close of 6:00 p.m. ET falls 45 minutes before that Fedwire customer deadline. Neither figure is the one you are held to: your bank's own cutoff sits in front of both, and the two rails run separate holiday calendars, so get your bank's cutoff in writing and get it per rail.

Why a bank routes over CHIPS at all

Liquidity is the usual explanation, and it is worth understanding because it shapes which of your payments tend to end up there.

Fedwire's gross settlement means each transfer is settled individually, for its full amount, across the sender's and receiver's master accounts — nothing is offset against anything else. CHIPS exists to need less funding for the same value: its mechanism "continuously evaluates payment flows and identifies opportunities to match and offset obligations among participants", and TCH puts the result at "$1 of funding into approximately $26 of settled payment value." That is a bank's economics, not yours. But it means high-value, correspondent-banking and cross-border USD flows — exactly the payments where an operator most needs a clean audit trail — are the ones with the strongest pull toward CHIPS.

The two systems are of comparable scale, on their own stated bases. Federal Reserve Financial Services reports Fedwire's 2025 average daily volume as 869,187 transfers and average daily value as $4,593,069 million — about $4.6 trillion per business day. The Clearing House reports CHIPS at "More than $2 trillion in average daily value cleared and settled" and "More than 630,000 transactions processed each business day". The bases differ — one is an annual statistics table, the other a current service page — so treat the comparison as order-of-magnitude.

Both run ISO 20022, and one has a deferred release

Both rails run ISO 20022 today. The Fedwire message types in the cutoff table above are ISO 20022 — pacs.008, pacs.009, pain.013 — and FRFS describes the result of its migration as formats that "now align with those used by other global, high-value payment systems". The Clearing House states that CHIPS "supports ISO 20022 messaging".

One date is worth keeping straight. FRFS announced on 27 August 2026 that "the November 2026 release has been rescheduled and will now occur in November 2027". It is a deferral of a future release, not of the migration itself; FRFS has said the scope of that release will be set out later. The wider context — Swift's own delay and what the other rails did — is in the MT103 to pacs.008 field-mapping reference. The ISO 20022 glossary entry has the message-family map.

What this reference does not establish

• CHIPS funding mechanics. How participants fund the system, and what happens to a queued payment at the end of the window, are matters for the CHIPS Rules and Administrative Procedures. This reference cites those rules for the operating schedule and the return-of-funds reference only; it does not set out the funding mechanics.
• Which CHIPS identifier reaches you. A payment reference does exist in the rules — the return-of-funds procedure requires a returning participant to quote the original payment's payment sequence number. What TCH does not state is which identifier, if any, a non-participant customer is given. (The service page's "UID Lookup" is routing reference data for participants, not a payment reference.) Ask your bank what it will give you.
• A current Fedwire participant count. The Board's page carries a 2008 figure, which is not cited. The eligibility rule is stated instead.
• Which rail your bank will pick for a given payment, and whether it will take an instruction from you. Neither rulebook addresses it, and bank wire agreements differ — the three cited here reserve the choice to the bank, but they are three named banks, not a general rule. Read your own agreement. The documentation above explains the pressures, not the outcome.

Operator checklist

1. Ask which rail, before you need to know. For any high-value or cross-border USD flow, get from your bank whether it originates on Fedwire, CHIPS as a direct participant, or CHIPS through a correspondent.
2. Demand the rail's reference, not the bank's. On Fedwire that is the IMAD/OMAD pair on every processed message. On CHIPS, establish with the participant what identifier it will provide.
3. Read CHIPS status as release, not submission. Until released, a CHIPS payment is not settled. Build your "has it settled" check on release confirmation.
4. Calendar the 6:45 p.m. ET Fedwire customer cutoff, not the 7:00 p.m. close. A customer transfer received after its cutoff is rejected unless the cutoff has been extended, so the fifteen minutes is the difference between today's business day and a resubmission tomorrow.
5. Read your own wire agreement on system selection. UCC Article 4A's default is that your bank follows an instruction naming a funds-transfer system; all three of the agreements cited here override it. Yours may too.
6. Know the CHIPS window, then get your bank's own cutoff in writing. The system window is published — 9:00 p.m. to 6:00 p.m. ET, in TCH's rulebook and PFMI disclosure — but the rules state those hours are guidance and may be varied, and your bank's internal cutoff sits in front of them.
7. Do not read the Fedwire November 2027 date as a format change in force. Fedwire runs on ISO 20022 today; November 2027 is a rescheduled future release whose scope FRFS has yet to publish.

Related references

• Weekend and holiday payment settlement — FedNow, RTP and the ACH clocks alongside these two.
• Tracing SWIFT payments: UETR and gpi status codes — the cross-border leg before a USD wire reaches either rail.
• MT103 to pacs.008 field mapping — the message types in the cutoff table.
• Settlement and netting — the two mechanisms this page contrasts.

Scope note

• Sources are the two operators and their supervisor. Fedwire claims come from the Board of Governors, Federal Reserve Financial Services and Operating Circular 6 (effective 5 January 2026). CHIPS claims come from The Clearing House's public service page and FAQ, its Rules and Administrative Procedures effective 4 June 2026, its PFMI public disclosure, and the Board's designated-FMU description. Two claims stand outside that. The default rule on a sender's routing instruction comes from UCC Article 4A, a model law adopted state by state; three named banks' published wire terms are cited as examples of contracting out of it, and nothing is generalised from them. Otherwise no secondary source supplies a mechanic either operator does not publish.
• CHIPS is described from its own documentation, service pages and rulebook alike. Where TCH states a figure or a behaviour, the article attributes it to TCH. Rule-level detail is drawn on only for the operating schedule and the return-of-funds payment reference; this is not a full account of the rules.
• This describes the current published position, not a history. Every statement is the position as at the access dates in the sources. The one dated event is the Fedwire release rescheduling, attributed to the FRFS announcement. Where FRFS's own page speaks of its "migration", the article repeats that word without asserting when it happened, because the page does not say.
• This is operator guidance, not legal advice. Finality and the allocation of loss on a failed or misdirected wire are governed by Regulation J, UCC Article 4A, the operators' rules and your bank's agreement. Confirm with your bank and counsel.