SWIFT

SWIFT is the plumbing of international finance: not glamorous, rarely visible to end users, but foundational to how money moves between countries. Understanding SWIFT is prerequisite to understanding why cross-border payments take 1–5 days, cost 2–7% in fees and FX spread, and sometimes fail without explanation — and what the current modernisation push (ISO 20022, SWIFT GPI) is attempting to fix.

What SWIFT Actually Does

SWIFT transmits payment instructions as standardised messages between banks. When a company in Singapore instructs its bank to pay a supplier in Germany, the Singapore bank does not directly debit the German bank. Instead:

1. The Singapore bank sends a SWIFT message (MT103 — Customer Credit Transfer) to a correspondent bank with a relationship to the German banking system
2. The correspondent bank forwards (or acts on) the message, debiting the Singapore bank’s nostro account held at the correspondent
3. The correspondent credits the German bank, which credits the beneficiary

SWIFT is the messaging layer; actual funds movement happens through bilateral correspondent account relationships and local clearing systems (TARGET2 in the EU, Fedwire in the US, etc.).

MT vs. MX (ISO 20022 Migration)

MT messages (Message Types): The legacy SWIFT format, developed in the 1970s. Structured but limited — fixed field lengths, limited data capacity, no structured remittance information. Common types:

• MT103: Single customer credit transfer (the core cross-border payment message)
• MT202: Financial institution transfer
• MT940/MT950: Account statement messages

MX messages (ISO 20022): The modern XML-based standard. Richer data structures, structured remittance information (invoice references, purpose codes), better support for regulatory reporting and AML. Migration for cross-border payments and cash management messages was mandated by SWIFT for all members by November 2025. Legacy MT messages for cross-border payments are deprecated post-migration.

The ISO 20022 migration matters for operators because richer payment data improves STP (straight-through processing) rates, reduces manual intervention in reconciliation, and enables better AML screening — but it requires banks and corporates to update systems to consume and produce MX messages.

SWIFT GPI

SWIFT GPI (Global Payments Innovation) is the industry initiative launched in 2017 to address the core weaknesses of correspondent banking: opacity, speed, and predictability.

GPI commitments by member banks:

• Same-day processing: Most payments processed within 24 hours; >50% within 30 minutes end-to-end
• Full fee transparency: Deduction fees applied by intermediaries are visible to the originator and beneficiary
• End-to-end tracking: GPI payments carry a Unique End-to-end Transaction Reference (UETR) — a tracking ID that allows banks and corporates to track payment status through every correspondent hop in real time (similar to parcel tracking)
• Unaltered remittance data: Intermediaries must pass through remittance information without modification

As of 2024, over 4,500 financial institutions in 200+ countries are SWIFT GPI members, and the majority of cross-border SWIFT payments include GPI tracking. For operators with significant international supplier payments or B2B AR collections, GPI-enabled banking reduces enquiry volume and provides status certainty that pre-GPI SWIFT could not offer.

SWIFT Limitations for Operators

Despite improvements, SWIFT correspondent banking has structural characteristics that alternative rails are designed to address:

Cost: Correspondent bank fees, FX conversion spreads, and intermediary deductions mean total cross-border payment cost of 2–7% for SME senders, even with GPI improvements. Fintech intermediaries (Wise, Airwallex, Nium) bypass SWIFT for many corridors by using local rails at both ends.

Speed: Even with GPI, some corridors (especially to emerging markets with limited GPI bank coverage) take 1–5 business days. True real-time cross-border settlement is only available where bilateral fast payment arrangements exist (e.g., Singapore-Thailand PromptPay/PayNow link).

Sanctions and compliance: SWIFT membership is subject to geopolitical pressure. Russia’s major banks were disconnected from SWIFT in 2022; Iran’s banks have been excluded since 2012. Operators dealing with sanctioned countries have no SWIFT path.

Opacity in non-GPI corridors: Outside GPI-covered corridors, tracking a payment through 2–3 correspondent hops remains difficult. Payments can be delayed at any hop without automated notification.

For high-volume cross-border payment operations, treasury teams benchmark their bank’s SWIFT performance against fintech alternatives for each material corridor — particularly for supplier payments, cross-border payroll, and marketplace disbursements.