ZagTrader

Common group, all categories

MT n92 Request for Cancellation (MT292 to MT992)

Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked

MT n92 is the common group message a bank, or a corporate customer, sends to ask the Receiver of an earlier Swift message to consider cancelling it. The first digit is the category of the message to be cancelled: MT292 for an interbank transfer, MT392 for a treasury message, MT592 for a securities message, and so on. The layout is the same in every category, and the Receiver always answers with the matching MT n96.

Message type
MTn92
Category
All (n = category digit)
Structure
5 fields listed

When MTn92 is used

Swift reserves the last two digits 90 to 99 in every category for the common group messages, which share one layout whatever the category: n90 Advice of Charges, Interest and Other Adjustments, n91 Request for Payment of Charges, Interest and Other Expenses, n92 Request for Cancellation, MTn95 Queries, MTn96 Answers, n98 Proprietary Message and MTn99 Free Format Message. The "n" stands for the category digit.

The category digit says which business area the message belongs to, and therefore which team at the Receiver handles it: 1 Category 1 customer payments and cheques (MT192); 2 Category 2 financial institution transfers (MT292); 3 Category 3 treasury markets, that is FX, money markets and derivatives (MT392); 4 Category 4 collections and cash letters (MT492); 5 Category 5 securities markets (MT592); 6 Category 6 precious metals, commodities and syndications (MT692); 7 Category 7 documentary credits and guarantees (MT792); 8 Category 8 travellers cheques (MT892); 9 Category 9 cash management and customer status (MT992).

Use the category of the message you want cancelled: an MT292 to cancel an MT202 or MT210, an MT392 to cancel a treasury message, an MT992 for a category 9 message. The request goes to the Receiver of that original message and to no one else, and it only covers Swift messages.

Some categories have their own cancellation mechanism, and there the n92 must not be used. An MT292 may not cancel an MT200: the Sender asks the account with institution to transfer the funds back instead. An MT592 may not cancel an ISO 15022 securities message such as an MT540; those are cancelled with a new message whose field 23G carries CANC. An MT792 may not cancel a documentary credit, an authorisation to reimburse or a guarantee; those use the MT707, MT747 and MT767.

An n92 is a request, not an order. If the Receiver has already acted, the request becomes a request to reverse the transfer, which may need the beneficiary’s consent. The Receiver must always answer with an MT n96 in the same category, quoting the request’s field 20 in its field 21.

MTn92 format: sequences and fields

Message text (block 4)Mandatory

Same layout in every category. After field 11S there must be field 79, a copy of the original fields, or both.

TagNameStatusFormatMeaning
20Transaction Reference NumberM16xThe Sender’s reference for this request. The answering MT n96 quotes it in field 21. No leading or trailing slash and no double slash (T26).
21Related ReferenceM16xField 20 of the message to be cancelled. To cancel a whole multiple message, field 20 of its non-repetitive part (or, if it has none, the reference of its first transaction).
11SMT and Date of the Original MessageM3!n 6!n [4!n6!n]Three lines: the message type of the original (100 to 999, T18), the date it was sent as YYMMDD (T50) and, when available, the session number and input sequence number (ISN) of the original.
79Narrative Description of the Original MessageC35*50xA description that lets the Receiver identify the message or the single transaction to cancel. A structured form starts line 1 with a reason code between slashes, /4!c/ with optional text, and lines 2 to 35 with //. Reason codes: AGNT, AM09, COVR, CURR, CUST, CUTA, DUPL, FRAD, TECH, UPAY.
(no tag)Copy of at least the Mandatory Fields of the Original MessageCCopy of fieldsThe fields of the original message, in their original order. Swift checks their syntax but not whether they match the original; any valid field except 77F and 77T may be copied.

Format notation: n digits, a upper-case letters, c upper-case letters and digits, x any character of the Swift character set, d a decimal number with a comma, ! fixed length, [ ] optional, 4*35x up to 4 lines of 35 characters. M mandatory, O optional, C conditional (a rule decides).

Rules worth knowing

  • Field 79, a copy of at least the mandatory fields of the original message, or both must be present (network rule C1, error C25). A message that ends after field 11S is rejected.
  • In field 11S the message type must be from 100 to 999 (T18) and the date a valid YYMMDD date (T50). Give the session number and ISN of the original when you have them.
  • An MT n92 may be sent only to the Receiver of the original message, and only to cancel a Swift message.
  • An MT n92 always requires an answer, and the answer must be an MT n96 in the same category.
  • An MT292 may not cancel an MT200. An MT592 may not cancel an ISO 15022 message (use field 23G with CANC). An MT792 may not cancel a documentary credit, authorisation to reimburse or guarantee (use MT707, MT747 or MT767).
  • To cancel one transaction of a multiple message, follow 11S with field 79 describing that transaction, or a copy of the relevant fields of the common part and of that transaction. To cancel several but not all transactions, send one n92 per transaction.
  • If /FRAD/ is the only content of field 79, a copy of at least the mandatory fields of the original message must also be present. Copied fields may not include 77F or 77T (T13).

MTn92 example

