SWIFT explained: the only rail that reaches everywhere, and what that reach costs

A company in Cairo can invoice a buyer in Osaka, a distributor in São Paulo and a contractor in Warsaw, and be paid by all three in currencies none of them share. One network makes that possible, and it is the same network that takes 120 euro out of a 50,000 euro payment on the way.

Both facts are true and they have the same cause. This article covers what SWIFT does that nothing else does, where the cost and the delay enter, and how to decide which payments belong on it.

Key takeaways

Question	Short answer
What is SWIFT?	A secure messaging network between financial institutions. It carries instructions, not money.
How far does it reach?	More than 11,500 institutions across more than 220 countries and territories. No other payment rail comes close.
What can it carry?	Payment instructions in effectively any currency, provided an institution in the chain can settle it.
Who moves the funds?	Correspondent banks, by debiting and crediting accounts they hold with each other.
Why does money arrive short?	Each correspondent in the chain can deduct its own charge from the principal before passing it on.
Is it final?	Yes. Once credited, a SWIFT payment is not reversible on the payer's say-so, which a US ACH payment is.
When should you use it?	Whenever no cheaper rail reaches the destination, and whenever finality matters more than cost.

What SWIFT is

SWIFT stands for the Society for Worldwide Interbank Financial Telecommunication. It is a member-owned cooperative based in Belgium that operates a secure messaging network between financial institutions. It connects more than 11,500 institutions across more than 220 countries and territories and carries an average of more than 53 million FIN messages a day (Swift, checked September 2026).

The single most useful thing to understand about it: SWIFT does not hold your money and does not move your money. It carries the instruction. The money moves separately, through accounts that banks hold with one another.

That distinction is what the rest of this article is about. It explains both the reach and the cost.

What SWIFT does that nothing else does

It is easy to find articles attacking SWIFT on price. They tend to be written by companies selling something else, and they skip the part where SWIFT is the reason international trade works at all outside a handful of currency blocs.

It reaches everywhere. SEPA covers the euro across Europe. ACH covers US dollars inside the United States. Faster Payments covers sterling inside the United Kingdom. Every one of those is a closed domestic or regional system, and a business outside it cannot be reached by it at all. SWIFT is the only network that connects institutions in more than 220 countries and territories, and for most corridors a MENA trading company runs, it is the only option that exists.

It carries almost any currency. Domestic rails carry one currency by design. A SWIFT instruction can be denominated in any currency an institution in the chain is able to settle, which is what lets an Egyptian exporter invoice in US dollars, a Moroccan importer pay in euro and a Gulf trading company settle in yen without holding accounts in three countries.

It is final. Once a SWIFT payment is credited, the payer cannot unilaterally pull it back. That sounds unremarkable until you compare it with the alternative: a US ACH credit can be returned after settlement under the Nacha rules, which is covered in the ACH article. For a first order with a new counterparty, or for an amount that would hurt to lose, finality is worth paying for.

It is traceable. Every payment carries a unique end-to-end transaction reference, the UETR, and the network tracks its status hop by hop. A payment that has stalled can be located and chased at the institution holding it. On informal or intermediated routes, the honest answer to "where is my money" is that nobody knows.

It is the rail trade finance runs on. Letters of credit, documentary collections and bank guarantees are exchanged as SWIFT messages between banks. A business doing documentary trade is on this network whether or not it thinks about payments.

Here is how the reach compares against the rails that beat SWIFT on price.

Rail	Reach	Currencies	Speed	Cost to the payer	Reversible after credit?
SWIFT	220+ countries and territories	Effectively any settleable currency	One to five business days	Fee per payment, plus deductions in transit	No
SEPA	SEPA scheme countries only	Euro only	Same day to next business day, or seconds for instant	Same as a domestic transfer	No
ACH	United States only	US dollars only	One to two business days	Very low	Yes, within the return windows
Domestic local rails	One country each	That country's currency	Usually minutes to hours	Low	Varies by country

Read that table the way a treasurer does. The cheap rails are cheap because they are closed. You do not choose SWIFT over SEPA. You use SEPA where it reaches and SWIFT where it does not, and most businesses trading across MENA, Europe and Asia need both.

How the money moves

Banks that do business with each other keep accounts with each other. A bank in Cairo holds a US dollar account at a bank in New York. The Cairo bank calls that its nostro account, meaning "our account with you". The New York bank calls the same account its vostro, meaning "your account with us".

A cross-border payment is a chain of debits and credits across those accounts, coordinated by SWIFT messages. If the sending bank and the receiving bank hold accounts with each other, the chain has one link. Usually they do not, so the payment routes through one or more intermediaries that both sides have a relationship with.

Here is a payment from an Italian company to an Egyptian supplier, in euro, routed the way it typically is today.

