What Is MT103 in Banking? Meaning, Format and How to Get One

An MT103 is a standardised SWIFT message that banks use to send a single customer credit transfer across borders. It records who paid whom, how much, in which currency and who covered the fees.

That is why it works as a bank-issued confirmation that a SWIFT wire transfer was sent.

In brief:

• What it is: a single customer credit transfer message sent bank-to-bank over the SWIFT network.
• What it proves: that a payment was sent, with amount, currency, date and fee terms, not that it has cleared.
• How to get it: the sender's bank issues it, and you can also request it from your own bank.
• 2026 update: for bank-to-bank flows, MT103 moved to ISO 20022 (PACS.008) from 22 November 2025.

This guide covers what an MT103 means, the fields inside it, how to read one, how to get it from your bank, and what ISO 20022 changes for Indian exporters who receive payments through Xflow receiving accounts.

MT103 stands for Message Type 103. It is the SWIFT format for a single customer credit transfer, meaning one named payer sending funds to one named beneficiary through the correspondent banking network.

Banks generate the MT103 the moment they release an outbound wire. It travels with the payment through any intermediary banks until it reaches the beneficiary's bank.

Because it carries the full audit trail of the instruction, exporters and finance teams treat it as the reference document for a cross-border payment. For the mechanics of the wider network, see how SWIFT payment works.

An MT103 has three practical uses for a business receiving money from abroad:

• Confirmation of sending: it shows the payer's bank released the funds, with the value date and amount.
• Payment tracing: each message carries a reference that lets banks locate a stuck or delayed wire.
• Reconciliation and audit: the remittance field and references help match the credit to an invoice for your books and compliance filings.

An MT103 is built from tagged fields, each holding one piece of the transfer. The mandatory five (20, 23B, 32A, 50a, 59a and 71A) form the core proof of what moved and between whom.

The table below breaks down the fields you will most often need to read.

Field 71A is worth understanding before you invoice. OUR means the sender covers all charges, so you receive the full amount.

SHA means each side pays its own bank, and intermediary fees may be deducted in transit. BEN means you, the beneficiary, absorb every charge.

If your USD invoice keeps landing short, the charge code is usually why. Our guide on international wire transfer fees covers how to reduce that leakage.

Reading a raw MT103 is easier once you see the tags in sequence. Here is a simplified, illustrative extract for a USD 4,000 payment from a US client to an Indian exporter:

Line by line: reference XF20260715ABCD (20), a credit transfer (23B), USD 4,000 value-dated 15 July 2026 (32A), the US payer (50K), the Indian beneficiary (59), the invoice reference (70), and OUR charges so the exporter receives the full USD 4,000 (71A).

The UTR-style reference lets your bank track the wire, similar to a domestic UTR number.

This is where many exporters get caught out. An MT103 is proof that a payment was instructed and sent, not a guarantee that the money has cleared into your account or that it cannot be recalled.

Funds can still be delayed by intermediary banks, held for compliance checks, or, in rare cases, reversed.

Treat these phrases as red flags, because they are common in advance-fee fraud rather than real banking:

• "MT103 one-way", "MT103/23" or "MT103 manual download" are not standard SWIFT terms.
• Anyone asking for a fee to "unlock", "release" or "download" blocked MT103 funds is describing a scam.
• A counterparty sending only an MT103 as a reason to ship goods before the credit appears in your account.

The safe rule: confirm the money is in your account, not that a document exists. A receiving setup that shows you the credit directly removes the need to chase paperwork from the sender's bank.

If you sent a wire, or need the document as a receiver, you can request the MT103:

Step 1: Ask the sender first.

The payer's bank issues the MT103, so the quickest route is your client requesting it from their bank.

Step 2: Request it from your own bank.

As beneficiary, your Indian bank can often retrieve the inbound message linked to the credit.

Step 3: Give the transaction details.

The date, amount, currency and beneficiary account help the bank locate the exact message.

Traditional banks may charge for the document and can take several days to produce it. Modern receiving platforms surface the equivalent confirmation and remittance detail without a manual request, which matters when a client needs proof the same day.

The MT103 alone tells you the wire was sent. To see where it is in transit, banks use the UETR, a 36-character Unique End-to-End Transaction Reference carried with the message, together with SWIFT gpi tracking.

Ask your bank to trace the UETR if a payment is delayed. For realistic timelines, see SWIFT transfer time.

Both are SWIFT payment messages, but they serve different legs of a transfer.

For an exporter, the MT103 is the document that matters, because it names you and your client. The MT202 moves funds between the banks in the background.

There is an important 2026 update. SWIFT's coexistence period for legacy MT payment messages in bank-to-bank cross-border flows ended on 22 November 2025, per SWIFT.

Those flows now use ISO 20022 MX messages, where PACS.008 is the structured equivalent of the MT103. In practice, the concept you rely on, a confirmed customer credit transfer with richer data, continues under a new format.

For most exporters nothing changes day to day: you still receive a confirmation and remittance detail for each payment.

The value of ISO 20022 is more structured data, which improves reconciliation and compliance matching over time. If you ask your bank for the old document, expect it to point you to the ISO 20022 confirmation instead.

If you receive payments from overseas clients, the MT103 is documentary support for reconciliation and RBI compliance.

It helps match a credit to an invoice and close it in EDPMS. The remittance field (70), carrying your invoice number, lets your accountant tie the receipt to the export and the correct RBI purpose code for inward remittance.

The slow part is rarely the MT103 itself. It is the correspondent-banking chain: intermediary fees deducted under SHA, days of transit, and manual requests when a client wants proof.

This is the problem cross-border payments for ITeS are built to solve.

You share local account details with your client, and the payment settles to your Indian bank account the next business day (T+1) at a live mid-market rate. Xflow auto-issues an eFIRA as your inward-remittance proof, so you are not chasing a bank document.

Xflow holds final RBI Payment Aggregator Cross-Border (PA-CB) authorisation for exports and imports, is ISO 27001 and SOC 2 certified, and works with AD-1 banks and JP Morgan Chase.

The compliance trail your bank once produced from an MT103 stays intact. EdTech exporter TeachEdison cut cross-border costs by 60% versus SWIFT wires after switching.

For businesses weighing options, SWIFT payment alternatives compares the routes for receiving money in India, and foreign inward remittance explains the paperwork that follows every credit.

It also helps to know the difference between FIRC vs FIRA. Understanding your client's SWIFT code and the likely bank charges for foreign remittance rounds out the picture.