GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX
PAYMENTSSIGNAL

The interactive academy for the standards, messages, and rails that move money.

PROGRESS
MT292SWIFT MT

MT292 — Request for Cancellation

Requests cancellation of a previously sent Category 2 financial-institution transfer, including the cover leg of a customer cover payment. It is a request, not returned value.

DIRECTION: Sent to the institution that received or forwarded the original Category 2 transfer.

Version + profile: MT292 follows the applicable Standards MT release and service rules. This page is a curated field subset; bilateral practice and annual standards changes can alter permitted content and handling.

Contributor Shubham Mathure

DOMAIN + EDITORIAL AUDITAudited 2026-07-18 for payment logic, source scope, technical writing, and Payments Signal voice — see the method.

EVIDENCE AT ARM'S REACH

IMPLEMENTATION RESOURCES

Start with the exact message version, then apply the scheme or network profile that governs your implementation.

An XSD checks XML structure. A usage guideline adds profile rules, conditional fields, code restrictions, and business controls. XSD-valid does not mean scheme-compliant.

MappingCBPR+current

MT292 → camt.056 implementation mapping

Field correspondence, transformation treatment, and data-loss notes for Category 2 cancellation request compared with the structured FI-to-FI cancellation request used for an institutional or cover-payment leg.

Owner
Payments Signal
Checked
2026-07-19
Integrity
crc32:32b2519f
Access
Payments Signal download · Original, source-backed teaching asset; no login required.
DOWNLOAD
Field matrixBase ISO 20022current

MT292 field matrix

Curated field requirements, contexts, operational meaning, and implementation cautions.

Owner
Payments Signal
Checked
2026-07-19
Integrity
crc32:08d17bc3
Access
Payments Signal download · Original, source-backed teaching asset; no login required.
DOWNLOAD

WHO IS INVOLVED

  • Category 2 cancellation requesterIdentifies the original transfer, UETR and reason, and coordinates the request with any linked customer-payment leg.
  • Cancellation receiverLocates the transfer, determines whether it can be stopped or recovered, and sends a substantive answer.

KEY FIELDS

Curated teaching subset. Use the current Standards MT handbook and service rules for complete format, codes and cover-leg cancellation choreography.

Key fields of MT292
FIELDNAMEPRESENCEWHAT IT MEANS
:20:Request referenceMANDATORYUnique reference for the cancellation request.
:21:Related referenceMANDATORYReference of the original Category 2 transfer.
:11S:Original message detailsMANDATORYOriginal message type and transmission date.
:79:Cancellation detailsMANDATORYReason and supporting information for the request.
Block 3 / field 121UETRCONDITIONALNetwork reference used to correlate the original transfer and linked cover payment.
:79:/CUST/Customer-requested markerOPTIONALIndicates a customer-originated cancellation reason where the market practice permits it.

COMMON ERRORS

  • Cancelling only the MT103 leg of a cover payment.Consequence: Cover value can continue and arrive without a usable customer instruction.Avoid it: Coordinate MT192 and MT292 requests with the same underlying payment references.
  • Closing the case on message acceptance.Consequence: Operations assumes value returned although only a request was delivered.Avoid it: Reconcile the substantive answer, reverse value movement and account entries separately.

USAGE CONTEXTS

  • Cover-payment cancellationA cover flow may require coordinated cancellation of the MT103 announcement and MT202 COV value leg; cancelling only one creates an unmatched state.
  • Category 2 transferUsed for an eligible financial-institution transfer rather than a Category 1 customer-payment message.
MT292 → CAMT.056

SEE IT IN A PLAYABLE FLOW

LEARN THE CONTEXT

Sources for this reference2
  1. Official requirement

    Swift Standards MT (annual standards releases) ↗ — Swift · Category 2 — MT292 Request for Cancellation

    Defines the MT message standards (including MT101, MT103, MT202/202 COV, and the MT9xx statement messages) exchanged over the Swift FIN network, maintained through annual standards releases. · Checked 2026-07-18

    Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login. Coexistence for in-scope FI-to-FI payment instructions ended on 22 November 2025, but treatment differs by MT: some instructions are NAKed and selected messages can enter temporary, chargeable contingency conversion. Reporting, initiation, investigations and correspondence follow separate roadmaps.

  2. Simplified educational illustration

    Payments Signal editorial teaching models — Payments Signal

    This site's own simplified teaching models. · Checked 2026-07-12

    What this simplifies: Focuses on one cover-payment cancellation and omits multi-correspondent variations.

    Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.

COMMUNITY SIGNAL

Discuss this learning page

Share an operational observation or ask a concrete payments question. Your name and message are public; your email remains private.

NEXT QUESTION REVIEWMonday, 27 Jul, 8:00 amMonday answer runs use source-supported educational material. Some questions may need owner review.
WHAT ARE YOU SHARING?

Publish only lawful, relevant content. Never include confidential payment or personal data.

Public discussion

LOADING

Loading the discussion…