Hop	Institution	What it does	What it can take
1	The payer's bank in Milan	Debits the payer, sends the instruction, applies its own outbound fee	Its published transfer fee, charged to the payer
2	A euro correspondent, often in Germany or France	Debits and credits the relevant accounts, forwards the message	A deduction from the principal, if the charge option allows it
3	A second intermediary, often in the UAE for MENA-bound euro	Same again	A second deduction from the principal
4	The beneficiary's bank in Cairo	Credits the account, applies its inbound charge, may convert to local currency	Its inbound fee, plus any conversion spread

Four institutions, three of which the payer never chose and the beneficiary cannot see. The reach described above and this chain are the same thing viewed from two sides. Global coverage is built out of bilateral relationships, and each relationship in the path has a price.

Where the cost enters

The charge option decides who pays for the hops

Every SWIFT payment instruction carries a charge option. Under the old MT103 message this was field 71A. Under ISO 20022 it is the charge bearer element, and the values map across.

Option	ISO 20022 code	Who pays the intermediaries	What the beneficiary receives
OUR	DEBT	The sender pays all charges	The full amount sent
SHA	SHAR	Sender pays its own bank, beneficiary absorbs the rest	Less than the amount sent
BEN	CRED	The beneficiary pays everything	Less than the amount sent, including the sender's fee

SHA is the default on most corporate banking platforms. It is also the reason most payments arrive short. Nobody chose to deduct from your invoice. The default did.

If you are invoicing a European customer and you need the full amount, the instruction to give them is specific: ask them to send OUR, or DEBT if their bank uses ISO 20022 terminology. Their bank will charge them more. Whether they agree is a commercial conversation, and it is a much easier one to have before the invoice than after the shortfall.

Lifting fees

A lifting fee is a charge an intermediary bank deducts from the principal as the payment passes through. It is not itemised to you, it does not appear on your bank statement as a fee, and it is the reason the credited amount and the invoice amount do not match.

The arithmetic below is illustrative. Substitute your own bank's published schedule and your counterparty's, and the shape stays the same.

Invoice 50,000.00 EUR

Payer's bank outbound fee (paid separately by the payer, SHA)

Intermediary 1 lifting fee (45.00)

Intermediary 2 lifting fee (45.00)

Beneficiary bank inbound fee (30.00)

                             \-------------

Credited to the account 49,880.00 EUR

The lesson is not that the fees are large. On a 50,000 euro payment they are 0.24%, which for a payment that could not have been made any other way is not an outrage. The lesson is that the number of hops, not the size of any single fee, is what you are buying when you choose a route. Two intermediaries cost twice one, and a route through a third country adds a hop by definition.

Where the time enters

The message moves in seconds. The delay is everything around it.

Cut-off times. Every bank in the chain has a daily deadline after which an instruction is processed the next business day. A payment released in Milan at 16:30 can miss a correspondent's cut-off and lose a day before it has left the country.

Value dating. Banks credit funds with a value date, which can sit one or two business days after the funds arrive. The money is at the bank. It is not yours yet.

Non-business days. Weekends and public holidays differ across the chain. A euro payment from Italy to Egypt passes through institutions that observe European holidays and institutions that observe Egyptian ones.

Compliance holds. Every institution in the chain screens the payment against its own sanctions lists and its own risk rules. A name that resembles a listed entity, a missing purpose code, or an unfamiliar country pair can put a payment into manual review at any hop. This is the single most common cause of a payment that has vanished for a week, and it is the price of a network that crosses every sanctions regime in the world.

What changed on 22 November 2025

Swift ended the coexistence period for cross-border payments on 22 November 2025, retiring the legacy MT payment messages in favour of ISO 20022. Institutions still relying on contingency processing or in-flow translation have been charged for it since 1 January 2026 (Swift, checked September 2026).

Two consequences matter to a finance team.

Structured data is now mandatory in places where free text used to be accepted, above all for names and addresses. A beneficiary address typed as one unpunctuated line is more likely to be rejected or held than it was in 2024.

Remittance information is richer. Invoice numbers and references travel with the payment in dedicated fields rather than in a truncated free-text line, which makes reconciliation on the receiving side materially easier if your provider surfaces the data.

When SWIFT is the right choice

Use SWIFT when the destination is outside every cheaper rail's coverage, which for most non-European, non-US corridors is all of the time. Use it when the payment is in a currency the destination's domestic rails do not carry. Use it for a first transaction with a new counterparty, where finality matters more than the fee. And use it for anything attached to a letter of credit or a documentary collection, because the trade documents are already travelling on it.

