What is an MT103?
SWIFT message, fields
and example.
An MT103 is a SWIFT FIN message for a single customer credit transfer. It records the ordering customer, beneficiary, amount, currency, charges and the UETR in field 121.
A customer-facing SWIFT copy can help you read the payment instruction. It does not independently confirm that the recipient received the money.
- What it contains: payment parties, bank routing information, amounts, charges and a transaction reference.
- MT103 and pacs.008: different message formats can carry the same end-to-end reference.
- Instruction, not arrival: confirm the actual financial outcome directly with your bank.
MT103 at a glance
A quick reference for the message, its blocks and the location of the UETR.
- MESSAGE TYPE
- MT103
- PURPOSE
- Customer credit transfer
- BLOCKS
- 5 · headers, text and trailer
- UETR LOCATION
- Block 3 · field 121
- HOW FIELD 121 APPEARS IN AN MT103
{121:6f8d3a2b-1c44-4f8e-9b21-7d2c9f0a1b22}
BLOCK-BY-BLOCK
- Block 1
- Basic header
- Block 2
- Application header
- Block 3
- User header · field 121 = UETR
- Block 4
- Text · the payment instruction
- Block 5
- Trailer
Read order: 1 → 2 → 3 → 4 → 5. The payment details are in block 4; the UETR is in block 3.
Interactive MT103 Field Explorer
Click a line to see what it means. The UETR sits in field 121, Block 3.
UETR, Field 121 (Block 3)
The user header contains the unique end-to-end reference. Use the original UETR when asking about this payment.
The headers wrap the message; block 4 contains the payment fields. These examples do not represent a real transfer.
MT103 field specifications: the complete list
The principal header reference and payment text fields in message order. A letter “a” means the field has lettered variants; the applicable variant determines its format.
| Field | Name | Status | What it carries |
|---|---|---|---|
| 121 | UETR (Block 3 header) | Mandatory | The unique 36-character reference. Located in the user header, outside the payment text block. |
| 20 | Sender’s Reference | Mandatory | The sending institution’s own transaction reference, up to 16 characters. |
| 13C | Time Indication | Optional | Time information associated with processing or settlement. |
| 23B | Bank Operation Code | Mandatory | The operation being instructed, such as CRED for a credit transfer. |
| 23E | Instruction Code | Optional | Additional handling instructions for the payment. |
| 26T | Transaction Type Code | Optional | A code describing the transaction type. |
| 32A | Value Date / Currency / Interbank Settled Amount | Mandatory | The value date, currency and interbank amount. |
| 33B | Currency / Instructed Amount | Optional | The original instructed currency and amount. |
| 36 | Exchange Rate | Optional | The rate used when the instructed and settlement currencies differ. |
| 50a | Ordering Customer | Mandatory | The payer, including the account and identification details appropriate to the selected variant. |
| 51A | Sending Institution | Optional | The institution sending the transaction in applicable message arrangements. |
| 52a | Ordering Institution | Optional | The ordering customer’s institution when different from the message sender. |
| 53a | Sender’s Correspondent | Optional | The institution through which the sender makes funds available. |
| 54a | Receiver’s Correspondent | Optional | The institution through which the receiver obtains funds. |
| 55a | Third Reimbursement Institution | Optional | An additional institution in the reimbursement arrangement. |
| 56a | Intermediary Institution | Optional | An institution between the receiver and the account-with institution. |
| 57a | Account With Institution | Optional | The institution servicing the beneficiary’s account. |
| 59a | Beneficiary Customer | Mandatory | The recipient’s account or IBAN and identifying details. |
| 70 | Remittance Information | Optional | Information for the recipient, such as an invoice reference. |
| 71A | Details of Charges | Mandatory | Fee allocation: OUR, SHA or BEN. |
| 71F | Sender’s Charges | Optional | Charges deducted by the sender or earlier institutions. |
| 71G | Receiver’s Charges | Optional | Charges due to the receiving institution in applicable arrangements. |
| 72 | Sender to Receiver Information | Optional | Additional bank-to-bank instructions. |
| 77B | Regulatory Reporting | Optional | Information required for regulatory reporting. |
| 77T | Envelope Contents | Optional | Extended information in applicable message variants. |
A customer copy usually contains only the fields used for that payment. Conditional requirements and message variants depend on the applicable banking standards.
MT103 vs MT202 vs MT202COV vs pacs.008
These messages serve different roles in payment instructions and settlement arrangements.
| Message | Purpose | Format | Reference context |
|---|---|---|---|
| MT103 | Single customer credit transfer | SWIFT FIN MT | UETR in field 121 |
| MT202 | Financial institution transfer | SWIFT FIN MT | Check the original message |
| MT202COV | Cover for an underlying customer payment | SWIFT FIN MT | Linked underlying payment |
| pacs.008 | Customer credit transfer | ISO 20022 XML | UETR element |
| pacs.009 | Financial institution credit transfer | ISO 20022 XML | Payment identification |
| pacs.004 | Payment return | ISO 20022 XML | Original payment references |
Why is my MT103 transfer delayed?
A payment instruction can pass through several banks before the receiving bank credits the account. Each institution may have its own processing windows, review requirements and operational queues.
Incomplete details, intermediary routing, currency conversion and non-working days can all affect timing. A document showing an instruction does not show every later event.
Keep the original UETR and bank confirmation together. Ask which bank last reported the payment, whether any action is needed and what the bank’s investigation process is.
UETR.io shows events registered with the transaction system. It does not currently query the live SWIFT gpi network. Ask your bank to confirm the movement and receipt of funds.
Track a transaction using the UETR on your MT103
Find field 121, copy the reference and review the available recorded information.
One UETR connects the record.
Locate the reference. Read the timeline.
Confirm financial outcomes with your bank.
Where the UETR sits in an MT103
The five blocks of the message, with field 121 highlighted in the user header.
The five blocks of an MT103
One header field carries the end-to-end reference.
Technical addressingMessage type and delivery121: 6f8d3a2b-1c44-4f8e-9b21-7d2c9f0a1b22Payment parties, amount, banks and chargesTechnical integrity informationHow does an MT103 work?
The five blocks, the fields that matter and an annotated example.
01/ The five sections of an MT103
Blocks 1 and 2 describe addressing and message delivery. Block 3 contains user-header information, including field 121. Block 4 contains the payment instruction. Block 5 contains trailer information.
02/ The fields that matter
:20:sender’s reference:32A:value date, currency and amount:50a:ordering customer:57a:account-with institution:59a:beneficiary:71A:allocation of charges
03/ Reading an annotated sample MT103
{1:F01RCVBUS33AXXX0000000000}
{2:O1031200250527SNDBGB2LAXXX00000000002505271201N}
{3:{121:6f8d3a2b-1c44-4f8e-9b21-7d2c9f0a1b22}}
:20:CUST-REF-12345
:23B:CRED
:32A:250527USD25000,00
:50K:/12345678 ACME EXPORTS LIMITED
:52A:SNDBGB2LXXX
:57A:RCVBUS33XXX
:59:/87654321 GLOBAL IMPORTS INC
:70:INV-2025-0421
:71A:OUR
{5:{CHK:000000000000}}
In this illustrative example, ACME Exports instructs a USD 25,000 payment to Global Imports. The UETR is the reference in block 3; OUR describes the instructed allocation of fees.
Anatomy of an MT103
{1:F01RCVBUS33AXXX0000000000}Basic header{2:O1031200250527SNDBGB2LAXXX00000000002505271201N}Application header{3:{121:6f8d3a2b-1c44-4f8e-9b21-7d2c9f0a1b22}}UETR, Field 121 (Block 3):20:CUST-REF-12345Sender’s reference:23B:CREDBank operation code:32A:250527USD25000,00Value date, currency and amount:50K:/12345678 ACME EXPORTS LIMITEDOrdering customer:52A:SNDBGB2LXXXOrdering institution:57A:RCVBUS33XXXAccount with institution:59:/87654321 GLOBAL IMPORTS INCBeneficiary customer:70:INV-2025-0421Remittance information:71A:OURDetails of charges{5:{CHK:000000000000}}TrailerIs the MT103 being replaced by ISO 20022?
ISO 20022 uses structured XML messages. The pacs.008 customer credit transfer message serves the customer-payment role associated with MT103 in the CBPR+ migration.
Message formats and customer-facing confirmations are different things. A bank may provide a confirmation in an MT103-style layout; ask the issuing bank what the document represents.
The 36-character UETR reference can connect the same payment across formats. In an MT103 it is in block 3, field 121. In pacs.008 it appears as a UETR element within payment identification.
Richer message structures can carry more detailed party and remittance data. Your bank can explain its current message and address requirements.
MT103 → pacs.008
{3:{121:6f8d3a2b-1c44-4f8e-9b21-7d2c9f0a1b22}}<UETR>6f8d3a2b-1c44-4f8e-9b21-7d2c9f0a1b22</UETR>Is an MT103 proof of payment?
A genuine bank-issued copy records payment-instruction information. It is useful for checking the payer, beneficiary, amount, value date and bank route. It does not by itself establish that funds reached the beneficiary’s account.
Source matters. Obtain the document directly from the bank or verify it with the issuing bank. An image or PDF forwarded by an unknown person is not independent confirmation that the payment exists.
A real UETR can be copied onto a misleading document. A format check cannot authenticate the document, and a tracking result should be read in the context of who recorded the event and what it actually confirms.
Confirm receipt through your own bank account and the bank servicing it. If a payment is missing, ask the sender’s bank for an investigation using the original reference.
How do I get an MT103 SWIFT copy from my bank?
Ask the sending bank for its payment confirmation or SWIFT copy, including the UETR. The request process, availability and any charges depend on the bank.
Identify the transfer
Have the payment date, amount, currency and customer reference ready.
Open the request
Use the bank’s secure portal, relationship manager or branch support.
Specify what you need
Ask for the bank-issued payment confirmation with the original UETR.
Check the details
Confirm the parties and reference, then ask your bank about the actual payment outcome.