API and JSON in banking: what they actually do
Why an API call never touches the ledger, and why a JSON payload on its own is not proof that a payment happened.
SWIFT is a global messaging system that connects thousands of banks and financial institutions.
Published
In today’s global economy, sending and receiving money across borders is a daily necessity for individuals, businesses, and financial institutions. With trillions of dollars transferred internationally every year, banks rely on the SWIFT network to ensure security, accuracy, and compliance. Among the different message types in SWIFT, the MT103 Document plays a critical role in international payments.
The MT103 Document is often treated as the “official receipt” of a cross‑border bank transfer—except it comes from the standardized SWIFT messaging system. Below, we’ll explain what it is, how it works, what’s inside it, and how you can request and read one.
SWIFT (Society for Worldwide Interbank Financial Telecommunication) is a global messaging system that connects thousands of banks and financial institutions. SWIFT doesn’t move money; it securely transmits payment instructions between institutions so funds can be settled by the banks involved.
SWIFT messages are grouped into MT (Message Types), each serving a different purpose. For example:
Among these, MT103 is the most recognized by customers because it’s issued for cross‑border payments between individuals or companies.
An MT103 Document is a standardized SWIFT message confirming that a single international credit transfer has been initiated. It contains the key details of the payment—sender, receiver, amount, currency, dates, and references—so banks and customers can track and verify the transaction.
While layouts may vary by bank system, a typical MT103 includes:
:20:):32A:):50K: or :50A:/:50F:):59: or :59A:):71A: — OUR/SHA/BEN):70:):20: TXREF123456789
:32A: 250824 USD 50000,
:50K: JOHN DOE, 123 MAIN ST, NEW YORK US
:59: ACME GMBH, BERLIN DE
:70: INVOICE 2025-081
:71A: SHA
For many counterparties, the MT103 serves as a strong confirmation that funds are on their way, allowing shipment or service delivery to proceed while the payment settles.
MT103 data supports compliance checks and helps institutions satisfy AML and audit requirements by documenting the parties, purpose, and routing.
If a transfer is delayed or appears missing, the MT103’s references and routing enable banks to trace the payment path and locate the hold‑up.
In short, MT103 is customer‑facing; MT202 is bank‑facing.
A bank receipt confirms your instruction, but an MT103 is a standardized SWIFT message with deeper data, making it more useful for tracing and counterpart verification.
A valid MT103 can only be issued by a SWIFT‑connected sending bank (or a regulated provider operating via a sponsoring bank). Intermediaries cannot create a legitimate MT103 independently.
If you used a money transfer provider, you can typically download the MT103 (or equivalent SWIFT copy) from your dashboard or ask support. See helpful references from Wise, Flywire, and Money Mover.
An MT103 shows that a payment was sent, not that funds have cleared into the beneficiary’s account. It’s evidence of instruction, not final settlement.
Depending on bank processes and compliance checks, obtaining a copy can take 1–3 working days.
| Field Code | Meaning |
|---|---|
:20: | Transaction Reference Number |
:32A: | Value Date, Currency, Amount |
:50K: | Ordering Customer |
:59: | Beneficiary Customer |
:70: | Remittance Information |
:71A: | Details of Charges (OUR/SHA/BEN) |
Only accept MT103 copies issued by your bank or regulated provider. Be cautious of altered PDFs or suspicious “screenshots.”
MT103s contain sensitive personal and banking data. Store them securely and share them only with trusted counterparties.
A U.S. company wires USD 50,000 to a German supplier. After initiating the transfer, the bank provides the MT103. The supplier uses it as evidence the funds are on the way, prepares shipment, and both banks can trace the transaction using the MT103 references if needed.
MT103 covers single customer credit transfers; MT202 is bank‑to‑bank settlement/cover. They serve different parties and purposes.
No. It confirms the payment was initiated but doesn’t prove the beneficiary has received the funds.
Usually 1–3 working days after initiating the transfer, subject to bank processes.
Yes. Most institutions can provide a copy upon request after your cross‑border payment has been sent.
Not exactly. A receipt is internal; the MT103 is a standardized SWIFT message with detailed data for tracing.
Policy differences. Some banks only release MT103s for investigations or specific compliance reasons.
The MT103 Document is central to cross‑border transfers: it confirms payment instructions, supports compliance, and enables tracing. Whether you’re paying suppliers or sending tuition abroad, understanding MT103 helps you communicate with banks and counterparties more effectively. For further reading, see helpful guides from Wise, Flywire, and Money Mover.
Why an API call never touches the ledger, and why a JSON payload on its own is not proof that a payment happened.
What L2L really means, how banks move money between ledgers in practice, and where ILP does and does not fit.
General explanations only get you so far. Bring us the specifics and you get a written answer, including the ones we turn down.
Ask a specific question