Provides a substantive answer to a Category 2 cancellation request or query. The answer reports a case outcome; it does not itself prove that reverse value settled.
DIRECTION: Sent by the institution answering the earlier MT292 or MT295.
Version + profile: MT296 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.
Field correspondence, transformation treatment, and data-loss notes for Category 2 cancellation answer compared with a structured resolution of the associated cancellation investigation.
crc32:ff6e8921Field correspondence, transformation treatment, and data-loss notes for Category 2 query answer compared with a structured Case Management investigation response.
crc32:8d3c9dc6Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:776bc9adCurated teaching subset. The full answer structure depends on the MT292 or MT295 being answered and the current service rules.
| FIELD | NAME | PRESENCE | WHAT IT MEANS |
|---|---|---|---|
:20: | Answer reference | MANDATORY | Unique reference for the answer. |
:21: | Related reference | MANDATORY | Reference of the request being answered. |
:76: | Answer | MANDATORY | Substantive outcome, reason and supporting detail. |
:76:/CNCL/ | Positive cancellation outcome | OPTIONAL | Indicates the cancellation request was accepted under the applicable convention. |
:76:/RJCR/ | Refused cancellation outcome | OPTIONAL | Indicates the cancellation request was refused with a reason. |
Block 3 / field 121 | UETR | CONDITIONAL | Reference of the underlying transfer or case. |
Swift Standards MT (annual standards releases) ↗ — Swift · Category 2 — MT296 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.
Payments Signal editorial teaching models — Payments Signal
What this simplifies: Shows cancellation and query outcomes at concept level.
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…