SWIFT messages are standardized electronic instructions that banks send each other to coordinate cross-border payments, trade finance, and securities transactions. They carry the order to move money rather than the money itself; the actual funds settle through correspondent accounts the banks hold with each other or through central bank systems. The network connects more than 11,000 financial institutions across 200-plus countries, which is why a wire request composed in Tokyo can be read and processed identically by a bank in Frankfurt.1Swift. Our Story
Instruction, Not Delivery
The easiest way to picture a SWIFT message is as a secure, highly structured email between banks that says “move $5,000 from Account A to Account B.” The receiving bank reads the instruction, verifies it, and then settles the money separately through accounts it already maintains with the sending bank or an intermediary.
Standardization is what makes the system work at scale. Every field, code, and tag follows a shared specification, so banks operating in different languages, time zones, and regulatory regimes can process incoming messages automatically rather than having humans interpret each one. That uniformity is what lets high-volume international payments clear in hours instead of days.
The BIC: The Address on the Envelope
Every institution on the network has a Business Identifier Code, or BIC, governed by ISO 9362.2Swift. Business Identifier Code (BIC) The base BIC is eight characters: four for the institution, two for the country (using ISO 3166-1 country codes), and two for the city or location. A three-character branch code can be added to make an eleven-character BIC when a specific branch needs to be reached. When no branch is specified, “XXX” is appended, routing the message to the main office.3Swift. Branch Identifier for Swift BIC
A wrong BIC is one of the most common reasons international wires get delayed or rejected. One mistyped character can send a message to the wrong institution or trigger an automatic rejection. Confirm the code directly with your recipient rather than relying on online lookup tools, which sometimes return outdated codes for banks that have merged or restructured.
What’s Inside the Message
Every SWIFT message is built from numbered tags, each defining what sits in that slot. The ones that matter most on a payment include:
- Tag 20, the sender’s reference, a unique identifier used to track the transaction through both banks’ systems.4ISO 15022. MT581 – Field 20 Transaction Reference Number
- Tag 32A, which carries the value date, currency code, and amount. The value date is the settlement target, not the date the message was sent.5ISO20022. MTN90 – Field 32a Value Date, Currency Code, Amount
- Tag 50K, the ordering customer, giving the name and address of whoever initiated the payment. Banks need this for compliance and anti-money laundering checks.
- Tag 71A, the charge code, which decides who pays the transfer fees.
Banks validate every field before transmission. A formatting error in a single tag can bounce the whole message, which is where delays on time-sensitive transfers tend to originate.
Message Types and the MT103
The legacy MT (Message Type) system groups messages into numbered categories by purpose. Most consumers only ever encounter one of them.
- MT1xx covers customer payments. The MT103, a single customer credit transfer, is the workhorse behind most international wires people initiate at their bank.
- MT2xx handles bank-to-bank transfers, such as settling foreign exchange trades.
- MT3xx deals with treasury and foreign exchange confirmations.
- MT4xx is used for documentary collections.
- MT5xx manages securities trade confirmations and settlements.
- MT7xx carries documentary credits and guarantees, including letters of credit.
- MT9xx delivers account statements and balance reports.
Each category has its own required fields tailored to the transaction. An MT103 needs ordering customer details and a charge code; an MT700 letter of credit needs shipment dates, goods descriptions, and documentary requirements. The numbering lets receiving banks route each message automatically to the right internal department.
Who Pays the Fees: OUR, SHA, and BEN
Field 71A, the charge code, is the detail that most often catches senders off guard. Three options exist:
- OUR: the sender pays all fees, including intermediary bank charges, and the recipient is supposed to receive the full amount.
- SHA (shared): the sender pays the originating bank’s fee, and the recipient absorbs any charges from intermediary or receiving banks. The beneficiary usually ends up with slightly less than the stated amount.
- BEN (beneficiary): the recipient pays all fees. Every charge along the way gets deducted before the money arrives.
If you need the recipient to receive an exact amount, OUR is the only reliable choice. SHA is the common default at many banks, which is why beneficiaries so often notice the credited amount is a few dollars short of what was promised. That shortfall is intermediary bank fees. Outgoing international wire fees at major U.S. banks generally run between $25 and $50, with some banks charging more for in-person or phone-initiated transfers than for online ones.
The Shift to ISO 20022
For decades, SWIFT messages used the MT format with its numbered tags and relatively rigid structure. ISO 20022 is the replacement standard, built on XML, that carries far richer data with each payment. Where an MT103 might cram remittance details into a free-text field, ISO 20022 provides structured elements for invoice numbers, tax references, and detailed creditor and debtor information.6Citi. The Importance of Data Structure – ISO 20022 and the Future of Payments
The migration completed on November 22, 2025, when the coexistence period between MT and ISO 20022 formats ended for cross-border payment instructions between financial institutions. Legacy MT payment instructions are no longer delivered on the network, though a conversion service temporarily handles stragglers.7Swift. Global Financial Community Completes Switch to ISO 20022 The next deadline is November 2026, when payments containing fully unstructured addresses (missing a structured town name and country) will be rejected.8Swift. ISO 20022 in Bytes for Payments – One Month to Go If your bank is asking for more detailed beneficiary address information than it used to, that rule is why.
Tracking a Payment with SWIFT gpi
Sending an international wire used to feel like dropping a letter in a mailbox. You knew it left; you had no visibility into where it was or when it would arrive. SWIFT gpi (Global Payments Innovation) changed that by assigning every payment a Unique End-to-End Transaction Reference (UETR) that follows the transfer in real time from initiation to final credit.9Swift. Swift GPI
Since November 2020, supervised financial institutions have been required to confirm when a customer credit transfer is credited to the beneficiary, placed on hold, or transferred outside the SWIFT network.9Swift. Swift GPI The originating bank sees each status as it happens, which is why your bank can now tell you with more precision where your payment is rather than quoting a vague three-to-five-business-day window. The gpi Tracker also shows what each bank in the chain charged along the way.
Why Wires Get Delayed: Sanctions and the Travel Rule
Every SWIFT message processed by a U.S. financial institution is screened against the Office of Foreign Assets Control’s Specially Designated Nationals (SDN) list before execution.10FFIEC. BSA/AML Manual Office of Foreign Assets Control OFAC requires U.S. entities to avoid transactions with sanctioned individuals, entities, or countries.11Office of Foreign Assets Control. Compliance for Internet, Web Based Activities, and Personal Communications When a payment contains a name, entity, or country that matches the SDN list, the bank’s compliance system flags or blocks the transaction for manual review. That is often the real reason behind an unexplained delay.
The penalties for getting sanctions compliance wrong are steep. Civil penalties can reach the greater of $250,000 or twice the transaction value. Willful violations can bring criminal penalties of up to $1 million in fines and 20 years in prison.12Office of Foreign Assets Control. How Will the Treasury Department Enforce the Iranian Financial Sanctions Regulations (IFSR) Banks invest heavily in automated screening because the stakes make manual oversight impractical at the volume they process.
Separately, international transfers of $3,000 or more trigger the FinCEN Travel Rule. The originating bank must pass identifying information about both the sender and the recipient to each bank in the payment chain, and these records must be retained for five years.13Financial Crimes Enforcement Network. FinCEN Advisory – Funds Travel Regulations Questions and Answers That is why your bank asks for so much detail about the beneficiary when you initiate a wire.
When Something Goes Wrong
Mistakes happen more often than the industry likes to admit. A wrong account number, an incorrect BIC, or a transposed digit in the amount can send money to the wrong place or get the payment stuck at an intermediary. Once a message is sent and acknowledged, unwinding it is far harder than sending it was.
SWIFT’s gpi Stop and Recall service (gSRP) gives banks a formal process to request that a payment be stopped or returned. The originating bank sends a recall request using specific message types (MT 192 or MT 199), and each bank in the chain responds with a status update.14Swift. Swift GPI Stop and Recall Rulebook Common Scenarios A recall is a request, not a command. If the funds have already been credited to the beneficiary, the receiving bank typically needs that beneficiary’s consent to return them. If the beneficiary refuses or has already withdrawn the money, the originating bank has limited options.
In the United States, bank liability for wire transfer errors sits under Uniform Commercial Code Article 4A. If a bank improperly executes a payment order, it is liable to the originator for the expenses in the funds transfer and for incidental expenses and interest losses from the error. Consequential damages beyond that are only recoverable if there is an express written agreement with the bank. Reasonable attorney’s fees are available if the bank refuses a compensation demand before litigation.15Legal Information Institute (LII) / Cornell Law School. UCC 4A-305 – Liability for Late or Improper Execution or Failure to Execute Payment Order The practical takeaway is simple: verify every field before you authorize a wire. Recovering from an error after the fact is slow, uncertain, and limited in what you can claim.