camt.056 — FI to FI Payment Cancellation Request
A bank asks a correspondent to cancel a payment previously routed. Core of SWIFT gpi for Stop and Recall (gSRP) — financial community anti-fraud response tool since 2018.
Purpose: request cancellation
camt.056 is used when a payment has already been sent and must be stopped or recovered. Typical cases: APP fraud (Authorised Push Payment), data-entry error, late duplication detection. The request is routed through the SWIFTNet gpi chain following the UETR ; each bank along the way reacts depending on local status (settled or not).
XML structure
Wrapped in <FIToFIPmtCxlReq>. Assgnmt (who asks whom) + Undrlyg/TxInf (targeted payment).
| Element | Role |
|---|---|
Assgnmt | Assigner/Assignee of the request (BICs of involved banks). |
OrgnlGrpInf | Original payment reference and msg type. |
OrgnlUETR | UUIDv4 — key for gpi tracker. |
CxlRsnInf/Rsn/Cd | Reason code (FRAD, DUPL, CUST, TECH, AGNT). |
CxlRsnInf/AddtlInf | Free context description (max 105 characters × 1 line). |
Example: fraud cancellation
BNP Paribas asks Citi US to cancel a pacs.008 of 75,000 USD after customer reported APP fraud 2 hours after send:
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.056.001.08">
<FIToFIPmtCxlReq>
<Assgnmt>
<Id>CXL-FRAUD-20260518-001</Id>
<Assgnr><Agt><FinInstnId><BICFI>BNPAFRPP</BICFI></FinInstnId></Agt></Assgnr>
<Assgne><Agt><FinInstnId><BICFI>CITIUS33</BICFI></FinInstnId></Agt></Assgne>
<CreDtTm>2026-05-18T16:45:00+02:00</CreDtTm>
</Assgnmt>
<Undrlyg>
<TxInf>
<CxlId>CXL-001</CxlId>
<OrgnlGrpInf>
<OrgnlMsgId>BNPP-CBPR-20260518-009</OrgnlMsgId>
<OrgnlMsgNmId>pacs.008.001.10</OrgnlMsgNmId>
</OrgnlGrpInf>
<OrgnlInstrId>BNPP-INSTR-2026009</OrgnlInstrId>
<OrgnlEndToEndId>INV2026-FRAUD-9999</OrgnlEndToEndId>
<OrgnlUETR>fffeeeeddddccccbbbbaaaa99998888</OrgnlUETR>
<OrgnlIntrBkSttlmAmt Ccy="USD">75000.00</OrgnlIntrBkSttlmAmt>
<OrgnlIntrBkSttlmDt>2026-05-18</OrgnlIntrBkSttlmDt>
<CxlRsnInf>
<Rsn><Cd>FRAD</Cd></Rsn>
<AddtlInf>Customer reported APP fraud at 14:30 ; freeze and recall requested URGENT</AddtlInf>
</CxlRsnInf>
</TxInf>
</Undrlyg>
</FIToFIPmtCxlReq>
</Document>Common pitfalls
- FRAD code not used: for APP fraud cases, FRAD must absolutely be used — triggers priority freeze protocols on the correspondent side.
- Empty OrgnlUETR: without UETR, the gpi chain cannot trace the transaction — cancellation impossible.
- Too long delay: if the pacs.008 is already settled at the beneficiary, fund recall depends on the debited party's agreement — gSRP can only request.
- Confusion with pacs.007: pacs.007 = reversal initiated by the creditor itself ; camt.056 = request to another bank to cancel.