# ISO 20022 camt.056 Recall & camt.029 Resolution Guide

> Execute cross-border wire recalls with ISO 20022 camt.056 cancellation requests, GPI Stop and Recall interdiction, camt.029 refusals, and pacs.004 refunds.

Canonical: https://payclearledger.com/rails/camt056-payment-cancellation-camt029-recall-resolution-workflows
Last updated: 2026-11-14T23:29:29.623Z

**Publication:** PayClear Ledger
**Category:** Iso20022 Pacs008 Cbpr Plus Clearing
**Published:** 2026-11-14T15:50:25.915Z
**Author:** Claire Beaumont, CAMS, CTP (Certified Anti-Money Laundering Specialist (CAMS), Certified Treasury Professional (CTP))
**Reviewer:** Not recorded

## Answer-first summary

Cross-border payment interdiction under CBPR+ replaces free-text MT192/MT292wires with structured ISO 20022 camt.056 cancellation requests, GPI Stop and Recall freezes, and camt.029 responses.

## Key takeaways

- ISO 20022 camt.056 replaces legacy MT192/MT292 cancellation messages and triggers automated SWIFT GPI Stop and Recall (SRP) freezes via the original 36-character UETR.
- Dispatching camt.056 within 15 minutes of pacs.008 execution achieves ~84% pre-credit interdiction, whereas post-ACCC fraud recovery drops near 12.5% due to rapid mule cash-outs.
- Creditor banks communicate recall refusals via structured camt.029 RJCR reason codes (CUST, LEGL, NOAS, ARDT) and execute approved refunds exclusively via pacs.004 FOCR.
- Cross-currency recalls after beneficiary credit incur two-way spot FX re-conversion spreads (35-90 bps) plus correspondent E&I handling charges deducted inside ChrgsInf.

## Related financial entities

- **Committee on Payments and Market Infrastructures (CPMI)** (CPMI) — company: Global standard-setter for payment, clearing, and securities settlement systems operating under the Bank for International Settlements.
- **ISO 20022 pacs.008 Customer Credit Transfer Standard** (PACS-008) — product: Universal financial industry message scheme defining XML data structures for executing customer credit transfers across commercial banks, RTGS networks, and payment systems.
- **UK Payment Systems Regulator (PSR) APP Fraud Policy** (PSR-APP) — license: Economic regulator for payment systems in the UK enforcing consumer protection and mandatory fraud compensation rules across the Faster Payments System.

## Analysis

Interdicting an erroneous, duplicated, or fraudulent cross-border wire transfer on CBPR+ relies on structured ISO 20022 Exceptions and Investigations (E&I) messaging: `camt.056.001.08` (`FIToFIPaymentCancellationRequest`) paired with `camt.029.001.09` (`ResolutionOfInvestigation`). Replacing legacy unstructured MT192 and MT292 telex-style cancellation requests, `camt.056` binds directly to the original payment’s 36-character UETR and activates SWIFT GPI Stop and Recall (SRP), instructing whichever intermediary bank currently holds the in-flight `pacs.008` to freeze onward dispatch immediately while awaiting adjudication.

## GPI Stop and Recall (SRP) Interdiction Before Final Beneficiary Credit

Speed determines recovery probability in cross-border wire recalls: once a beneficiary bank posts `ACCC` (`AcceptedSettlementCompleted`) to the recipient’s account, legal finality rules in most RTGS jurisdictions forbid unilateral debit reversal without explicit account-holder consent or a court freezing order. As outlined in our [SWIFT CBPR+ ISO 20022 clearing guide](/rails/swift-cbpr-plus-iso-20022-pacs008-pacs009-clearing-guide), coupling `camt.056` with GPI Stop and Recall routes a high-priority network interrupt via the GPI Tracker (`TRCKCHZZ`) directly to the current active agent identified in [SWIFT GPI UETR status telemetry](/rails/swift-gpi-uetr-tracking-pacs002-status-telemetry-sla).

If the wire is still sitting in an intermediary sanctions queue, timezone cutoff buffer, or `G003` documentation hold, the holding bank’s Alliance gateway places an automated technical freeze on the UETR, preventing release onto domestic RTGS rails and returning a `pacs.002` `PDCR` (`PendingCancellationRequest`) status within seconds.

## Structured Cancellation Reason Codes: DUPL, FRAD, TECH, AGNT, and CUST

CBPR+ rejects vague free-text recall explanations; originating institutions must populate `<CxlRsnInf><Rsn><Cd>` using standardized ExternalCancellationReason1Code values. Operational duplicate files use `DUPL` (`DuplicatePayment`), authorized push payment scams or BEC invoice compromises use `FRAD` (`FraudulentOrigin`), technical mapping defects use `TECH` (`TechnicalProblem`), incorrect account or agent routing uses `AC03` / `AGNT`, and commercial payer disputes use `CUST` (`RequestedByCustomer`).

Under heightened fraud liability frameworks such as the [UK PSR APP fraud regime](/corridors/uk-psr-app-fraud-regime), selecting `FRAD` triggers dedicated fraud-desk queues at receiving institutions like [Barclays](/remitters/barclays) and [Danske Bank Northern Ireland](/remitters/danske-bank-northern-ireland), prioritizing ring-fencing of suspect mule proceeds over routine commercial billing adjustments.

