Local rails, SWIFT or crypto: choosing the right way to send money abroad

Sending money to another country is rarely one thing. Behind a single instruction sits a choice of rail — the underlying network that carries value from your account to the recipient's. That choice, more than the headline fee, governs how quickly the payment lands, how much reaches the other side and how predictable the whole thing is. Understanding the three broad options — local rails, SWIFT and crypto payouts — is the difference between a payment that simply works and one that generates a support ticket.

Local rails: fast, cheap, domestic in disguise

A local rail is a country's own domestic payment network — ACH and FedWire in the United States, Faster Payments in the United Kingdom, SEPA across the euro area, FAST in Singapore, and so on. When you hold a virtual account with local details in the destination currency, a payout can travel over these rails as if it were a domestic transfer. Settlement is typically same-day or near-instant, fees are low or flat, and the recipient sees the full amount because there are no intermediary banks skimming charges along the way.

The catch is coverage. Local rails only reach accounts in that specific market and currency. To pay a supplier in euros over SEPA, you first need euros and a euro account with the right local details. This is precisely why multi-currency accounts and cross-border payouts are usually designed together: hold the currency, then send it locally.

SWIFT: universal reach, at a cost

SWIFT is not a payment network so much as a messaging standard that lets banks around the world instruct one another to move money. Its strength is reach — almost any bank in any country can be paid this way. Its weaknesses are cost and opacity. A wire often hops through one or more correspondent banks, each of which may deduct a fee, so the amount that arrives can be smaller than the amount sent. Settlement usually takes one to three business days, and cut-off times matter: miss the daily deadline and your payment waits until the next processing window.

Who pays the charges: SHA, OUR and BEN

Every SWIFT payment carries a fee-bearer instruction that decides who absorbs the correspondent-bank charges. Getting this wrong is one of the most common reasons a beneficiary complains that they were short-changed.

• SHA (shared) — you pay your bank's fees; the beneficiary absorbs any intermediary and receiving-bank charges. This is the market default.
• OUR — you pay all the charges, so the beneficiary receives the full amount. Best when the exact received figure matters, for example a rent or invoice payment.
• BEN — the beneficiary pays all fees, deducted from the amount sent. Rare, and worth flagging clearly to whoever is expecting the funds.

Crypto payouts: fast settlement, new operational duties

Stablecoin payouts move value on a blockchain rather than through the banking system. Settlement is often measured in minutes and runs outside banking hours, which is genuinely useful for weekend or holiday payments. But crypto introduces its own discipline: the receiving wallet address must be exactly correct, the chosen chain must match on both sides, and the recipient needs a way to hold or off-ramp the asset. Availability also depends on where you and the recipient are — digital-asset services are offered only where local law permits.

The best rail is not the cheapest or the fastest in the abstract — it is the one that matches the currency you hold, the deadline you face and the certainty the recipient needs.

In practice most treasuries end up using all three. Local rails for routine, in-currency payments where speed and low cost matter. SWIFT for the long tail of countries and banks nothing else reaches. Crypto for time-critical, out-of-hours settlement between parties equipped to handle it. The skill is not loyalty to one rail but knowing, for each payment, which trade-off you are making.