Struct MT111 

pub struct MT111 {
    pub field_20: Field20,
    pub field_21: Field21NoOption,
    pub field_30: Field30,
    pub field_32: Field32,
    pub field_52: Option<Field52DrawerBank>,
    pub field_59: Option<Field59NoOption>,
    pub field_75: Option<Field75>,
}

MT111: Stop Payment of a Cheque

Purpose

Used to request the stop payment of a previously issued cheque from the account holder to their bank. This message provides precise identification of the cheque to be stopped and includes supporting information for immediate processing to prevent unauthorized or problematic cheque payments.

Scope

This message is:

• Used for stop payment requests from account holders to their financial institutions
• Applicable for preventing payment of specific cheques before clearing
• Designed for urgent processing to halt cheque payment authorization
• Compatible with both domestic and international cheque clearing systems
• Subject to validation rules for proper cheque identification
• Integrated with fraud prevention and account security systems

Key Features

• Precise Cheque Identification: Complete cheque details for accurate identification
• Immediate Stop Payment Control: Urgent processing to prevent cheque payment
• Reference Tracking System: Links to original cheque issue and account references
• Reason Code Support: Optional information about why stop payment is requested
• Payee Information: Optional payee details for additional verification
• Bank Integration: Seamless integration with bank’s cheque processing systems

Common Use Cases

• Stolen or lost cheque stop payment requests
• Fraudulent cheque prevention and security measures
• Duplicate cheque issuance corrections
• Post-dated cheque cancellation requests
• Dispute resolution for unauthorized cheque issuance
• Account closure preparation with outstanding cheques
• Emergency stop payments for financial protection

Message Structure

• Field 20: Transaction Reference (mandatory) - Unique stop payment request identifier
• Field 21: Cheque Number (mandatory) - Specific cheque number to be stopped
• Field 30: Date of Issue (mandatory) - Date when cheque was originally issued (YYMMDD)
• Field 32: Currency/Amount (mandatory) - Original cheque amount and currency
• Field 52: Drawer Bank (optional) - Bank on which the cheque was drawn
• Field 59: Payee (optional) - Name and address of cheque payee (no account number)
• Field 75: Queries (optional) - Additional information or reason for stop payment

Network Validation Rules

• Reference Format: Transaction reference must not start/end with ‘/’ or contain ‘//’
• Cheque Number Format: Cheque number must not contain ‘/’ or ‘//’ characters
• Date Validation: Date of issue must be in valid YYMMDD format
• Payee Information: Payee field must not contain account number information
• Amount Validation: Currency and amount must match original cheque details
• Bank Identification: Proper validation of drawer bank information when present
• Query Information: Proper formatting of reason codes and additional information

SRG2025 Status

• Structural Changes: None - MT111 format remains stable for stop payment processing
• Validation Updates: Enhanced validation for fraud prevention and security
• Processing Improvements: Improved handling of urgent stop payment requests
• Compliance Notes: Maintained compatibility with regulatory requirements for stop payments

Integration Considerations

• Banking Systems: Compatible with cheque processing and fraud prevention systems
• API Integration: RESTful API support for modern digital banking platforms
• Processing Requirements: Supports urgent processing with immediate effect
• Compliance Integration: Built-in validation for regulatory stop payment requirements

Relationship to Other Messages

• Triggers: Often triggered by customer requests through digital banking or branch systems
• Responses: Generates MT112 status response messages for stop payment confirmation
• Related: Works with cheque processing systems and account management platforms
• Alternatives: Electronic payment cancellation messages for digital transactions
• Status Updates: May receive status updates about stop payment effectiveness

Fields

field_20: Field20

field_21: Field21NoOption

field_30: Field30

field_32: Field32

field_52: Option<Field52DrawerBank>

field_59: Option<Field59NoOption>

field_75: Option<Field75>

Implementations

impl MT111

pub fn validate() -> &'static str

Get validation rules for this message type

Trait Implementations

impl Clone for MT111

fn clone(&self) -> MT111

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for MT111

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for MT111

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for MT111

fn eq(&self, other: &MT111) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for MT111

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl SwiftMessageBody for MT111

fn message_type() -> &'static str

Get the message type identifier (e.g., “103”, “202”)

fn from_fields( fields: HashMap<String, Vec<(String, usize)>>, ) -> SwiftResult<Self>

Create from field map with sequential consumption tracking

fn from_fields_with_config( fields: HashMap<String, Vec<(String, usize)>>, config: &ParserConfig, ) -> Result<ParseResult<Self>, ParseError>

Create from field map with configuration for error collection

fn to_fields(&self) -> HashMap<String, Vec<String>>

Convert to field map

fn required_fields() -> Vec<&'static str>

Get required field tags for this message type

fn optional_fields() -> Vec<&'static str>

Get optional field tags for this message type

fn to_ordered_fields(&self) -> Vec<(String, String)>

Convert to ordered field list for MT serialization Returns fields in the correct sequence order for multi-sequence messages

impl StructuralPartialEq for MT111