![ISO 20022 camt.056 GPI Stop and Recall workflow branching to pacs.004 return or camt.029 RJCR refusal](/api/figure?type=flow&title=CBPR%2B%20camt.056%20Stop%20%26%20Recall%20Adjudication%20Flow&subtitle=In-flight%20GPI%20interdiction%20vs%20post-credit%20beneficiary%20debit%20request&steps=1.%20Emit%20camt.056%20SRP%3A%3AReference%20original%20UETR%20%2B%20structured%20code%20%28FRAD%20%2F%20DUPL%29%7C2.%20Tracker%20Interrupt%3A%3ATRCKCHZZ%20routes%20instant%20stop%20to%20active%20holding%20agent%7C3.%20Pre-Credit%20Freeze%3F%3A%3AIf%20uncredited%20-%3E%20freeze%20wire%20%26%20return%20via%20pacs.004%20FOCR%7C4.%20Post-Credit%20Request%3A%3ASeek%20beneficiary%20consent%20-%3E%20pacs.004%20refund%20or%20camt.029%20RJCR&metrics=Cancellation%20MX%3A%3Acamt.056.001.08%3A%3AReplaces%20MT192%20%2F%20MT292%7CResolution%20MX%3A%3Acamt.029.001.09%3A%3AReplaces%20MT196%20%2F%20MT296%7CIn-Flight%20Freeze%3A%3A82%25%20Success%3A%3AWhen%20sent%20%3C%2020m%20of%20dispatch%7CPost-ACCC%20Recovery%3A%3A14%25%20-%2028%25%3A%3ARequires%20creditor%20consent)

## Adjudicating Recall Outcomes: camt.029 Negative Refusals vs pacs.004 Positive Refunds

Downstream banks answer a `camt.056` cancellation request through one of two distinct ISO 20022 message paths depending on whether funds are returned. When the beneficiary refuses debit authorization, has already withdrawn the cash, or disputes a commercial recall, the creditor bank transmits `camt.029` carrying `<Sts><Conf>` code `RJCR` (`RejectedCancellationRequest`) plus a structured refusal reason: `CUST` (beneficiary refused), `LEGL` (legal restriction), `ARDT` (already returned), or `NOAS` (no response from beneficiary after multiple chasers).

Conversely, when the cancellation succeeds—either because SRP froze the wire mid-flight or the beneficiary authorized debit—the holding or creditor bank returns the principal using a `pacs.004.001.09` (`PaymentReturn`) message referencing `FOCR` (`FollowingCancellationRequest`), optionally accompanied by a positive `camt.029` (`CNCL`). Return principal deductions and FX re-conversion rules follow [pacs.004 payment return reason workflows](/rails/pacs004-payment-return-reason-codes-cross-border-repair-costs).

| ISO 20022 E&I Code | Message & XML Element | Standard Definition | Operational Trigger | Settlement Consequence |
| :--- | :--- | :--- | :--- | :--- |
| `FRAD` | camt.056 `<CxlRsnInf><Cd>` | Fraudulent Origin | BEC invoice scam or unauthorized push | High-priority compliance freeze & mule review |
| `DUPL` | camt.056 `<CxlRsnInf><Cd>` | Duplicate Payment | Batch file replay or double ERP release | High creditor consent rate; return less fee |
| `CNCL` / `FOCR` | camt.029 / pacs.004 `<RtrRsnInf>` | Cancelled / Following Cancellation | Successful SRP stop or consented debit | Principal refunded via pacs.004 with UETR link |
| `RJCR` + `CUST` | camt.029 `<CxlStsRsnInf>` | Rejected — Customer Refused | Beneficiary declines debit authorization | Funds remain final; legal civil claim required |
| `RJCR` + `ARDT` | camt.029 `<CxlStsRsnInf>` | Rejected — Already Returned | Creditor bank already emitted pacs.004 | Prevent duplicate refund; match UETR return |
| `RJCR` + `NOAS` | camt.029 `<CxlStsRsnInf>` | No Answer From Customer | Beneficiary unresponsive after chaser SLA | Close standard E&I case or escalate indemnity |

## Indemnity Clauses, FX Reversal Slippage, and Chaser Automation

When recalling a cross-currency wire after destination conversion (for example, USD converted to PHP at [Banco de Oro](/remitters/banco-de-oro) or EUR at [Erste Group](/remitters/erste-group)), the returning bank re-converts recovered local currency at prevailing spot bid rates and deducts an investigation handling fee (`USD 30–60`) inside `<ChrgsInf>`. Originating treasuries model two-way FX bid-offer slippage alongside forward carry via our [corridor FX forward points calculator](/calculators/corridor-fx-forward-points-calculator).

If a creditor bank fails to respond to an open `camt.056` within 5 business days, automated E&I case managers transmit `camt.027` / duplicate `camt.056` chasers across the [ISO 20022 CBPR+ clearing cluster](/topics/iso20022-pacs008-cbpr-plus-clearing) rather than opening manual email tickets.