ZagTrader Test Bank, Dubai (ZAGTAEADXXX), sent BANKUS33XXX the same MT210 notice to receive twice on 20 October 2026: once as ZTN2610200007 and again as ZTN2610200009. It asks BANKUS33 to cancel the second one with an MT292, because the original is a category 2 message.

{1:F01ZAGTAEADAXXX0000000000}{2:I292BANKUS33XXXXN}{4:
:20:ZTC2610200003
:21:ZTN2610200009
:11S:210
261020
:79:/DUPL/DUPLICATE OF OUR MT210 ZTN2610200007
//VALUE 261022 USD1200000,00 FROM BANKDEFFXXX
//PLEASE DISREGARD AND CONFIRM BY MT296
-}
Decode this example in the parser

Line by line

LineWhat it says
{1:F01ZAGTAEADAXXX0000000000}{2:I292BANKUS33XXXXN}{4:Sender ZAGTAEADXXX, input MT292 to BANKUS33XXX: the Receiver of the MT210 to be cancelled.
:20:ZTC2610200003Reference of this request. BANKUS33 will quote it in field 21 of its MT296.
:21:ZTN2610200009Field 20 of the MT210 to be cancelled.
:11S:210Line 1 of 11S: the original was an MT210.
261020Line 2: it was sent on 20 October 2026. The optional session number and ISN are left out.
:79:/DUPL/DUPLICATE OF OUR MT210 ZTN2610200007Structured line 1: reason code DUPL between slashes, then free text.
//VALUE 261022 USD1200000,00 FROM BANKDEFFXXXFollowing lines start with //. They identify the notice.
//PLEASE DISREGARD AND CONFIRM BY MT296The answer the Sender expects.
-}End of block 4.

An MT392, MT592 or MT992 has exactly the same fields; only the category digit, and so the message being cancelled, changes. For a customer payment, see the MT192.

BICs and references are made up.

Common errors and rejects

  1. Nothing after field 11S (C25)

    The network rejects an n92 that has neither field 79 nor copied fields. Add a description, a copy of the original, or both.

  2. Wrong category digit

    An MT192 sent about an MT202, or an MT292 about an MT103, reaches the wrong team and is often refused. Use the category of the message you want cancelled.

  3. n92 used where the category has its own cancellation

    Settlement instructions such as an MT540 are cancelled with a new message carrying CANC in field 23G, not an MT592; documentary credits and guarantees use MT707, MT747 or MT767, not an MT792; an MT200 cannot be cancelled with an MT292.

  4. Wrong date or type in 11S (T50, T18)

    The second line is the date the original was sent, not its value date, and the first line is a three-digit message type. A wrong date is not always rejected but often means the Receiver cannot find the original.

  5. Copied fields not accepted (T13)

    Fields 77F and 77T may not be copied, and generic ISO 15022 fields may not be mixed with other fields in the copy. Copy only what identifies the original, in its original order.

  6. No answer received

    The Receiver must answer with an MT n96. If none arrives, chase with an MT n95 query quoting your field 20 and, for a payment, its UETR.

    How to fix it

MTn92 in ISO 20022

For payments, the ISO 20022 equivalent of the MT n92 is camt.056 (FI to FI Payment Cancellation Request), answered by camt.029 (Resolution of Investigation), which replaces the MT n96. J.P. Morgan’s and Clearstream’s adoption schedules map camt.056 to MTx92 and camt.029 to MTx96.

Cancelling a notice to receive (MT210) is a separate message in ISO 20022: camt.058 Notification to Receive Cancellation Advice, which both schedules map to the MT292. camt.055 Customer Payment Cancellation Request, sent by the payer about its own payment initiation, is listed in both schedules as a new message with no MT equivalent.

Swift postponed its mandate to send all payment cancellations through the Stop and Recall process; according to J.P. Morgan, cancellation messages can continue in both MT and ISO 20022 until November 2027. The n92 in categories 3 to 9 was not part of the CBPR+ migration.

MTn92 questions

What does the n in MT n92 mean?
It stands for the category digit. The same request for cancellation exists as MT192, MT292, MT392 and so on up to MT992, one per category, all with the same fields.
Which category digit should I use?
The category of the message you want cancelled: MT292 for an MT202 or MT210, MT392 for a treasury confirmation, MT992 for a category 9 message. That routes the request to the team that handled the original.
What is the difference between MT192 and MT292?
Only the category. The MT192 cancels a customer payment such as an MT103; the MT292 cancels an interbank message such as an MT202, MT202COV or MT210.
Can an MT n92 cancel any message?
No. It cannot cancel an MT200 (MT292), ISO 15022 securities messages (MT592: use CANC in field 23G), or documentary credits, reimbursement authorisations and guarantees (MT792: use MT707, MT747 or MT767).
How is an MT n92 answered?
With an MT n96 in the same category, quoting the request’s field 20 in field 21. See MTn96.
What is the ISO 20022 equivalent of MT n92?
For payments, camt.056, answered by camt.029. The cancellation of a notice to receive is camt.058.

All MT messages · ISO 20022 messages · Codes · Troubleshooting