Insights Contact

Cross-Border and FX

SWIFT Cross-Border Payments, File by File: pain.001, pacs.008, MT, Rules and Security

By SP Sankar

⏱ About a 7-minute read. Click “Read more” or “Sample file” whenever you want the details.

Sree pays a contractor in India. Dollars leave Sree’s account in the US, and rupees arrive in India. Here is the journey, file by file.

  • 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 SWIFT payments work

In one line: Payments abroad. The bank changes the currency, the money hops through correspondent banks, and a UETR tracks it all the way.

CUSTOMERYOUR BANK · INTERNALOUTSIDE · EXTERNALCompanytreasurypays abroad (USD→INR)GatewaySFTP · SWIFTFileAct · APIValidate+ mapFX rate · feesto internal recordChecks+ postOFAC · AMLdebit accountSWIFTcorrespondentsForeignbankcredits in INRpain.001 · MT101 · APIpacs.008 (+ pacs.009 COV)pacs.008COMING BACKpacs.002 · gpi tracker · pacs.004pain.002 · UETR trackingReconcile: bank books vs networkNostro account = payments sentStatementcamt.053 (was MT940)settlement reportwhat the networksays movedMT103 retired Nov 22, 2025 · ISO 20022 (CBPR+) now · UETR tracks the payment end to endledger postings
SWIFT (cross-border): what comes in, what goes out, what comes back, and how the bank checks it all matches.
  • Coming in: a pain.001, an MT101 (until November 2026) or an API call.
  • Going out: a pacs.008, sometimes with a pacs.009 “cover” payment between the banks.
  • Coming back: a pacs.002, tracker updates, a pacs.004 for returns and camt.053 statements.

Status, rules, security and data

Status flowReceived → FX booked → Screened → Sent → With correspondent → Credited abroad
Side paths: Rejected, Held (sanctions query), Returned
Regulation and rulesSWIFT’s CBPR+ rules (ISO 20022 since November 22, 2025). OFAC sanctions. The Bank Secrecy Act travel rule. And Regulation E’s remittance rule when a consumer sends money abroad.
Security standardsSWIFT’s Customer Security Programme: every bank confirms each year that it meets SWIFT’s security controls.
Data governanceStructured addresses are becoming mandatory step by step. For every payment, keep the exchange rate, the fees and every bank in the chain.
Read more: SWIFT (cross-border)

For tech teams, product owners and testers

For developersBuild pacs.008 to the CBPR+ rules. Store the UETR and get tracker updates, either by asking or by being told. Link each currency deal to its payment.
For product ownersWho pays the fees (OUR, SHA or BEN), the currency margin, and what the client sees while a payment sits with a correspondent bank.
What to testAn unstructured address that gets rejected. A sanctions hold. A return in a different currency. Each fee option.

Step by step

  1. The company sends a pain.001 (or an older MT101, or an API call) in US dollars or rupees.
  2. The bank books the exchange rate and works out the fees.
  3. Sanctions and anti-money-laundering checks run.
  4. The bank sends a pacs.008 over SWIFT to its correspondent bank, sometimes with a pacs.009 cover payment. A UETR tracks it from start to finish.
  5. Each correspondent bank passes it along and may take a fee.
  6. The bank in India credits the contractor in rupees. Tracker updates show every step.
  7. The bank checks its nostro account (its account at the foreign bank) against camt.053 statements. Returns come back as pacs.004.

When things go wrong: rejected, returned, cancelled

Not every payment goes through. On SWIFT, there are three ways a payment can fail. Each one means something different for the money.

SWIFT: rejected, returned and cancelledRejectedin the chainA bank says noPayment is stoppedpacs.002Client is toldpain.002Returnedafter sendingBank abroad can’t postMoney comes backpacs.004Client is toldcamt.054Cancelledby the clientClient asks to stopcamt.055Bank sends recallcamt.056Other bank answerscamt.029Rejected = money never moved · Returned = money moved, then came back · Cancelled = stopped (or recalled) by the sender
Navy: the money never moved. Blue: it moved and came back. Grey: the sender stopped it.