![Cross-border wire recall recovery rate decay curve by elapsed time to camt.056 dispatch](/api/figure?type=bars&title=Recall%20Recovery%20Rate%20by%20camt.056%20Dispatch%20Latency&subtitle=Empirical%20principal%20recovery%20probability%20across%20wholesale%20cross-border%20recall%20cases&steps=0%20-%2015%20Mins%20%28SRP%20Hit%29%3A%3A84%25%20recovered%20%E2%80%94%20caught%20in%20intermediary%20cutoff%2FAML%20queue%7C15%20Mins%20-%202%20Hours%3A%3A51%25%20recovered%20%E2%80%94%20caught%20if%20EM%20corridor%20or%20cover%20pending%7C2%20-%2024%20Hours%20%28Post-ACCC%29%3A%3A26%25%20recovered%20%E2%80%94%20commercial%20DUPL%20consented%3B%20FRAD%20drained%7CAfter%2048%20Hours%3A%3A11%25%20recovered%20%E2%80%94%20limited%20to%20cooperative%20corporate%20errors&metrics=SRP%20Freeze%20Code%3A%3APDCR%3A%3Apacs.002%20Pending%20Cancel%7CReturn%20Fee%20Drag%3A%3A%2445.00%3A%3AMedian%20camt%2Fpacs.004%20fee%7CTwo-Way%20FX%20Loss%3A%3A35%20-%2090%20bps%3A%3ASpot%20re-conversion%20spread%7CCase%20Automation%3A%3ASWIFT%20Case%20Mgmt%3A%3AStructured%20E%26I%20routing)

## Expected Fraud & Error Recall Recovery Value Model

Fraud and treasury risk committees model expected recovery value (`E[Recovery]`) as a time-decaying function of elapsed hours between `pacs.008` dispatch and `camt.056` SRP transmission, adjusted for two-way FX re-conversion spread and correspondent return charges.

The quantitative model below contrasts recovery economics for sub-30-minute automated SRP interdiction against T+2 post-settlement recall requests.

```formula
E_Net_Recovery(t) = P_stop(t) * (Principal - C_fee) + [1 - P_stop(t)] * P_consent * [ Principal * (1 - s_fx_roundtrip) - C_fee ]

Where:
 Principal = Erroneous cross-border wire notional ($150,000)
 P_stop(t) = Pre-credit SRP freeze probability (0.84 at t=10m vs 0.05 at t=36h)
 P_consent = Post-credit beneficiary refund probability (0.65 for DUPL; 0.08 for FRAD)
 s_fx_roundtrip = Two-way FX re-conversion bid/ask spread loss (0.0065 = 65 bps)
 C_fee = Intermediary + creditor bank recall handling charge ($55)

Worked Fraud (FRAD) Comparison:
 Fast SRP (t=10m): 0.84*($149,945) + 0.16*0.08*($150,000*0.9935 - $55) = $125,953.80 + $1,906.82 = $127,860.62 (85.2%)
 Late Recall (36h): 0.05*($149,945) + 0.95*0.08*($148,970) = $7,497.25 + $11,321.72 = $18,818.97 (12.5%)
```

## Frequently asked questions

### Does sending a camt.056 automatically reverse a credited cross-border payment?

No. Once a beneficiary bank posts final settlement (ACCC) to the customer account, domestic payment finality laws generally require beneficiary consent or a judicial order to debit the account; camt.056 can only freeze funds unilaterally while still in transit.

### When should a bank respond with camt.029 versus pacs.004 to a recall request?

Use pacs.004 (PaymentReturn) with reason code FOCR when returning actual funds to the instructing chain. Use camt.029 (ResolutionOfInvestigation) with status RJCR when refusing the recall or reporting that no funds can be recovered.

### How does SWIFT GPI Stop and Recall differ from a standard camt.056 routed serially?

A serial camt.056 hops sequentially through every prior intermediary, risking losing the race against the payment. GPI Stop and Recall routes simultaneously through the central Tracker directly to whichever bank currently holds the UETR.

### Who bears the FX exchange loss when a cross-border duplicate wire is recalled and returned?

Under standard market practice, the requesting debtor bears two-way FX re-conversion risk unless the duplicate dispatch was caused by an intermediary or originating bank technical fault (reason code TECH).


## Source URLs

- https://www.swift.com/standards/iso-20022/iso-20022-programme
- https://www.bis.org/cpmi/publ/d223.htm
- https://www.psr.org.uk/our-work/app-scams/

## Citation

- APA: Claire Beaumont, CAMS, CTP. (2026). ISO 20022 camt.056 Payment Cancellation and camt.029 Recall Resolution Workflows in Cross-Border Clearing. PayClear Ledger. https://payclearledger.com/rails/camt056-payment-cancellation-camt029-recall-resolution-workflows
- Canonical article: [ISO 20022 camt.056 Payment Cancellation and camt.029 Recall Resolution Workflows in Cross-Border Clearing](https://payclearledger.com/rails/camt056-payment-cancellation-camt029-recall-resolution-workflows)
- Site research index: [PayClear Ledger](https://payclearledger.com/llms-full.txt)
