SWIFT Payments Explained: Fees, Speed, Tracking, and Alternatives

Colton Seal September 9, 2024

SWIFT is a global financial messaging network, not a payment rail that moves money by itself. A SWIFT payment sends standardized instructions between banks, while the funds settle through correspondent banking relationships, account balances, compliance checks, and local clearing steps.

For platforms, that distinction drives the real operating questions: how much the wire costs, how long settlement takes, where tracking breaks down, what data must be collected from the beneficiary, and when a local rail or stablecoin-funded settlement path is a better fit.

Use this guide to understand SWIFT fees, speed, tracking, ISO 20022 changes, and alternatives. If your team needs to route payments across SWIFT, local rails, and other funding paths from one integration, see Routefusion's cross-border payments API.

• Use SWIFT when the corridor, currency, recipient bank, or payment size requires international wire coverage.
• Use local rails when the destination market supports domestic-style payout and cost or delivery speed matters.
• Use a multi-rail payments API when your platform needs SWIFT, local rails, compliance context, tracking, and reconciliation in one operating workflow.

What Is a SWIFT Payment?

SWIFT (Society for Worldwide Interbank Financial Telecommunication) is a messaging network, not a payment system. When a bank initiates a SWIFT payment, it sends a standardized message to the receiving bank instructing it to credit funds to a specific account. The actual money movement happens through correspondent banking relationships and nostro/vostro account settlements.

This distinction matters for platforms because it means SWIFT payments involve multiple intermediaries, each with their own processing times, compliance checks, and fee structures. A single payment from the US to Brazil might pass through two or three correspondent banks before reaching the beneficiary, with each hop adding cost and latency.

SWIFT assigns each member institution a unique identifier called a BIC (Bank Identifier Code), commonly referred to as a SWIFT code. These 8- or 11-character codes route messages to the correct institution and branch. When your platform initiates a SWIFT payment, the BIC of both the sending and receiving banks determines the routing path.

How SWIFT Payments Work: Step by Step

Understanding the mechanics of a SWIFT payment helps platforms anticipate costs, set accurate delivery expectations, and troubleshoot delays. Here is the end-to-end flow for a typical international wire transfer.

1. Payment Initiation

The sending bank (or the platform via its banking partner) creates an MT103 message, the standard SWIFT format for single customer credit transfers. The MT103 contains the sender and beneficiary details, amount, currency, and routing instructions. For platforms using a cross-border payments API, this step is abstracted behind an API call.

2. Correspondent Bank Routing

If the sending and receiving banks do not have a direct relationship, the payment routes through one or more correspondent banks. The sending bank debits its nostro account (its account held at the correspondent bank) and the correspondent forwards the payment toward the beneficiary bank. In corridors with limited banking relationships, payments may pass through two or three intermediaries.

3. Compliance Screening

Each bank in the chain performs sanctions screening, AML checks, and potentially manual compliance review. This is the most common source of delays in SWIFT payments. A payment flagged for review at any point in the chain can be held for hours or days while the compliance team investigates. Incomplete or ambiguous beneficiary information increases the likelihood of holds.

4. Settlement and Credit

Once the payment clears all compliance checks, the beneficiary bank credits the recipient's account. Settlement between correspondent banks happens through nostro/vostro account reconciliation, which may occur on a different timeline than the payment message itself. The recipient typically sees funds within 1-5 business days, depending on the corridor and number of intermediaries.

5. Confirmation and Tracking

The MT103 message serves as proof of payment initiation and is the primary document for tracking and dispute resolution. SWIFT gpi (Global Payments Innovation), launched in 2017, adds end-to-end tracking with a unique reference number (UETR) that follows the payment through every intermediary. As of 2026, over 4,000 banks are live on gpi, and 50% of gpi payments are credited within 30 minutes.

SWIFT Payment Fees and Costs

