camt.056 FI to FI Payment Cancellation Request

When camt.056 is used

Banks send a camt.056 when a payment went out by mistake: a duplicate, a wrong amount or currency, the wrong beneficiary bank, a technical problem, a customer request, or fraud. The same message covers two situations: a cancellation request, when the instructed bank has not yet processed the payment, and a request for refund, when it has.

The request is part of the exceptions and investigations set and works as a case. The case has an ID and a creator, both carried unchanged to the end. At each hop the sender is the assigner and the receiver is the assignee, in the same way that a payment has an instructing and an instructed agent.

No bypass: the camt.056 must travel through the same banks as the original payment, in the same order. Each bank either stops the payment itself or passes the request on, and answers its own sender with a camt.029 (for example pending, passed to the next agent).

A corporate customer that wants to cancel its own instruction sends its bank a camt.055 (the customer-to-bank form); the bank then sends the camt.056 into the interbank chain.

If the creditor’s bank has already credited the creditor, it usually needs the creditor’s consent before it can give the money back. If consent is given, the funds come back in a pacs.004 with reason FOCR; if not, a camt.029 rejects the request.

Versions in common use

camt.056 key elements

Paths are relative to Document/FIToFIPmtCxlReq. Occurrence is from the base message (camt.056.001.08); market practice such as CBPR+ or a CSD’s rules can make an optional element mandatory or forbid it.

Rules worth knowing

• Cancellation reason codes (ISO names): AGNT Incorrect Agent, AM09 Wrong Amount, COVR Cover Cancelled Or Returned, CURR Incorrect Currency, CUST Requested By Customer, CUTA Cancel Upon Unable To Apply, DUPL Duplicate Payment, FRAD Fraudulent Origin, NARR Narrative, TECH Technical Problem, UPAY Undue Payment.
• The request must follow exactly the route of the original payment. A bank that cannot resolve it itself forwards it and answers its sender that the case was passed on.
• The original references must match the payment exactly; the receiving bank finds the payment by UETR and checks amount and date.
• One camt.056 can cover a pacs.008, a pacs.009 or a pacs.010 (financial institution direct debit).
• A camt.056 is a request, not an instruction: the money comes back only if the receiving bank (and, after crediting, its customer) agrees.

camt.056 XML example

ZagTrader Test Bank (ZAGTAEADXXX) notices that a payment of GBP 25,000.00 to Acme Components Ltd was released twice: the second one, UETR ac618c39-fc23-4c68-8900-7e656666f6b0, duplicates the pacs.008 example (UETR ed154219-a6d0-477d-a698-b8f543d107bb). It asks BANKGB2LXXX to cancel the duplicate with reason DUPL.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.056.001.08">
  <FIToFIPmtCxlReq>
    <Assgnmt>
      <Id>ZTCXL2610200001</Id>
      <Assgnr>
        <Agt>
          <FinInstnId>
            <BICFI>ZAGTAEADXXX</BICFI>
          </FinInstnId>
        </Agt>
      </Assgnr>
      <Assgne>
        <Agt>
          <FinInstnId>
            <BICFI>BANKGB2LXXX</BICFI>
          </FinInstnId>
        </Agt>
      </Assgne>
      <CreDtTm>2026-10-20T14:05:00+04:00</CreDtTm>
    </Assgnmt>
    <Undrlyg>
      <TxInf>
        <CxlId>ZTCXL2610200001</CxlId>
        <Case>
          <Id>ZTCASE2610200001</Id>
          <Cretr>
            <Agt>
              <FinInstnId>
                <BICFI>ZAGTAEADXXX</BICFI>
              </FinInstnId>
            </Agt>
          </Cretr>
        </Case>
        <OrgnlGrpInf>
          <OrgnlMsgId>ZT26102000005</OrgnlMsgId>
          <OrgnlMsgNmId>pacs.008.001.08</OrgnlMsgNmId>
          <OrgnlCreDtTm>2026-10-20T12:40:00+04:00</OrgnlCreDtTm>
        </OrgnlGrpInf>
        <OrgnlInstrId>ZT2610200005</OrgnlInstrId>
        <OrgnlEndToEndId>GT-PO-2026-0457</OrgnlEndToEndId>
        <OrgnlUETR>ac618c39-fc23-4c68-8900-7e656666f6b0</OrgnlUETR>
        <OrgnlIntrBkSttlmAmt Ccy="GBP">25000.00</OrgnlIntrBkSttlmAmt>
        <OrgnlIntrBkSttlmDt>2026-10-22</OrgnlIntrBkSttlmDt>
        <CxlRsnInf>
          <Orgtr>
            <Nm>ZAGTRADER TEST BANK</Nm>
          </Orgtr>
          <Rsn>
            <Cd>DUPL</Cd>
          </Rsn>
          <AddtlInf>DUPLICATE OF UETR ED154219-A6D0-477D-A698-B8F543D107BB</AddtlInf>
        </CxlRsnInf>
      </TxInf>
    </Undrlyg>
  </FIToFIPmtCxlReq>
