Ohmyfin

Home › Drafters › MT103

Free MT103 message drafter

Build a valid SWIFT MT103 (single customer credit transfer) in the browser. Every field is checked against the SWIFT User Handbook character sets, BIC and IBAN rules, ISO 4217 currencies and SWIFT date format. The output is a real 4-block FIN message you can copy, download or share via link — no signup, no logging of your data.

Message envelope

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

Reference & operation

Sender reference (field 20), bank operation code (23B).

Amount & date

Value date / currency / amount (32A); instructed amount (33B) if FX differs.

Ordering customer

Field 50K — up to 4 lines of 35 chars (account + name + address).

Sending side institutions

Ordering institution and sender's correspondent (BICs).

Receiving side institutions

Receiver's correspondent, intermediary and account-with institution.

Beneficiary customer

Field 59 — up to 4 lines of 35 chars (account + name + address).

Information for the beneficiary

Remittance information (70) and charges (71A: BEN/OUR/SHA).

Sender-to-receiver info

Fill in the form and press Build.

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

{
  "payload": {
    "senderBic": "DEUTDEFFXXX",
    "receiverBic": "NWBKGB2LXXX",
    "uetr": "eb6305c9-1f7f-4def-aaee-805b6e8b3b1a",
    "fields": { ... }
  }
}
    
    
    
  
    

    


    
  
    Frequently asked questions
    
  
    What is an MT103?
    MT103 is the SWIFT FIN message type used to instruct a single customer credit transfer between banks. It carries the sender, beneficiary, amount, currency, charge bearer and references.
    Is this MT103 message valid for sending through SWIFT?
    The output is structurally valid against the SWIFT MT103 specification. To actually send it you need SWIFT Alliance (or an equivalent service bureau) credentials and a BIC connected to FIN — Ohmyfin does not transmit messages.
    What is field 121 (UETR)?
    Field 121 in block 3 carries the Unique End-to-end Transaction Reference, a UUID v4 mandatory under CBPR+ for tracking the payment across the correspondent chain.
    Does Ohmyfin store the data I type?
    No. The form runs client-side; the optional REST API validates and returns the formatted message without persisting any payload.
    Can I share a draft with a colleague?
    Yes — the Share button copies a URL whose # fragment contains your payload (base64-encoded JSON). The fragment never reaches the server, so the share link is private to whoever you send it to.
    

    


    Other drafters: MT202MT202COVMT199