Most cross border payments a UK business sends outside the euro and sterling rails still travel over SWIFT. The same supplier invoice can be credited before you close the banking app one week and sit unexplained for three days the next. That is not random, and it is mostly not about your bank.

This guide explains what SWIFT does, what the data says about speed, where the fees come out, and the handful of decisions that are actually yours to make.

What SWIFT actually does in a cross border payment

SWIFT does not move money. It is a secure messaging network through which banks exchange standardised payment instructions, while the value travels through a chain of correspondent banks that each hold accounts with the next link. Your bank almost never holds an account with your supplier's bank, so the payment hops: your bank debits its nostro account at a correspondent, the correspondent forwards a new instruction, and eventually the beneficiary bank credits your supplier.

The message format changed recently. MT103, the customer credit transfer most finance teams have seen referenced on a remittance advice, was retired from the cross border network in November 2025 and replaced by the ISO 20022 pacs.008 message. That upgrade carries richer, structured data. It does not change how many banks sit in the chain, so it does not by itself make a payment faster or cheaper.

How fast SWIFT payments really are

Swift's own headline is strong: nearly 60% of Swift GPI payments are credited to end beneficiaries within 30 minutes and almost 100% within 24 hours. GPI, the rulebook most banks on the network now follow, added end to end tracking and mandatory status updates.

The headline hides the shape of the distribution, and the shape is what explains your slow payment.

Average versus median

The Bank for International Settlements looked at about 20 million GPI payments across 141 countries and found an average processing time of eight hours and 36 minutes against a median of one hour and 38 minutes. When the average is five times the median, most payments are quick and a long tail is very slow. Your three day payment lives in that tail.

Geography sets the tail. In the same study, the median was under 15 minutes for payments sent to Northern America and parts of Europe, and more than 22 hours for payments sent to Northern Africa and Southern and Central Asia. Of more than 57,000 possible end to end routes, the top 20 carried 15% of volume and 24% of value. A GBP payment to a US supplier runs on a motorway. A payment to a smaller bank in a less busy corridor runs on a series of B roads, each with its own opening hours.

Why the route matters more than the amount

The BIS data points at three drivers: capital controls in the destination country, bank offline hours, and the number of intermediaries. Direction matters too. Payments sent east to west, "with the sun", were nearly 30 minutes faster on average, because they are less likely to arrive at a bank that has closed for the night.

Two things you might expect to matter did not. The payment amount was uncorrelated with speed, and a currency conversion by an intermediary showed no clear link to processing time. A £500 payment and a £500,000 payment on the same route follow the same rules.

Where the money goes: the SWIFT fee stack

A SWIFT payment has up to four cost layers: your provider's sending fee, a fee for each correspondent hop, the FX margin if currencies change, and a receiving fee at the beneficiary's bank. Only the first is usually visible when you press send.

Charge codes: SHA, OUR and BEN

The charge code decides who absorbs the middle of that stack. SHA splits charges: you pay your own provider, and correspondent and receiving fees come out of the amount in transit. OUR puts every fee on the sender, so the beneficiary should receive the full amount. BEN deducts everything from the principal. SHA is the default on most payment forms, which is why a supplier invoice for 10,000 USD so often arrives short and turns into a reconciliation email.

The codes survived the ISO 20022 migration under new names: OUR becomes DEBT, SHA becomes SHAR and BEN becomes CRED, so expect either set on a payment screen.

The FX line you never see

When a conversion happens inside the bank, the margin sits in the rate rather than on the statement. The same guide quotes banks saying so themselves: Bank of America states it profits from markups included in the exchange rate it sets at its discretion, and Wells Fargo states its rate includes a markup set at its sole discretion. A "free" foreign currency wire is priced in the rate.

What a business can control

You cannot choose the correspondent chain. You can choose almost everything around it.

  • •Pick the charge code deliberately. Use OUR when the invoice must settle to the penny. If a customer pays you under SHA, price the shortfall into your terms or ask for OUR in the payment instructions.
  • •Mind the cut off, not just your own. A payment released on Friday afternoon can wait for the next business day at every bank in the chain. The offline hours effect in the BIS data is exactly this.
  • •Capture the UETR. Every GPI payment carries a Unique End to end Transaction Reference. Store it against the invoice in your accounting system. Asking a provider to trace a payment by amount and date is slower than handing over the reference.
  • •Know what the tracker tells you. Since 22 November 2020, banks on the network must confirm when a customer credit transfer is credited, put on hold or passed outside Swift, so "on hold" is a real status you can ask about. GPI also offers stop and recall for payments sent in error.
  • •Complete the details once. Beneficiary name exactly as registered, account or IBAN, BIC, purpose of payment where the corridor requires it. Our guide to IBAN vs SWIFT vs BIC covers which identifier each corridor needs.

When a payment should not go over SWIFT at all

The cheapest SWIFT payment is the one you did not need to send. A euro invoice paid from a euro account over SEPA, or a sterling payment over Faster Payments, never enters the correspondent chain.

This is where the price list does the arguing. EX FI accounts hold balances in 16 or more currencies with a dedicated IBAN where applicable and reach SWIFT, SEPA, FPS, BACS and CHAPS; SEPA and UK FPS payments cost 0.99 GBP, an international SWIFT payment costs 26.40 GBP, internal transfers are free, and FX is 0.70 percent on major pairs and 0.90 percent on minors. On the same euro invoice, the difference between those two rails is 25.41 GBP per payment before any FX, which is the practical case for a multi currency business account that receives each currency on local details.

The regulatory position matters as much as the price. EXFI is a trading name of EX Financial Solutions Ltd, which is not itself authorised or regulated by the FCA and acts as a distributor of payment services provided by Gemba Finance Limited, FCA FRN 804853. Regulated payment services are provided to UK customers only. EX FI accounts are payment accounts, not bank accounts: balances are not covered by the FSCS and are safeguarded in segregated accounts under the Payment Services Regulations 2017. If that model is new to you, start with what an authorised payment institution is.

SWIFT remains the right rail for currencies and countries without a local alternative. For some corridors new rails are appearing, and it is worth reading whether stablecoins can be used for cross border payments before assuming either answer. When you are comparing providers on these criteria, our guide to the best cross border payment services sets them side by side.

FAQ

Is a SWIFT payment the same as a wire transfer? For international payments, usually yes. An international business wire is a bank to bank payment sent across borders over the SWIFT network: SWIFT carries the instruction and correspondent banks settle the funds.

Can a SWIFT payment be stopped after it is sent? Sometimes. Banks on GPI can send a stop and recall request that halts a payment in flight and notifies every bank in the chain. Contact your provider immediately with the UETR, because once the beneficiary is credited a recall depends on the receiving side agreeing.

Does a larger SWIFT payment take longer? Not on GPI. BIS analysis found payment amount uncorrelated with processing time, because every payment follows the same business rules and infrastructure. Compliance reviews on unusual payments are a separate matter and can still add time.

Do SWIFT payments move at weekends? The message can be sent, but each bank processes during its own operating hours. A payment that reaches a bank during its offline hours waits for it to reopen, which is why Friday afternoon payments often credit on Monday.