</Document>

The case ID ZTCASE2610200001 and the case creator stay the same if BANKGB2LXXX has to pass the request further down a chain.

The settlement date is two days ahead, so BANKGB2LXXX may still be able to stop the payment; see the camt.029 example for its answer.

All identifiers are made up.

camt.056 and its MT equivalent

The camt.056 is the ISO 20022 counterpart of the MT192 (request for cancellation of a customer payment) and the MT292 (of a bank transfer). The MT version had a reference, the related reference of the original, field 11S with the MT type and date of the original, a narrative in field 79 and a copy of the original fields. The ISO message has dedicated elements for every original reference, including the UETR, and a mandatory coded reason.

Swift’s 22 November 2025 deadline covered payment instructions. Exceptions and investigations messages were not part of it, so MT n92 messages can still be exchanged where both sides support them, but a camt.056 is the natural answer to a payment that arrived as a pacs.008 or pacs.009.

Common errors and rejects

1. Request sent around the chain

   Sending the camt.056 straight to the creditor’s bank, skipping the banks in between, breaks the no-bypass rule. Banks that did not see the request cannot stop the funds they hold. Send it to the bank you sent the payment to.

2. Original payment cannot be found

   Wrong OrgnlUETR, an instruction ID retyped with a typo, or the wrong original message name stop the receiver from matching. Copy the references from your sent pacs.008 or pacs.009.

   How to fix it

3. Reason code missing or not allowed

   CBPR+ requires a coded reason. Use NARR with additional information only when no other code fits.

4. No answer for days

   A camt.056 does not stop anything by itself. If no camt.029 comes back, chase the assignee and check the payment status in the tracker by UETR. If the funds have been credited, the creditor’s bank needs its customer’s consent.

5. Funds returned but not matched

   A positive outcome after settlement comes back as a pacs.004 with reason FOCR, quoting the original payment, not the camt.056. Match it by the original UETR and close the case.

Related messages

• camt.029Resolution of Investigation
• pacs.004Payment Return
• pacs.008FI to FI Customer Credit Transfer
• pacs.009Financial Institution Credit Transfer
• pacs.002FI to FI Payment Status Report
• MT192Request for Cancellation
• MT196Answers
• MT199Free Format Message

• Serial MT103 chains vs MT103 plus MT202COV cover, and the same flows in pacs.008 and pacs.009 COV.

camt.056 questions

What is a camt.056 message?

The ISO 20022 FI to FI Payment Cancellation Request: a bank asks the next bank to cancel a payment it sent, or to return the funds if the payment was already processed.

What is the difference between camt.056 and camt.029?

The camt.056 is the request. The camt.029 Resolution of Investigation is the answer: cancelled, pending or rejected.

What is the ISO 20022 equivalent of MT192?

The camt.056. MT192 (customer payments) and MT292 (bank transfers) both map to it.

What does DUPL mean in camt.056?

Duplicate Payment: the payment was sent more than once and the extra one should be cancelled.

Can a camt.056 recall money that was already credited?

It can ask. The creditor’s bank normally needs the creditor’s agreement; if given, the money comes back in a pacs.004 with reason FOCR, otherwise the request is rejected in a camt.029.

Which camt.056 version does CBPR+ use?

camt.056.001.08, also used by the SEPA Credit Transfer inter-PSP guidelines for recalls.