MT292 — Request for Cancellation
Cancellation request for a previously sent interbank transfer (MT200, MT202). Typical cases: duplicate instruction, wrong beneficiary, detected fraud.
Purpose
MT292 requests cancellation of a previous FI transfer. If the receiver has not yet executed the payment, cancellation may be accepted. If already executed, the receiver may propose a return MT202 or refuse.
Block 4 structure
| Tag | Name | Status |
|---|---|---|
:20: | Transaction Reference Number | Mandatory |
:21: | Related Reference (reference of MT202 to cancel) | Mandatory |
:11S: | MT and Date of Original Message | Mandatory |
:79: | Narrative (reason + details) | Mandatory |
Real-world example
BNP Paribas asks HSBC to cancel a duplicate MT202:
{1:F01BNPAFRPPAXXX0000000000}{2:I292HSBCGB2LXXXXN}{4:
:20:CXL260518001
:21:FIN20260518002
:11S:202
260518
:79:WE HEREBY REQUEST CANCELLATION OF OUR MT202 REF FIN20260518002
DATED 18 MAY 2026 FOR GBP 5000000,00 IN FAVOUR OF HSBC LONDON
REASON: DUPLICATE INSTRUCTION SENT IN ERROR.
PLEASE CONFIRM CANCELLATION OR INDICATE IF PAYMENT ALREADY EXECUTED.
REGARDS.
-}{5:{CHK:VWX678901234}}Common pitfalls
- Missing :11S: — without MT type + date, ambiguous if several messages share the same :20:.
- Unclear reason — the spec expects an explicit reason in :79: (DUPL, FRAUD, INCV, ...).
- Late cancellation — if MT900 / MT910 have been issued, simple cancellation is no longer possible.
MX equivalent
Replaced by camt.056 (FI to FI Payment Cancellation Request) in ISO 20022. More structured with standard reason codes.