Cross-border payout costs rarely arrive as one big number. They arrive as a fee here, a spread there, a €20 minimum on a €400 wire, an intermediary deduction nobody authorised — small enough individually that no single payment justifies changing anything. Add them up across a year of supplier and contractor payouts, and they quietly become one of the larger operating lines a business never budgeted for.
The good news is that most of that cost is not the price of moving money — it's the price of moving money a particular way. Here are the five operational changes that reliably shrink it, roughly in order of how much they save.
1. Route local, and save SWIFT for when nothing else reaches
The single most expensive habit in cross-border payouts is defaulting to SWIFT wires for destinations that a local rail could reach. A SWIFT payment costs more at the source — 0.5% with a €20 minimum on our business tier, versus 0.2% with a €0.50 minimum for local SEPA, FPS, or ACH payouts — and that's before the part you don't control: correspondent banks along the route may deduct their own handling fees from the amount in transit, so the beneficiary receives less than you sent, and someone has to reconcile the difference.
A EUR payout to an EEA supplier should travel by SEPA. A GBP payout to the UK should travel by Faster Payments. A domestic USD payout should travel by ACH. SWIFT earns its cost when the destination genuinely sits outside local rails — not as the default for anything with a foreign address.
2. Batch your payment runs
Per-payment minimums and fixed fees don't care how large a payment is — which means they punish frequency, not volume. A business paying the same contractor four times a month pays four minimums, generates four bank statement lines, and reconciles four transactions, for the same money that one consolidated run would move with one of each.
Moving from ad-hoc payouts to one or two scheduled runs per month does three things at once: it collapses fixed fees, it turns reconciliation into a single predictable event, and — often overlooked — it lets you convert currency once per run at a better effective rate, instead of many small conversions each carrying their own spread.
3. Decide where the FX happens — because somewhere, it will
Every cross-currency payout involves a conversion. The only question is who performs it and at what rate — and the difference between the answers is one of the biggest hidden costs in international payments.
If you send EUR to a supplier's USD account, the conversion happens at the beneficiary's bank, at a rate you never see, never agreed to, and that is almost always the worst rate in the entire chain. If instead you convert EUR to USD in your own account — at a disclosed rate, from 0.4% over mid-market — and send USD to a USD account, the conversion happened where you could see it, compare it, and time it.
4. Use stablecoin settlement on the corridors where banking rails are worst
Not every corridor deserves a stablecoin — EUR to Germany over SEPA is already fast and nearly free. But on corridors where wires are slow, expensive, or unreliable, settling suppliers in USDT or USDC changes the cost structure entirely: conversion from 0.4% plus a fixed network fee, settlement in minutes rather than days, and no correspondent bank deducting fees in transit.
The prerequisite is that the recipient can actually receive and off-ramp the stablecoin cheaply — which makes this a per-corridor decision, agreed with each counterparty, not a blanket policy. Where it fits, it tends to fit dramatically: the corridors with the worst banking rails are usually exactly the ones where stablecoin acceptance is strongest.
5. Hold balances in the currencies you pay out — and only convert the net
A business that collects EUR revenue and pays USD suppliers converts constantly. A business that collects some USD revenue and pays USD suppliers from that same balance converts only the shortfall. This is natural hedging, and a multi-currency account makes it free to implement: hold EUR, GBP, and USD side by side, let inflows in each currency fund outflows in the same currency, and convert only your net exposure — once, deliberately, at a moment you choose.
For a business with two-way flows in a currency, this can cut total FX volume — and therefore total FX cost — by half or more, without changing a single supplier relationship.
What it adds up to
Take an illustrative business making 100 payouts a month, averaging €800 each, half of them cross-currency:
| Habit | Default approach | Optimised approach |
|---|---|---|
| Routing | SWIFT by default: 0.5%, €20 min, plus in-transit deductions | Local rails where possible: 0.2%, €0.50 min, full amount arrives |
| Frequency | Ad-hoc payouts as invoices arrive | Two consolidated runs per month |
| FX location | Beneficiary bank converts at an unseen rate | Converted in-account at a disclosed rate from 0.4% |
| Hard corridors | Wires that take days and shed fees en route | Stablecoin settlement where counterparties accept it |
| FX volume | Convert every cross-currency payment | Net flows per currency, convert the difference |
None of these five changes is dramatic on its own, and that's precisely why they get skipped — each one saves fractions of a percent, a few euros, a settlement day. Across a year of payouts, the fractions are the budget line. The businesses that pay the least for cross-border payments aren't the ones that found a secret cheap rail; they're the ones that made these five decisions once, turned them into defaults, and stopped paying for the alternative every month.
This article is for general information only and is not financial, legal, or tax advice. Product availability, fees, and features depend on verification, account type, jurisdiction, and applicable regulatory requirements, and may change over time.