Answers an MT195 query, MT192 cancellation request, or another Category 1 case without its own response type. The same message shell can therefore carry a cancellation outcome or an investigation answer, distinguished by structured content.
DIRECTION: Sent by the institution answering the earlier Category 1 request to the institution that opened the case.
Version + profile: MT196 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.
EVIDENCE AT ARM'S REACH
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.
The annual MT standard and release information. Full field specifications may require an authenticated Swift account.
A fictional answer to an MT192 or MT195; the response is not proof that return value settled. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:ee0ddb7fInitiation, serial and cover context, cancellation and correspondence, advices, and statements.
crc32:8b3a20e4Field correspondence, transformation treatment, and data-loss notes for Legacy answer to a cancellation/query compared with a structured resolution of investigation.
crc32:6cd3cfd2Field correspondence, transformation treatment, and data-loss notes for Legacy answer compared with a structured investigation response.
crc32:efa3234eCurated field requirements, contexts, operational meaning, and implementation cautions.
crc32:04c55911Curated teaching subset. MT196 answer codes and narrative structure depend on the request being answered; consult the current Standards MT handbook and market-practice guidance.
| FIELD | NAME | PRESENCE | WHAT IT MEANS |
|---|---|---|---|
:20: | Answer reference | MANDATORY | Unique reference for this answer. |
:21: | Related reference | MANDATORY | Reference of the MT192 or MT195 being answered. |
:76: | Answers | MANDATORY | Structured outcome, reason, and evidence for the request. |
:76:/CNCL/ | Cancelled status | OPTIONAL | States that the cancellation was completed as requested. |
:76:/RJCR/ | Rejected-cancellation status | OPTIONAL | States that the cancellation request was refused, with a reason. |
Block 3 / field 121 | UETR | CONDITIONAL | Reference of the underlying payment or investigation case. |
Swift Standards MT (annual standards releases) ↗ — Swift · Category 1 — MT196 Answers
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.
ISO 20022 Standards (Swift ISO 20022 adoption programme) ↗ — Swift · Payment cancellation and E&I MT/MX equivalents
Do not generalise the payment-instruction deadline to every FIN message. Swift publishes differentiated NAK, contingency-conversion, reporting, initiation and exceptions-and-investigations treatment.
Payments Signal editorial teaching models — Payments Signal
What this simplifies: The sample focuses on a cancellation response; query-answer usages share the same message type.
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.
Share an operational observation or ask a concrete payments question. Your name and message are public; your email remains private.
Loading the discussion…