Rejected. Any bank in the chain can reject the payment: the sending bank, a correspondent or the bank in India. The usual reasons are a missing or unstructured address, a missing purpose code, or a sanctions concern. The answer is a pacs.002 with RJCT, and the client fixes the details and tries again.

Returned. If the bank abroad can’t credit the account (wrong or closed), it sends the money back as a pacs.004. Because of fees and a different exchange rate on the way back, the client may get back less than they sent.

Cancelled. To stop a payment that is already on its way, the bank uses SWIFT gpi Stop and Recall. It sends a camt.056, and the bank that holds the money answers with a camt.029. If it agrees, the money returns as a pacs.004. The earlier you ask, the better the chance.

Codes you will see: AC01 wrong account · AC04 closed account · BE01 name doesn’t match · RR04 regulatory reason · CUST customer asked to cancel · DUPL duplicate

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.

PathFile or messageFrom → toWhat it says
Rejectedpacs.002 (RJCT)Any bank in the chain → previous bankRejected, with reason
Rejectedpain.002 (RJCT)Bank → clientFix the details and resend
Returnedpacs.004Bank abroad → correspondents → your bankMoney back, fees and FX may differ
Cancelledcamt.055Client → bankPlease stop my payment
Cancelledcamt.056, then camt.029 (gpi Stop and Recall)Bank ↔ banks in the chainRecall and the answer
Statementcamt.053 / camt.054Bank → clientShows the return on the account
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.055 company asks its bank to cancel

Fictional data, shortened. Real files carry more fields.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.055.001.08">
 <CstmrPmtCxlReq>
  <Assgnmt><Id>SREE-CXL-01</Id><CreDtTm>2026-11-20T10:55:00</CreDtTm></Assgnmt>
  <Undrlyg><OrgnlPmtInfAndCxl>
   <OrgnlPmtInfId>BATCH-01</OrgnlPmtInfId>
   <TxInf>
    <OrgnlEndToEndId>INV-7781</OrgnlEndToEndId>
    <OrgnlInstdAmt Ccy="USD">1250.50</OrgnlInstdAmt>
    <CxlRsnInf><Rsn><Cd>DUPL</Cd></Rsn></CxlRsnInf>
   </TxInf>
  </OrgnlPmtInfAndCxl></Undrlyg>
 </CstmrPmtCxlReq>
</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>
Sample file: camt.029 the answer

Fictional data, shortened. Real files carry more fields.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.029.001.09">
 <RsltnOfInvstgtn>
  <Assgnmt><Id>ANS-20261120-0019</Id><CreDtTm>2026-11-20T16:40:00</CreDtTm></Assgnmt>
  <Sts><Conf>RJCR</Conf></Sts>             <!-- RJCR = request refused, CNCL = accepted -->
  <CxlDtls><TxInfAndSts>
   <OrgnlEndToEndId>INV-7781</OrgnlEndToEndId>
   <CxlStsRsnInf><Rsn><Cd>NOAS</Cd></Rsn></CxlStsRsnInf>   <!-- payee did not answer -->
  </TxInfAndSts></CxlDtls>
 </RsltnOfInvstgtn>
</Document>

SWIFT 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.

StepFileCheckIf it goes wrongWho
1. Request arrivespain.001, MT101 or APIStructured address, purpose code, currency.Missing data? Reject with pain.002 now. A bank abroad will reject it later anyway.L2
2. FX and feesFX deal recordRate booked, fee option (OUR, SHA, BEN) shown to the client.Rate expired? Re-quote. Never send on an old rate.L2 with treasury
3. Sanctions and AMLScreening caseNo open hits.Possible match? Hold and work the case.L2 with compliance
4. Sendpacs.008 (+ pacs.009 cover)Sent with a UETR, accepted by the first correspondent.pacs.002 RJCT? Read the reason, fix with the client, resend once.L2
5. Trackgpi trackerPayment credited abroad within the expected time.Stuck with a correspondent? Ask through the tracker and tell the client what you know.L1 and L2
6. Returns and recallspacs.004, camt.056, camt.029Returns linked to the original; recalls chased.Return in another currency? Explain FX and fees to the client.L2
7. Reconcilecamt.053 nostro statementsEvery payment out matches the nostro account.Break? Open an item and own it.L2 with finance

