pub struct MT192 {
pub field_20: GenericReferenceField,
pub field_21: GenericReferenceField,
pub field_11s: Field11S,
pub field_79: Option<GenericMultiLine6x35>,
pub field_23b: Option<GenericTextField>,
pub field_32a: Option<Field32A>,
pub field_50: Option<Field50>,
pub field_59: Option<Field59>,
pub field_71a: Option<GenericTextField>,
}
Expand description
§MT192: Request for Cancellation
This message is sent by a financial institution to request the cancellation of a previously sent message. MT192 is used for cancellation requests related to customer credit transfers and other payment instructions.
§Key Features
- Cancellation request: Official request to cancel a previously sent message
- Reference tracking: Links to the original message through multiple reference fields
- Conditional structure: Either narrative (field 79) or copy of original message fields
- Audit trail: Maintains complete cancellation audit records
- Reason codes: Standardized cancellation reason codes for processing
§Field Structure
The message follows a conditional structure where either field 79 (narrative description) or a copy of the mandatory fields from the original message must be present, or both.
§Cancellation Process
Used when a sender needs to request cancellation of a previously sent message, typically due to errors, fraud, customer request, or technical problems. The receiver processes the request and may accept or reject the cancellation.
Fields§
§field_20: GenericReferenceField
Transaction Reference Number - Field 20
Unique reference assigned by the sender for this cancellation request. This reference is used throughout the cancellation lifecycle for tracking, acknowledgment, and audit purposes. Must be unique within sender’s system per business day.
field_21: GenericReferenceField
Related Reference - Field 21
Contains the reference from field 20 of the message to be cancelled. This creates a direct link between the cancellation request and the original message, enabling the receiver to identify exactly which message to cancel.
field_11s: Field11S
MT and Date of the Original Message - Field 11S
Specifies the message type, date, session number, and Input Sequence Number (ISN) of the original message to be cancelled. Format: 3!n6!n4!n/4!n Example: 103231215001/0123 (MT103 dated 2023-12-15, session 0001, ISN 0123)
field_79: Option<GenericMultiLine6x35>
Narrative Description of the Original Message - Field 79 (Conditional)
Contains cancellation reason codes and free-form text explaining the cancellation. Must be present if copy of original message fields is not included, or both may be present. Common reason codes: AGNT, AM09, COVR, CURR, CUST, CUTA, DUPL, FRAD, TECH, UPAY
field_23b: Option<GenericTextField>
Copy of Mandatory Fields from Original Message - Multiple Fields (Conditional)
When present, contains a copy of at least the mandatory fields from the original message. This helps the receiver identify the exact transaction to be cancelled. The specific fields depend on the original message type referenced in field 11S.
For MT103: Would include fields 23B, 32A, 50, 59, 71A
Note: This is represented as optional structured content that can contain various field combinations depending on the original message type.
field_32a: Option<Field32A>
§field_50: Option<Field50>
§field_59: Option<Field59>
§field_71a: Option<GenericTextField>