SWIFT payment costs are one of the most common pain points for platforms processing international payments. The total cost includes multiple fee components that are often opaque until after the payment settles.

Fee Components

• Sending bank wire fee: $15-$50 per transaction, charged by the originating bank
• Correspondent bank fees: $10-$30 per intermediary, deducted from the payment amount (SHA/BEN) or charged separately (OUR)
• Receiving bank fee: $5-$20, charged by the beneficiary bank for incoming international wires
• FX conversion spread: 0.5-3% margin above interbank rates, applied when the sending and receiving currencies differ
• SWIFT network fee: Small per-message fee charged to member banks, typically passed through to customers

Charge Options: OUR, SHA, BEN

SWIFT payments offer three fee allocation methods. OUR means the sender pays all fees, including correspondent bank charges, so the beneficiary receives the full amount. SHA (shared) means the sender pays sending bank fees and the beneficiary absorbs correspondent and receiving bank fees. BEN means the beneficiary pays all fees. For platforms paying contractors or suppliers, OUR ensures predictable delivery amounts but costs more. SHA is the default in most corridors.

Total Cost per Payment

A typical SWIFT payment from the US to Europe costs $25-$50 in fees plus FX spread. For less liquid corridors like US to Southeast Asia or Africa, total costs can reach $40-$80 per transaction. At scale, these costs compound: a platform processing 5,000 international payments per month at an average cost of $40 each spends $200,000 monthly on SWIFT fees alone. This is why platforms processing high volumes increasingly explore local payment rails and hybrid routing strategies.

ISO 20022 Migration: What Changes for SWIFT Payments

The SWIFT network is in the middle of a multi-year migration from the legacy MT message format to ISO 20022, a richer data standard based on XML. This migration, which began in March 2023 and has a coexistence period running through November 2025, is the most significant change to SWIFT messaging infrastructure in decades.

What ISO 20022 Changes

• Structured data: ISO 20022 messages (MX format) carry significantly more structured data than MT messages. Beneficiary addresses, purpose codes, and remittance information are now in standardized fields rather than free-text.
• Richer payment information: The new format supports up to 9,000 characters of remittance data compared to 140 characters in MT103. This enables platforms to include invoice numbers, contract references, and detailed payment descriptions.
• Improved compliance screening: Structured address and entity data reduces false positives in sanctions screening, which should decrease payment delays caused by compliance holds.
• Interoperability: ISO 20022 is already the standard for major domestic payment systems (SEPA, CHAPS, FedWire). Alignment means less format translation between domestic and international payment rails.

Impact on Platforms

For platforms using a payments API, the ISO 20022 migration is largely transparent. Your API provider handles the message formatting. However, platforms should ensure their data collection captures the structured fields that ISO 20022 requires, particularly structured beneficiary addresses (street, city, postal code, country as separate fields) and purpose of payment codes. Payments with complete structured data will process faster and encounter fewer compliance holds.

SWIFT vs Local Payment Rails

SWIFT is not always the optimal rail for international payments. For platforms processing cross-border payments, understanding when to use SWIFT versus local rails is critical for cost optimization and delivery speed.

When SWIFT Is the Right Choice

• High-value B2B payments where fees are a small percentage of the transaction amount
• Corridors where no local rail alternative exists (e.g., payments to certain African or Central Asian markets)
• Payments requiring proof of payment via MT103 for regulatory or contractual reasons
• One-off or infrequent payments where setting up local rail access is not justified

When Local Rails Are Better

• High-volume, lower-value payments (payroll, contractor payments, marketplace disbursements)
• Corridors with mature local rail infrastructure: SEPA (Europe), Faster Payments (UK), SPEI (Mexico), PIX (Brazil), UPI (India)
• Time-sensitive payments: local rails often settle in seconds or minutes versus 1-5 days for SWIFT
• Cost-sensitive use cases: local rail payments typically cost $0.20-$2.00 versus $25-$80 for SWIFT

