
⏱ About a 5-minute read. Click “Read more” or “Sample file” whenever you want the details.
Sree’s company is receiving a large dollar payment from a buyer abroad. On its way, the money passes through CHIPS, the large-payment system run by The Clearing House (a group owned by big banks).
- Not a banker? Just look at the pictures and read the “In one line” boxes. That is enough to get the idea.
- Work in banking or operations? Open “Read more” under each file and each payment type.
- Product owner? Read the status codes, the “Status, rules, security and data” boxes and the product owner rows. Those are the decisions that land on your desk.
- Developer? Open every “Sample file”, then read the data mapping section and the developer rows.
- Operations or support? Use the runbook table: what to watch at each file, and who acts.
- Tester? Use the “What to test” rows as your starting checklist.
- Forward deployed engineer? Jump to “For forward deployed engineers”. It covers what to ask the client, set-up, testing, go-live and where things usually go wrong.
How CHIPS works
In one line: The Clearing House’s system for large payments. Payments are offset against each other, so banks need less cash to make them.
- Coming in: a pain.001, a SWIFT message or an API call, often for international dollar payments.
- Going out: a pacs.008 or pacs.009 to CHIPS.
- Coming back: a pacs.002 and, if needed, a pacs.004 return.
Status, rules, security and data
| Status flow | Sent → Queued → Released (netted) → Final Side paths: Rejected, Returned |
| Regulation and rules | The CHIPS Rules and Administrative Procedures. UCC Article 4A, under New York law. OFAC sanctions. And the travel rule. |
| Security standards | The Clearing House sets connectivity and security requirements for its participants, and they must test before going live. |
| Data governance | CHIPS moved to ISO 20022 in April 2024. Keep the full message, because correspondent banks may need it for investigations. |
Read more: CHIPS
For tech teams, product owners and testers
| For developers | Use the same pacs formatter as Fedwire, with the CHIPS-specific rules on top. Handle payments still waiting in the queue near the end of the day. |
| For product owners | Decide for each payment whether it goes by CHIPS or Fedwire, based on cost, cash needs and timing. |
| What to test | A payment still in the queue at the end of the day. Routing through a member bank. Very long remittance details. |
Step by step
- The instruction reaches a CHIPS member bank as a pain.001, a SWIFT message or an API call. Often it is a dollar payment for a foreign bank.
- Approvals and sanctions screening run.
- The bank sends a pacs.008 or pacs.009 to CHIPS.
- CHIPS holds payments in a queue. It releases them by matching them against payments going the other way, using money each bank put in at the start of the day. This is called netting.
- Once a payment is released, it is final. A pacs.002 confirms it.
- At the end of the day, whatever is left over is settled, and each bank checks its CHIPS position.
When things go wrong: rejected, returned, cancelled
Not every payment goes through. On CHIPS, there are three ways a payment can fail. Each one means something different for the money.
Rejected. The bank or CHIPS can refuse a payment before it is released, for example for sanctions, a bad message or wrong routing. Nothing settles, and the client gets a pacs.002 with the reason.
Returned. A released CHIPS payment is final. If the receiving bank can’t apply it, it sends the money back as a new payment (pacs.004) linked to the original, and the sending bank credits its client.
Cancelled. While a payment is still waiting in the CHIPS queue, the sending bank can delete it. Once it is released, the only option is a recall request (camt.056), and the other bank decides.
Codes you will see: AC04 closed account · AC01 wrong account · RR04 regulatory reason · FOCR returned after a recall request
Which files carry the bad news?
Each path has its own file or message. Here is what travels, who sends it, and what is inside.
| Path | File or message | From → to | What it says |
|---|---|---|---|
| Rejected | pacs.002 (RJCT) | CHIPS or bank → sending bank | Payment refused, with reason |
| Returned | pacs.004 | Receiving bank → CHIPS → sending bank | Money sent back, linked to the original |
| Cancelled | Delete request for a queued payment | Sending bank → CHIPS | Remove it before it is released |
| Cancelled | camt.056, then camt.029 | Bank ↔ bank | Recall request and the answer |
Sample file: pacs.002 with RJCT
Fictional data, shortened. Real files carry more fields.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10">
<FIToFIPmtStsRpt>
<GrpHdr><MsgId>FED-STS-88120</MsgId><CreDtTm>2026-11-20T10:02:11</CreDtTm></GrpHdr>
<TxInfAndSts>
<OrgnlInstrId>SND-20261120-0007</OrgnlInstrId>
<OrgnlEndToEndId>INV-7781</OrgnlEndToEndId>
<OrgnlUETR>3f1c9d2e-7b4a-4c1e-9a55-2d8e6f0b1a77</OrgnlUETR>
<TxSts>RJCT</TxSts>
<StsRsnInf><Rsn><Cd>AC04</Cd></Rsn></StsRsnInf> <!-- account closed -->
</TxInfAndSts>
</FIToFIPmtStsRpt>
</Document>Sample file: pacs.004 payment return
Fictional data, shortened. Real files carry more fields.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.004.001.10">
<PmtRtr>
<GrpHdr>
<MsgId>RTN-20261120-0031</MsgId><CreDtTm>2026-11-20T14:20:00</CreDtTm>
<NbOfTxs>1</NbOfTxs><SttlmInf><SttlmMtd>CLRG</SttlmMtd></SttlmInf>
</GrpHdr>
<TxInf>
<RtrId>RTN-0031-1</RtrId>
<OrgnlInstrId>SND-20261120-0007</OrgnlInstrId>
<OrgnlEndToEndId>INV-7781</OrgnlEndToEndId> <!-- links to the original -->
<OrgnlUETR>3f1c9d2e-7b4a-4c1e-9a55-2d8e6f0b1a77</OrgnlUETR>
<RtrdIntrBkSttlmAmt Ccy="USD">1250.50</RtrdIntrBkSttlmAmt>
<IntrBkSttlmDt>2026-11-20</IntrBkSttlmDt>
<RtrRsnInf><Rsn><Cd>AC04</Cd></Rsn></RtrRsnInf> <!-- account closed -->
</TxInf>
</PmtRtr>
</Document>Sample file: camt.056 “please return it”
Fictional data, shortened. Real files carry more fields.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.056.001.08">
<FIToFIPmtCxlReq>
<Assgnmt>
<Id>CXL-20261120-0004</Id>
<Assgnr><Agt><FinInstnId><ClrSysMmbId><MmbId>222333445</MmbId></ClrSysMmbId></FinInstnId></Agt></Assgnr>
<Assgne><Agt><FinInstnId><ClrSysMmbId><MmbId>123456780</MmbId></ClrSysMmbId></FinInstnId></Agt></Assgne>
<CreDtTm>2026-11-20T11:15:00</CreDtTm>
</Assgnmt>
<Undrlyg><TxInf>
<CxlId>CXL-0004-1</CxlId>
<OrgnlEndToEndId>INV-7781</OrgnlEndToEndId>
<OrgnlUETR>3f1c9d2e-7b4a-4c1e-9a55-2d8e6f0b1a77</OrgnlUETR>
<OrgnlIntrBkSttlmAmt Ccy="USD">1250.50</OrgnlIntrBkSttlmAmt>
<CxlRsnInf><Rsn><Cd>DUPL</Cd></Rsn></CxlRsnInf> <!-- sent twice by mistake -->
</TxInf></Undrlyg>
</FIToFIPmtCxlReq>
</Document>CHIPS runbook: what to watch at each file
This is the day-to-day runbook for the files above, in the same order. For each step: the file you are looking at, what “good” looks like, what to do when it isn’t, and who acts. L1 is the service desk, L2 is payment operations and app support, and L3 is engineering.
| Step | File | Check | If it goes wrong | Who |
|---|---|---|---|---|
| 1. Payment arrives | pain.001, SWIFT or API | Complete data, routing to the right CHIPS member. | Wrong routing? Fix it in the payment hub, or reject with a reason. | L2 |
| 2. Checks | Internal record | Approval, sanctions and limits passed. | Possible sanctions match? Hold and work the case. | L2 with compliance |
| 3. Send to CHIPS | pacs.008 or pacs.009 | CHIPS accepted it into the queue. | Rejected? Read the pacs.002 reason, fix, resend once. | L2 |
| 4. Watch the queue | CHIPS queue view | Payments are released through the day, not piling up. | Big payment stuck? Talk to treasury about pre-funding, or move it to Fedwire. | L2 with treasury |
| 5. End of day | Final settlement report | Nothing left in the queue that should have gone. | Payments left at close? Decide: Fedwire now, or next day with the client told. | L2 with treasury |
| 6. Returns and recalls | pacs.004, camt.056, camt.029 | Every return linked to the original payment. | Unanswered recall? Chase the other member bank. | L2 |
Golden rules
- A released CHIPS payment is final.
- Watch the queue before the end of the day, not at the end of the day.
- Never resend before you know CHIPS didn’t accept the first one.
Want the full picture, from building it to running it live? Read the Wire Payments Runbook (Fedwire and CHIPS).
For forward deployed engineers (FDE)
As an FDE, you sit with the client and make the integration actually work. Here is your checklist for this rail.
| First call with the client | Is the client a CHIPS member, or using a member bank? Which payments should go by CHIPS and which by Fedwire (cost, timing)? |
| Set up and connectivity | Routing rules in the payment hub, CHIPS connectivity at the member bank, and who to call about liquidity and pre-funding. |
| Test and certify | Test in The Clearing House’s environment. Try payments that are still queued near the end of the day, and routing through correspondent banks. |
| Go-live and hypercare | On day one, watch the queue and the released payments. Agree who makes the end-of-day calls about cash. |
| Where it usually breaks | Payments left in the queue at closing time. Routing to the wrong member bank. Data lost when converting from older formats. |
The files on this rail
Each file below shows how it starts, what is inside, its status codes and a sample. For all the other files, see the full guide: how payment files are processed in US banks.
pacs.008 and pacs.009: bank-to-bank payment
In one line: The message one bank sends to the network to move money. pacs.008 is for a customer’s payment. pacs.009 is when the bank pays for itself.
- How it starts: your bank creates it once all checks pass. It is built from the bank’s own internal payment record, not copied from the customer’s file.
- Who uses it: Fedwire, CHIPS, RTP, FedNow and SWIFT for cross-border payments.
- What is inside: the amount, the settlement date, the sending and receiving banks, who pays, who gets paid, the customer’s EndToEndId and a UETR (a unique tracking ID).
Sample file: pacs.008 and pacs.009
Made-up data, shortened. Real files have more fields.
<!-- Business Application Header (head.001) is sent with it -->
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.008.001.08">
<FIToFICstmrCdtTrf>
<GrpHdr>
<MsgId>20261120BANKOUT000123</MsgId><CreDtTm>2026-11-20T10:01:07</CreDtTm>
<NbOfTxs>1</NbOfTxs>
<SttlmInf><SttlmMtd>CLRG</SttlmMtd></SttlmInf>
</GrpHdr>
<CdtTrfTxInf>
<PmtId>
<InstrId>OUT-000123</InstrId>
<EndToEndId>INV-7781</EndToEndId> <!-- from the customer -->
<UETR>8a562c67-ca16-48ba-b074-65581be6f001</UETR>
</PmtId>
<IntrBkSttlmAmt Ccy="USD">1250.50</IntrBkSttlmAmt>
<IntrBkSttlmDt>2026-11-20</IntrBkSttlmDt>
<ChrgBr>SLEV</ChrgBr>
<InstgAgt><FinInstnId><ClrSysMmbId><MmbId>222333445</MmbId></ClrSysMmbId></FinInstnId></InstgAgt>
<InstdAgt><FinInstnId><ClrSysMmbId><MmbId>123456780</MmbId></ClrSysMmbId></FinInstnId></InstdAgt>
<Dbtr><Nm>Sree Corp</Nm>
<PstlAdr><TwnNm>Edison</TwnNm><CtrySubDvsn>NJ</CtrySubDvsn><Ctry>US</Ctry></PstlAdr></Dbtr>
<DbtrAcct><Id><Othr><Id>1112223334</Id></Othr></Id></DbtrAcct>
<DbtrAgt><FinInstnId><ClrSysMmbId><MmbId>222333445</MmbId></ClrSysMmbId></FinInstnId></DbtrAgt>
<CdtrAgt><FinInstnId><ClrSysMmbId><MmbId>123456780</MmbId></ClrSysMmbId></FinInstnId></CdtrAgt>
<Cdtr><Nm>Acme Supplies Inc.</Nm></Cdtr>
<CdtrAcct><Id><Othr><Id>9876543210</Id></Othr></Id></CdtrAcct>
<RmtInf><Ustrd>Invoice INV-7781</Ustrd></RmtInf>
</CdtTrfTxInf>
</FIToFICstmrCdtTrf>
</Document>Read more: pacs.008 and pacs.009
For tech teams, product owners and testers
| For developers | Every network has its own rules for which fields are allowed, how long they can be and which characters are OK. Write one formatter per network, all fed from the same internal record. Keep a copy of the exact message you sent, for audit. |
| For product owners | Better data, such as structured addresses and remittance details, means fewer false sanctions alerts and easier reconciliation. Decide how much of it your clients must give you. |
| What to test | Each network’s required fields. Very long names and addresses. A missing UETR. A duplicate InstrId. A message sent after the network’s cut-off. |
pacs.002: the network’s answer
In one line: The network’s answer about a bank-to-bank payment: accepted, settled, or rejected (with a reason).
- How it starts: the network or the receiving bank sends it back. On instant rails it takes seconds. On wires it takes minutes.
- Statuses: ACSC (settled), ACSP (in progress), ACWP (accepted, waiting to be posted) and RJCT (rejected, with a reason such as AC04, closed account).
Sample file: pacs.002
Made-up data, shortened. Real files have more fields.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10">
<FIToFIPmtStsRpt>
<GrpHdr><MsgId>NET-ACK-778899</MsgId><CreDtTm>2026-11-20T10:01:09</CreDtTm></GrpHdr>
<TxInfAndSts>
<OrgnlInstrId>OUT-000123</OrgnlInstrId>
<OrgnlEndToEndId>INV-7781</OrgnlEndToEndId>
<OrgnlUETR>8a562c67-ca16-48ba-b074-65581be6f001</OrgnlUETR>
<TxSts>ACSC</TxSts> <!-- or RJCT with <StsRsnInf><Rsn><Cd>AC04</Cd> -->
</TxInfAndSts>
</FIToFIPmtStsRpt>
</Document>Read more: pacs.002
For tech teams, product owners and testers
| For developers | Match it to the message you sent using OrgnlInstrId, OrgnlEndToEndId or OrgnlUETR. Be ready for statuses that arrive late, twice, or in the wrong order. |
| For product owners | Decide what the customer sees at each status, and at what point you tell them the money is gone for good. |
| What to test | A reject after a timeout. An answer that never arrives. Two answers for one payment. A reject reason you have never seen before. |
camt.056, camt.029 and pacs.004: asking for money back
In one line: How one bank asks another to send a payment back, and how the money returns.
- How it starts: the customer or the bank spots a mistake, such as a duplicate, a wrong amount or fraud, and asks for a recall.
- camt.056 says “please return this payment.” camt.029 is the answer, and it is often “no.” pacs.004 is the money actually coming back, linked to the original payment.
- Remember: wires and instant payments are final. The other bank does not have to say yes.
Sample file: camt.056, camt.029 and pacs.004
Made-up data, shortened. Real files have more fields.
<!-- Step 1: the sending bank asks for the money back (camt.056) -->
<FIToFIPmtCxlReq>
<Undrlyg><TxInf>
<CxlId>CXL-0042</CxlId>
<OrgnlEndToEndId>INV-7781</OrgnlEndToEndId>
<OrgnlUETR>8a562c67-ca16-48ba-b074-65581be6f001</OrgnlUETR>
<CxlRsnInf><Rsn><Cd>DUPL</Cd></Rsn></CxlRsnInf> <!-- sent twice by mistake -->
</TxInf></Undrlyg>
</FIToFIPmtCxlReq>
<!-- Step 2a: the other bank says no (camt.029) ... -->
<!-- Step 2b: ... or sends the money back (pacs.004) -->
<PmtRtr>
<TxInf>
<RtrId>RTN-5511</RtrId>
<OrgnlEndToEndId>INV-7781</OrgnlEndToEndId>
<OrgnlUETR>8a562c67-ca16-48ba-b074-65581be6f001</OrgnlUETR>
<RtrdIntrBkSttlmAmt Ccy="USD">1250.50</RtrdIntrBkSttlmAmt>
<RtrRsnInf><Rsn><Cd>FOCR</Cd></Rsn></RtrRsnInf> <!-- following cancellation request -->
</TxInf>
</PmtRtr>Read more: camt.056, camt.029 and pacs.004
For tech teams, product owners and testers
| For developers | A pacs.004 has to find the original payment using its EndToEndId and UETR. Then it reverses the posting and updates the status. The amount that comes back can be smaller if fees were taken. |
| For product owners | Set up the recall process: who can ask for one, how fast it happens, and how the customer is told. With fraud, every minute counts. |
| What to test | A recall that is accepted. One that is refused. A partial return. A return for a payment you cannot find. A return in a different currency. |
Read next
- All payment files, one by one (pain.001, pain.002, pain.008, NACHA, ISO 20022)
- Related runbook on this site
Sources: Federal Reserve Financial Services; The Clearing House; Nacha Operating Rules; Swift. Sample files are fictional and shortened.
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