Golden rules

  • Collect structured addresses up front. Most rejections start there.
  • Never send on an expired FX rate.
  • Keep the SWIFT CSP attestation current every year.
  • Tell the client what you know, even when it’s “still with the correspondent”.

Want the full picture, from building it to running it live? Read the Cross-Border SWIFT Payments Runbook.

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 clientWhich countries and currencies? Who pays the fees (OUR, SHA, BEN)? Do they need to see the exchange rate before sending? Can they give structured addresses?
Set up and connectivitypain.001 or API with currency fields, the flow for booking exchange rates, correspondent routing, access to the gpi tracker, and camt.053 for nostro or client statements.
Test and certifyTest the ISO 20022 (CBPR+) messages, sanctions holds, returns in another currency, and tracker updates.
Go-live and hypercareStart with one route, for example US dollars to Indian rupees. Follow each payment until it is credited abroad.
Where it usually breaksAddresses that are unstructured or incomplete. Missing purpose codes for the destination country. Fees nobody explained. Payments held over sanctions questions.

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.

pain.001: “please pay these people”

In one line: The company telling its bank, “please send these payments.” It can hold one payment or thousands.

  • How it starts: the company’s payments manager approves a payment run, such as Thursday’s payroll, and the company’s ERP or payroll system creates the file.
  • How it gets to the bank: by secure file transfer (SFTP), SWIFT FileAct, an upload on the bank’s portal, or an API call.
  • What is inside: a header with the file ID, the number of payments and the total. Then one or more payment blocks (date, which account pays, ACH or wire). Then one line for each person being paid.
  • What happens next: the bank sends a pain.002 back to say how it went. Then it creates one network message for each payment, such as a NACHA entry or a pacs.008.
Sample file: pain.001

Made-up data, shortened. Real files have more fields.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.09">
 <CstmrCdtTrfInitn>
  <GrpHdr>
   <MsgId>PAY-20261119-001</MsgId>
   <CreDtTm>2026-11-19T17:05:00</CreDtTm>
   <NbOfTxs>1</NbOfTxs>
   <CtrlSum>1250.50</CtrlSum>
   <InitgPty><Nm>Sree Corp</Nm></InitgPty>
  </GrpHdr>
  <PmtInf>
   <PmtInfId>BATCH-01</PmtInfId>
   <PmtMtd>TRF</PmtMtd>
   <PmtTpInf>
    <SvcLvl><Cd>NURG</Cd></SvcLvl>          <!-- NURG = ACH, URGP = wire -->
    <LclInstrm><Prtry>CCD</Prtry></LclInstrm>
   </PmtTpInf>
   <ReqdExctnDt><Dt>2026-11-20</Dt></ReqdExctnDt>
   <Dbtr><Nm>Sree Corp</Nm></Dbtr>
   <DbtrAcct><Id><Othr><Id>1112223334</Id></Othr></Id></DbtrAcct>
   <DbtrAgt><FinInstnId><ClrSysMmbId><MmbId>222333445</MmbId></ClrSysMmbId></FinInstnId></DbtrAgt>
   <CdtTrfTxInf>
    <PmtId><EndToEndId>INV-7781</EndToEndId></PmtId>
    <Amt><InstdAmt Ccy="USD">1250.50</InstdAmt></Amt>
    <CdtrAgt><FinInstnId><ClrSysMmbId>
      <ClrSysId><Cd>USABA</Cd></ClrSysId><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>
  </PmtInf>
 </CstmrCdtTrfInitn>
</Document>
Read more: pain.001

For tech teams, product owners and testers

For developersFirst check the file against the XSD (the official schema). Then check the business rules. NbOfTxs and CtrlSum must match the lines. The MsgId must be new, or it is a duplicate. The date must be a banking day. Finally, use SvcLvl and LclInstrm to pick the rail: NURG + CCD means ACH, URGP means wire.
For product ownersDecide which versions you accept (many US banks take pain.001.001.03 and .09). Set a cut-off time for each rail. And decide: does one bad line reject the whole file, or just that line?
What to testTotals that do not add up. The same MsgId sent twice. A date in the past. A bank holiday. A file with 10,000 lines. A name with & or accents. An amount with three decimals.

SWIFT MT: the older SWIFT messages

