Ohmyfin

Home › Drafters › MT199

Free MT199 message drafter

Build a SWIFT MT199 free-format customer-payment message in the browser. Used for ad-hoc bank-to-bank communication about an existing customer transfer — e.g. status enquiries, recall requests, charge claims. Validates references, narrative length and SWIFT character set.

Message envelope

BICs (block 1 / 2). UETR (block 3, field 121) is mandatory for MT103/202/202COV under CBPR+; optional on MT199.

References
Narrative

Field 79 — free-format text, multi-line.

Fill in the form and press Build.

    
    
    
    
    
      
    Free REST APIMT199 drafter API
    
      
    100 drafts per IP per day. No auth. CORS open.
    
      
    POST https://ohmyfin.org/api/draft/mt199
Content-Type: application/json

{
  "payload": {
    "senderBic": "DEUTDEFFXXX",
    "receiverBic": "NWBKGB2LXXX",
    "fields": { ... }
  }
}
    
    
    
  
    

    


    
  
    Frequently asked questions
    
  
    When do banks send an MT199?
    MT199 is the free-format companion to the MT103. Banks use it for queries, recall requests, payment investigations and charge claims relating to an existing customer payment.
    Is field 21 mandatory?
    No — field 21 (related reference) is optional on MT199 but should be populated with the reference of the original payment whenever you are corresponding about an existing transaction.
    How long can the narrative be?
    Field 79 allows up to 35 lines of up to 50 characters in the SWIFT z character set. Ohmyfin enforces 35 × 50 by default; some implementations restrict to 35 × 35.
    Does an MT199 need a UETR?
    No — UETR is not mandatory on MT199 because it is a communication message, not a payment. If you do supply one, Ohmyfin validates it as a UUID v4.
    

    


    Other drafters: MT103MT202MT202COV