SWIFT (Society for Worldwide Interbank Financial Telecommunication)

What Is SWIFT?

SWIFT is the member-owned cooperative that operates the dominant cross-border interbank messaging network. It is headquartered in La Hulpe, Belgium, connects more than 11,000 financial institutions across more than 200 countries, and is the layer through which most international wire payments are instructed. SWIFT does not move money itself. It transmits standardised payment messages between member banks, which then settle the underlying funds across correspondent-bank accounts or through central-bank real-time gross settlement systems. The authoritative source on the network, its standards, and its governance is https://www.swift.com.

For a US business paying international contractors or EOR employees outside the United States, SWIFT is almost always the rail behind the scenes. The originator’s bank generates a SWIFT message, routes it through correspondent banks until it reaches the beneficiary bank, and the beneficiary bank credits the receiver’s account.

MT to MX: The 2025 ISO 20022 Migration

SWIFT messages historically used the MT (Message Type) format, a fixed-field text standard dating to the 1970s. Cross-border customer credit transfers used MT103, and bank-to-bank transfers used MT202. These formats are now retired for cross-border interbank messaging.

On 22 November 2025, SWIFT completed the Cross-Border Payments and Reporting Plus (CBPR+) migration to the ISO 20022 MX message standard. From that date:

• MT103 is replaced by pacs.008 (FIToFICustomerCreditTransfer) for customer credit transfers.
• MT202 is replaced by pacs.009 (FinancialInstitutionCreditTransfer) for bank-to-bank transfers.
• MT category 1 and 2 messages are no longer supported for cross-border use.

ISO 20022 is an XML-based open standard maintained by ISO and adopted across major payment systems globally (Fedwire, CHIPS, TARGET2, CHAPS, India’s NPCI rails, and others have all migrated or are migrating). It carries materially richer structured data than MT, including separated debtor and creditor names, structured postal addresses, purpose codes, ultimate-debtor and ultimate-creditor fields, and remittance information that supports automated reconciliation and screening.

SWIFT has set a deadline of November 2026 for full structured-address compliance. After that date, fully unstructured addresses are no longer permitted in cross-border ISO 20022 messages, and a hybrid model (town and country mandatory, other fields optional) applies in the interim. The authoritative migration plan is published on the SWIFT standards portal at https://www.swift.com/standards/iso-20022.

Correspondent Banking and Why Fees Stack

When the originator’s bank does not hold an account directly with the beneficiary’s bank, the SWIFT payment routes through one or more correspondent banks. Each correspondent maintains a nostro account (the sender bank’s holding at the correspondent) and a vostro account (the correspondent’s holding at the sender bank) in the relevant currency, and debits and credits flow along this chain.

Each intermediary in the chain typically deducts a fee from the payment, known as a lifting fee, and may apply an FX margin where a currency conversion occurs at its leg. The combined effect is that a $1,000 USD payment sent from a US bank to an Indian beneficiary in INR can land with $20 to $50 less in nominal USD-equivalent value and at an FX rate that is 1 to 4 percent below the live mid-market rate, before the beneficiary bank’s own inbound charge.

The MX pacs.008 message exposes more of this detail than the legacy MT103, including a charge-bearer indicator and structured remittance information, but the underlying correspondent-bank economics are unchanged.

Settlement Timing

A cross-border SWIFT payment typically arrives in the beneficiary account within one to five business days, with the spread driven by:

• Number of correspondent banks in the chain (more hops, more time).
• Currency of the payment (major currencies clear faster).
• Sanctions, AML, and PEP screening holds at each correspondent.
• Time-zone gaps between sender and receiver.
• Weekend and holiday calendars in each country.

SWIFT gpi (Global Payments Innovation), embedded in the CBPR+ ISO 20022 flow, attaches a Unique End-to-End Transaction Reference (UETR) to each payment and provides tracking across the chain. SWIFT publishes that the majority of gpi payments credit within 30 minutes and almost all within 24 hours, although emerging-market corridors and screening holds can extend timing.

SWIFT Alternatives for USD

For domestic USD large-value payments inside the United States, two rails dominate:

• Fedwire Funds Service, operated by the Federal Reserve Banks, a real-time gross settlement system used for high-value time-critical wires. Each payment is final and irrevocable on settlement (https://www.federalreservehistory.org/essays/fedwire).
• CHIPS (Clearing House Interbank Payments System), operated by The Clearing House, a private multilateral-netting system. CHIPS settles approximately 500,000 payments worth roughly $1.8 trillion daily (https://www.theclearinghouse.org/payment-systems/CHIPS).

Together CHIPS and Fedwire handle roughly 96 percent of large-value USD payments in the US.

For cross-border USD payments to non-US beneficiaries, SWIFT still carries the messaging layer, but the underlying USD settlement between US correspondent banks usually clears on Fedwire or CHIPS, with the foreign correspondent then crediting the beneficiary in local currency or holding the USD in a vostro account.

SWIFT and US Contractor Payments

For US businesses paying contractors or EOR employees outside the United States, SWIFT is the default cross-border rail. The originator pays in USD, the chain converts to local currency at a correspondent or at the beneficiary bank, and the beneficiary receives local currency one to five business days later. The combined cost of correspondent fees and FX margin typically lands in the 2 to 4 percent range for major corridors. See our guide on paying international contractors from the US for a corridor-by-corridor cost view.

How Omnivoo Helps

Omnivoo Contract Management routes US contractor payments on ACH where the contractor is US-based, and on bank rails messaged through SWIFT (with FX disclosed at origination) where the contractor or EOR employee is outside the US. Our payout flow batches invoices, validates IBAN or SWIFT BIC and beneficiary data before origination, attaches a UETR for tracking on supported corridors, and surfaces the all-in cost including correspondent fees and FX margin so finance teams see the real landed cost before approval.