Use something else when a cheaper rail genuinely reaches the destination. A euro payment from a European customer into euro account details inside the SEPA area is a domestic transfer with no correspondents and no deductions, which is the subject of the SEPA article. A US dollar payment from an American customer into US account details is a domestic ACH credit. In both cases the saving comes from removing hops rather than from negotiating fees.

The decision is per payment, per corridor. A business that runs everything over SWIFT is overpaying on the corridors where a domestic rail reaches, and a business that has replaced SWIFT entirely has quietly stopped selling to the countries it does not cover.

What you can control

You cannot pick the correspondents. You can control four things, and they account for most of the variance.

Agree the charge option in writing before the invoice goes out, and put it on the invoice itself. Give complete structured beneficiary details, with the legal entity name exactly as registered and a real street address. Include the purpose of payment and the invoice reference, which many receiving jurisdictions require and which shortens compliance review everywhere. Then ask your provider for the payment's UETR at the moment of release, so a stalled payment can be traced rather than re-sent.

And where the corridor allows it, reduce the hop count. That is a routing decision, and it is the one with the largest effect on both cost and time.

How TrillioniPay handles it

TrillioniPay is a Canadian FINTRAC-registered money services business. It is not a bank. Account and payment infrastructure is provided through regulated financial partners.

Sending by SWIFT. TrillioniPay executes SWIFT payments through its regulated financial partners, to the destinations those partners cover, net of the markets on its published restricted list. So a customer can pay a supplier in a country no domestic rail reaches from their own market. Check your destination in the eligibility checker before you invoice.

EDITORIAL NOTE, remove before publish. Coverage counts are deliberately absent. When the partner confirms (a) destination countries, (b) payout currencies and which land in local currency, and (c) which destinations are local rail against SWIFT, net the restricted list out and the sentence above can carry two owned figures. Do not substitute Swift's 220+ countries, a partner's coverage, or a competitor's published count. Presenting a borrowed coverage figure as ours is a hard prohibition under Phase 3 section 4.5, and a count that exceeds what the eligibility checker will approve contradicts the sanctions page.

Receiving without SWIFT where a better route exists. For a business in Egypt, Morocco, Algeria or the Gulf receiving euro from Europe, TrillioniPay issues named euro account details through a regulated financial partner in Lithuania. A European customer paying those details sends a domestic euro transfer inside the SEPA area rather than a SWIFT payment across three intermediaries, and the hops that were taking the deduction stop existing for that leg. The named account details explainer sets out what that does and does not give a company incorporated outside Europe.

On charges. Where a payment travels by SWIFT, TrillioniPay shows its own charge before the payment is confirmed. It cannot show another bank's, and no provider that tells you otherwise is describing a network it controls.

TrillioniPay publishes the markets and activities it cannot serve, with reasoning, on its eligibility page. Availability depends on eligibility, KYC/KYB and compliance approval, and on partner coverage at the time your account opens.

Frequently asked questions

Can I send money anywhere in the world by SWIFT? The network reaches institutions in more than 220 countries and territories, which is broader than any alternative. Your own provider's coverage is narrower than the network's, because it depends on which correspondents your provider's partners hold relationships with and on the sanctions rules that apply to both of you. Ask any provider for their payout country and currency list rather than the network's.

Is SWIFT a bank? No. SWIFT is a member-owned cooperative that operates a messaging network. It has no customers who hold accounts and it does not take custody of funds.

Why use SWIFT if SEPA is cheaper? SEPA carries euro between participating European institutions and nothing else. If your counterparty is in Cairo, Casablanca, Dubai or Shanghai, SEPA does not reach them at any price.

Can I find out exactly which banks handled my payment? Your own bank can see the route and the deductions on request, using the payment's UETR. Ask for the tracker record rather than a verbal update.

Why did my payment arrive short when my customer says they paid the full amount? Both of you are right. Your customer sent the full amount. The intermediaries deducted from it in transit, which is what SHA authorises them to do.

Can a SWIFT payment be reversed? Not unilaterally by the payer once it has been credited. A recall can be requested where a payment was sent in error, and the receiving bank is not obliged to return the funds without the beneficiary's agreement. Compare that with a US ACH credit, which can be returned within the network's return windows.

How long should a SWIFT payment take? Between one and five business days is normal for a well-formed payment on an established corridor. Anything longer usually means a compliance hold or a data problem, and both are traceable.

Does ISO 20022 make payments faster? Not directly. It reduces the number of payments that stop for missing or malformed data, which removes one of the common causes of delay.

Sources

Swift, Discover Swift: network reach, connected institutions and message volumes. Checked September 2026.
Swift, ISO 20022 implementation FAQs: end of the CBPR+ coexistence period on 22 November 2025 and charging for contingency measures from 1 January 2026. Checked September 2026.
Nacha Operating Rules, return reason codes and return timeframes, for the ACH comparison. Checked September 2026.