CHIPS is a private U.S. dollar clearing and settlement system. Learn how payment release, netting, prefunding, finality, and bank posting differ.
CHIPS, or the Clearing House Interbank Payments System, is a private-sector clearing and settlement system for eligible large-value U.S. dollar payments between participating financial institutions. Operated by The Clearing House, CHIPS continuously evaluates payment instructions and releases them with final settlement when its funding, position, priority, and netting conditions are met.
CHIPS supports domestic and cross-border dollar payments, but it is not a foreign-exchange market, customer bank account, or messaging-only network. It settles the interbank CHIPS leg. A payer’s account debit, a beneficiary’s account credit, a currency conversion, and invoice reconciliation occur on other records and may have different timestamps.
CHIPS provides a common system in which participating institutions can submit, store, prioritize, release, receive, and settle qualifying U.S. dollar payment messages. Common contexts include commercial payments, bank treasury transfers, institutional transactions, correspondent banking, and the dollar leg of cross-border payments.
The system addresses three connected problems:
CHIPS does not decide whether an invoice is valid, perform the foreign-exchange conversion for a multicurrency transaction, hold ordinary customer deposits, or guarantee when a beneficiary bank makes funds available to its customer. Those questions require contracts, customer ledgers, correspondent records, and applicable law outside the CHIPS system.
| Party or record | Role in the payment chain | Evidence to examine |
|---|---|---|
| Originator | Instructs its bank to make the underlying payment | Customer instruction, authorization, purpose, amount, currency, and requested value date |
| Originator’s bank or intermediary | Converts the customer request into the applicable interbank route | Customer debit, compliance review, payment message, route, and fee record |
| Sending CHIPS participant | Delivers a CHIPS payment message for storage and release | Participant identifier, message reference, amount, priority, delivery time, and release status |
| The Clearing House | Operates CHIPS and applies its release, position, funding, netting, and settlement rules | System acknowledgement, stored or released status, position reports, finality record, and exception notices |
| Receiving CHIPS participant | Receives the released payment message and acts under the applicable payment chain | Receipt, participant credit, onward instruction, beneficiary identification, and customer posting |
| Funding participant | Funds its own position and, where designated, may support a nonfunding participant | Opening and supplemental funding, current position, closing requirement, and payout record |
| Beneficiary bank | Holds or services the beneficiary’s account, directly or after another intermediary | Incoming instruction, screening or repair, account credit, value date, and funds-availability status |
| Beneficiary | Receives and applies the payment | Bank statement, remittance detail, invoice, receivables ledger, and exception correspondence |
The sending or receiving CHIPS participant may also be the originator’s or beneficiary’s bank, but it need not be. A bank that does not participate directly can access CHIPS through a correspondent or respondent relationship with a participant. As a result, the name on the customer’s statement may differ from the institution shown as the direct CHIPS sender or receiver.
flowchart TD
A["Originator gives its bank a USD payment instruction"] --> B["Bank selects CHIPS and creates the payment message"]
B --> C["Sending participant delivers the message to CHIPS"]
C --> D["CHIPS stores and continuously evaluates the message"]
D --> E["Funding, positions, priority, and netting conditions permit release"]
E --> F["CHIPS releases and finally settles the participant obligation"]
F --> G["Receiving participant processes the payment or sends it onward"]
G --> H["Beneficiary bank posts the customer credit"]
H --> I["Beneficiary matches the receipt to the invoice"]
This is a simplified payment chain. A real transfer may include more intermediaries, repairs, sanctions screening, correspondent accounts, foreign-exchange activity, and internal bank queues.
The sequence matters because several statements can be true at different times:
Only the relevant evidence can establish each stage. A bank confirmation reading “sent” is not necessarily a CHIPS finality record, and a CHIPS release does not by itself show the beneficiary’s available balance.
Current CHIPS rules allow a participant to deliver a payment message for storage and release. A stored message can generally be deleted by the sending participant before release, subject to the rules and system timing. After CHIPS releases the message, the sending participant cannot delete it.
Release has specific legal and operational significance under the system rules:
This does not mean that every attempted customer payment is impossible to return. A receiving bank or beneficiary may send a new return payment under applicable law, agreement, compliance requirements, or consent. That is a separate transaction. It does not reverse history by turning the original released CHIPS payment into an unreleased message.
When investigating a cancellation request, ask whether the original message is still stored, has been released, or has already produced later customer-account entries. “Recall requested” is not the same as “payment recovered.”
CHIPS uses a prefunded balance structure linked to participant positions. Under the current rules, the CHIPS prefunded balance account is maintained at the Federal Reserve Bank of New York for the joint benefit of CHIPS funding participants. Funding participants transfer required funds directly or through applicable arrangements, while a nonfunding participant designates a funding participant.
CHIPS tracks system positions as payment messages settle. Its release methodology is designed to prevent a participant’s position from falling below applicable limits. Participants can also provide supplemental funding and use priority and liquidity controls under the current rules.
Three distinctions are important:
| Concept | Meaning | Common error |
|---|---|---|
| Customer deposit | Liability of a commercial bank to its customer | Treating the customer’s balance as if it were held in the CHIPS prefunded account |
| CHIPS participant position | System record that changes as payment messages are released and settled | Treating a positive position as a named customer’s payment |
| Prefunded balance account | Special account at the New York Fed supporting CHIPS funding and payout arrangements | Saying CHIPS owns or can use the funds as ordinary corporate cash |
| Federal Reserve master account | Account relationship used by an eligible institution for Federal Reserve services | Assuming every CHIPS participant necessarily funds directly from its own master account |
The prefunded structure supports settlement, but it does not make CHIPS identical to Fedwire. CHIPS records and settles participant obligations under CHIPS rules using its position and netting methodology; Fedwire settles each processed transfer individually by debiting and crediting Federal Reserve accounts.
Suppose three participants have these simplified payment instructions:
| Instruction | Amount |
|---|---|
| Bank A pays Bank B | $10 million |
| Bank B pays Bank C | $9 million |
| Bank C pays Bank A | $8 million |
| Gross payment value | $27 million |
If all three obligations can be offset, their simplified net positions are:
| Participant | Receives | Sends | Simplified net position |
|---|---|---|---|
| Bank A | $8 million | $10 million | -$2 million |
| Bank B | $10 million | $9 million | +$1 million |
| Bank C | $9 million | $8 million | +$1 million |
The instructions carry $27 million of gross value, while the combined simplified net debit is $2 million. That difference illustrates why matching offsetting obligations can reduce liquidity use.
Actual CHIPS settlement is not a once-a-day spreadsheet net. The system continuously evaluates stored messages and can release individual, bilateral, or multilateral combinations as permitted by current positions, funding, priorities, and system rules. A payment may settle quickly when conditions allow or remain stored while the system seeks a valid release opportunity. The example explains the arithmetic, not the actual release algorithm or one participant’s funding requirement.
Current CHIPS rules distinguish urgent, preferred, and nonpriority payment messages. Participants can apply or change a priority designation before a stored message is released, subject to the rules and system procedures. The release methodology considers priority while also accounting for positions and opportunities to increase the number or value of payments that can settle.
Priority does not mean unconditional immediate release. A time-sensitive message still depends on valid data, system acceptance, available liquidity, position constraints, and the applicable release methodology. Conversely, holding every payment for maximum netting could conflict with customer deadlines and risk controls.
Bank treasury and payment teams therefore manage a tradeoff:
A useful performance review looks beyond average settlement speed. It considers stored-payment aging, urgent-payment release, liquidity use, repair rates, operating incidents, closing requirements, and whether customers received accurate status information.
CHIPS finality applies to the settled obligation between its sending and receiving participants. The customer payment chain can extend beyond those two participants.
For example, the receiving participant may need to:
Federal Reserve research distinguishes CHIPS and Fedwire interbank settlement from newer instant-payment systems whose rules address immediate end-user credit and funds availability. Therefore, “settled on CHIPS” and “available to the beneficiary” should not be used as synonyms.
For accounting purposes, the payer may record cash leaving before the payee records cash received. Each party should apply its accounting policy to reliable bank and settlement evidence rather than assuming one universal timestamp.
Assume a company outside the United States owes a U.S. supplier USD 4.2 million. The buyer instructs its local bank to pay the supplier. The local bank uses a U.S. dollar correspondent that participates in CHIPS, and the supplier’s bank receives the CHIPS payment.
| Stage | Evidence | What it establishes |
|---|---|---|
| Invoice approval | Supplier invoice and buyer approval for USD 4.2 million | Commercial obligation and authorized amount |
| Currency conversion | FX trade confirmation, if the buyer funds in another currency | Exchange rate, currency amount, spread, and settlement date outside CHIPS |
| Customer instruction | Buyer’s bank payment order | Beneficiary, bank route, amount, fees, and requested value date |
| CHIPS delivery | Sending participant’s message reference and timestamp | Message submitted to CHIPS, but not necessarily released |
| CHIPS settlement | Released status and participant finality record | Interparticipant dollar obligation settled under CHIPS rules |
| Beneficiary posting | Supplier-bank statement credit | Supplier’s bank account credited |
| Receivables application | Supplier ledger applies USD 4.2 million to the invoice | Commercial balance reduced or closed |
If CHIPS has settled but the supplier cannot see the credit, the investigation should move downstream. The receiving participant may not be the final beneficiary bank, or the beneficiary bank may be repairing, screening, or posting the payment.
If the supplier receives less than USD 4.2 million, compare the original fee instruction, intermediary deductions, correspondent entries, and beneficiary-bank charges. CHIPS settlement of a stated interparticipant amount does not explain every fee elsewhere in the payment chain.
| Feature | CHIPS | Fedwire Funds Service | SWIFT | Correspondent banking |
|---|---|---|---|---|
| Primary function | Clears and settles eligible USD payments | Transmits and settles individual transfers | Exchanges standardized financial messages | Provides bilateral bank relationships and account access |
| Operator or arrangement | The Clearing House | Federal Reserve Banks | SWIFT cooperative | Contract between correspondent and respondent institutions |
| Settlement approach | Prefunded positions plus liquidity-saving netting and intraday finality | Real-time gross settlement in Federal Reserve accounts | No settlement merely from message delivery | Debit and credit entries on correspondent accounts or through another system |
| Currency scope | U.S. dollars | U.S. dollars | Messages can describe many currencies and products | Depends on the accounts and services offered |
| Critical status | Message released and finally settled | Transfer processed, final, and irrevocable | Message acknowledged or delivered | Correspondent account entry and onward processing |
| Customer-credit proof | Separate beneficiary-bank evidence required | Separate beneficiary-bank evidence may still be required | Separate clearing, settlement, and bank evidence required | Separate beneficiary posting and reconciliation required |
One payment can involve all four. SWIFT can carry instructions; a correspondent can provide access; CHIPS can settle the eligible dollar obligation between participants; and Fedwire can support separate funding or another leg. The system named on one record should not be assumed to describe the entire route.
CHIPS supports ISO 20022 messaging. Structured data can improve automated validation, compliance workflows, straight-through processing, and reconciliation when institutions populate and preserve it correctly.
ISO 20022 does not itself settle a payment or guarantee accurate data. A valid message can still contain an incorrect beneficiary, duplicate invoice reference, wrong amount, or payment purpose that requires review. Current CHIPS rules also make clear that ISO 20022 terminology does not by itself create or change the legal relationships among payment parties.
Operational teams should validate identifiers, beneficiary details, remittance information, purpose data, duplicate controls, and sanctions-screening inputs before submission. Finance teams should preserve structured remittance data through to the receivables ledger instead of reducing the payment to an amount and date only.
Netting and prefunding reduce specific liquidity and credit exposures; they do not eliminate operational, legal, fraud, compliance, or customer-posting risk.
Operator pages summarize the system but do not prove the status of a particular payment. Transaction-specific conclusions require participant messages, CHIPS reports, correspondent entries, customer statements, and current legal or contractual analysis.
This article provides general financial education. It is not payment-operation, treasury, liquidity, accounting, legal, sanctions, cybersecurity, compliance, or transaction-recovery advice. Institutions and customers should use current system rules, bank records, contractual terms, and qualified professional guidance for a specific payment.