The most effective approach for platforms is multi-rail routing: use SWIFT for corridors and transaction types where it makes sense, and local rails where they are available and cost-effective. Routefusion's cross-border payments infrastructure supports both SWIFT and local rails through a single API, with intelligent routing that selects the optimal rail based on corridor, amount, and speed requirements.

How Platforms Process SWIFT Payments via API

Platforms building cross-border payment products do not interact with SWIFT directly. Instead, they integrate with a payments API that abstracts the complexity of SWIFT messaging, correspondent banking, and compliance screening behind a developer-friendly interface.

API-First SWIFT Integration

A typical API integration for SWIFT payments involves three core workflows. First, the platform submits a payment request with beneficiary details, amount, and currency. The API provider validates the data, selects the optimal routing path, and initiates the SWIFT message. Second, the platform receives webhook notifications as the payment progresses through the correspondent banking chain, including status updates from SWIFT gpi tracking. Third, the platform queries the API for payment status, fee breakdowns, and delivery confirmation.

What to Look for in a SWIFT API Provider

• Multi-rail support: The best providers offer SWIFT alongside local rails, so your platform can route each payment optimally without managing multiple integrations
• Transparent fee quoting: Pre-transaction fee estimates that include correspondent bank charges, not just the sending bank fee
• gpi tracking integration: Real-time payment status updates through SWIFT gpi, accessible via webhook or API polling
• Structured data support: Full ISO 20022 field support to minimize compliance holds and maximize straight-through processing rates
• FX management: Competitive rates with the ability to lock rates at the time of payment initiation, avoiding spread risk during settlement

Routefusion provides all of these capabilities through a single API integration. Platforms can initiate SWIFT payments, track delivery via gpi, and access FX hedging tools to manage currency risk on international wire transfers. For platforms that also need local rail access, global bank accounts in 10+ currencies provide local clearing capabilities alongside SWIFT.

Frequently Asked Questions

How long does a SWIFT payment take?

Most SWIFT payments settle within 1-3 business days. Payments using SWIFT gpi are faster, with 50% credited within 30 minutes and nearly all completed within 24 hours. Delays beyond 3 days are typically caused by compliance holds, incomplete beneficiary information, or routing through multiple correspondent banks in less liquid corridors.

What is an MT103 and why does it matter?

An MT103 is the standard SWIFT message format for single customer credit transfers. It contains all payment details including sender, beneficiary, amount, and routing information. The MT103 serves as proof of payment initiation and is the primary document used for tracking payments, resolving disputes, and satisfying audit requirements. Under ISO 20022, the MT103 is being replaced by the pacs.008 message, which carries richer structured data.

What is the difference between SWIFT and a wire transfer?

SWIFT is the messaging network used to instruct wire transfers between banks. A wire transfer is the broader term for an electronic fund transfer between financial institutions. Not all wire transfers use SWIFT: domestic wires in the US use Fedwire, European transfers use SEPA, and other countries have their own domestic wire systems. When people refer to international wire transfers, they are almost always talking about SWIFT-routed payments.

Can platforms send SWIFT payments without a bank account?

Platforms cannot send SWIFT payments directly since SWIFT is a bank-to-bank network. However, platforms can access SWIFT through API providers like Routefusion, which maintain the banking relationships and SWIFT connectivity. The platform integrates with the API and the provider handles the SWIFT messaging, correspondent banking, and compliance requirements on the platform's behalf.

How does SWIFT gpi improve international payments?

SWIFT gpi (Global Payments Innovation) adds end-to-end tracking, fee transparency, and speed commitments to SWIFT payments. Each gpi payment receives a unique tracking reference (UETR) that follows it through every intermediary, providing real-time status updates. Banks participating in gpi commit to same-day processing and transparent fee reporting. For platforms, gpi means more predictable delivery times, the ability to provide real-time payment status to end users, and visibility into the fee deductions at each hop in the correspondent chain.