In one line: Short text messages made of tagged fields. ISO 20022 is replacing them, but you will still see them.

  • MT101: a company asks its bank to make a payment. It can be used alongside ISO 20022 until November 2026.
  • MT103: the classic cross-border customer payment. It was retired for payment instructions on 22 November 2025, and pacs.008 took its place.
  • MT940 and MT942: end-of-day and during-the-day statements. Many companies still use them.
Sample file: SWIFT MT

Made-up data, shortened. Real files have more fields.

Legacy MT103 (retired for payment instructions in Nov 2025, shown to compare)
:20:OUT000123
:23B:CRED
:32A:261120USD1250,50
:50K:/1112223334
SREE CORP 
:59:/9876543210
ACME SUPPLIES INC
:70:INVOICE INV-7781
:71A:SHA

MT940 statement (still common with corporates)
:20:STMT261120
:25:222333445/1112223334
:28C:00320/1
:60F:C261119USD50000,00
:61:2611201120D1250,50NTRFOUT000123//INV-7781
:86:WIRE TO ACME SUPPLIES INC
:62F:C261120USD48749,50
Read more: SWIFT MT

For tech teams, product owners and testers

For developersYou will see both formats for a while. Translate MT into your internal record the same way you do for pain.001. Watch out for cut-off text: MT lines only hold 35 characters.
For product ownersPlan how clients move from MT101 and MT940 to pain.001 and camt.053, and set a date when you stop accepting MT.
What to testCommas used as decimals (1250,50). Names that run over several lines. Characters SWIFT does not allow. The MT and ISO versions of the same payment should give the same result.

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 developersEvery 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 ownersBetter 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 testEach 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 developersMatch 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 ownersDecide what the customer sees at each status, and at what point you tell them the money is gone for good.
What to testA 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 developersA 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 ownersSet 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 testA 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.

camt.052, camt.053 and camt.054: reports and statements

In one line: How the bank tells the customer what came in and what went out.

  • camt.052: a report during the day, sent several times.
  • camt.053: the end-of-day statement, with opening and closing balances.
  • camt.054: a notice for each debit or credit, sent as it happens.
  • Each line is either BOOK (posted) or PDNG (pending).
Sample file: camt.052, camt.053 and camt.054

Made-up data, shortened. Real files have more fields.

<!-- camt.054: one notice, sent as soon as the account is debited -->
<BkToCstmrDbtCdtNtfctn>
 <Ntfctn>
  <Acct><Id><Othr><Id>1112223334</Id></Othr></Id></Acct>
  <Ntry>
   <Amt Ccy="USD">1250.50</Amt>
   <CdtDbtInd>DBIT</CdtDbtInd>
   <Sts><Cd>BOOK</Cd></Sts>
   <BookgDt><Dt>2026-11-20</Dt></BookgDt>
   <ValDt><Dt>2026-11-20</Dt></ValDt>
   <NtryDtls><TxDtls><Refs><EndToEndId>INV-7781</EndToEndId></Refs></TxDtls></NtryDtls>
  </Ntry>
 </Ntfctn>
</BkToCstmrDbtCdtNtfctn>

<!-- camt.053: the end-of-day statement adds opening and closing balances -->
<Bal><Tp><CdOrPrtry><Cd>OPBD</Cd></CdOrPrtry></Tp><Amt Ccy="USD">50000.00</Amt><CdtDbtInd>CRDT</CdtDbtInd></Bal>
<Bal><Tp><CdOrPrtry><Cd>CLBD</Cd></CdOrPrtry></Tp><Amt Ccy="USD">48749.50</Amt><CdtDbtInd>CRDT</CdtDbtInd></Bal>
Read more: camt.052, camt.053 and camt.054

For tech teams, product owners and testers

For developersPut the customer’s EndToEndId and the bank’s reference on every entry. That is what the customer’s ERP uses to match payments. Use the standard bank transaction codes (BkTxCd).
For product ownersPick the format and timing for each type of client. For example, camt.053 for large companies, BAI2 for others and PDF for small businesses.
What to testOpening balance plus entries equals the closing balance. A reversal. A pending entry that books later. A day with no activity (the statement should still go out).

Read next

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