Payments

SEPA vs SWIFT: which is right for your business?

Two payment rails, two different jobs. This is how to tell them apart, and how to choose the right one every time you send money.

Settled team · 7 min read

SEPA versus SWIFT payments across Europe and the world

If you move money internationally, you have seen the letters SEPA and SWIFT next to your transfers. They sound like alternatives: pick one and go. In practice they are built for different distances, settle at different speeds and cost very different amounts. Choosing well on each payment can be the difference between a partner being paid this afternoon and a wire that lands four working days later, lighter than you expected.

This is the plain-English version of the difference, written for the person who presses "send".

What SEPA is

SEPA, the Single Euro Payments Area, is a shared standard that lets euro payments move between accounts across 36 European countries as easily as a domestic transfer. It covers the EU plus a handful of neighbours, and it only ever moves euros. If you are paying a supplier in Germany, a contractor in Portugal or a landlord in Ireland, and the payment is in euros, it travels over SEPA.

There are two flavours worth knowing:

Because everyone on the network speaks the same format, SEPA payments are cheap, predictable and rarely go astray. With Settled, SEPA in and out costs 0.1% (minimum €2), and internal Settled-to-Settled transfers are free and instant.

What SWIFT is

SWIFT is not a single network in the way SEPA is. It is a global messaging system that lets banks around the world instruct each other to move money, in almost any currency, to almost any country. When you send a US dollar payment to a supplier in Singapore, your bank, the receiving bank and sometimes one or two banks in between exchange SWIFT messages to settle it.

That reach is the point. SWIFT connects more than 190 countries, which is why it is the rail for anything outside the euro zone or in a non-euro currency. The trade-off is that messages can pass through intermediary (correspondent) banks, and each one can take a fee and add a little time. At Settled, SWIFT in and out is 0.15% (minimum €15), and payments reach 190+ countries with transparent, tracked routing.

The honest comparison

Strip away the acronyms and it comes down to four questions: how far, how fast, how much and which currency.

So which should you use?

The rule of thumb is simple. If the payment is in euros and the recipient is in the SEPA area, use SEPA every time. It is faster, cheaper and the amount lands intact. Reach for SWIFT when you need to go beyond Europe or send a currency other than the euro.

A few practical cases:

What you do not want is to fall back on SWIFT out of habit for a payment that could have gone over SEPA. That is where businesses quietly overpay.

Where a multi-currency account changes the maths

The reason this choice trips people up is that most businesses bank in one currency and convert on the way out. Every cross-border payment then bundles three things together: an FX conversion, a transfer fee and a rail. It is hard to see what you are paying for.

Holding the currency you need before you send it untangles that. With a Settled account you can hold 12+ currencies with dedicated IBANs, receive euros over SEPA and dollars over SWIFT, and convert only when you choose to, at transparent FX from 1% (0.75% on Premium). The payment rail becomes a clean decision on its own, separate from the conversion, which is how it should be.

The short version

SEPA is your default for euros inside Europe: fast, cheap, exact. SWIFT is your passport for everything else: global reach in almost any currency, at a slightly higher floor. Match the rail to the job and you will rarely overpay, and with a multi-currency account underneath, the decision takes seconds.

Put it to work

Send SEPA and SWIFT from one account.

Open a Settled account to hold 12+ currencies, pay over SEPA from 0.1% and reach 190+ countries on SWIFT, with transparent FX when you need it.

Back to the blog