Outbound GBP payouts for UK platforms and finance teams.
Contact NowMost UK businesses pick a payment rail by accident. SWIFT is the default – for German suppliers, US contractors, Dutch marketplace sellers. It fits some of those jobs. For others, it adds cost and days that a better-matched rail would not.
The five types of cross border payments are not interchangeable. They differ by cost, settlement speed, coverage, and the job they were built for. Getting the match right is where most of the friction disappears.
“Most finance teams we speak with have never questioned which rail they are using. They just know SWIFT is expensive and slow – but they have not mapped the alternatives to what they actually need to send.” – Ravi, Finexer
TL;DR
UK businesses use five types of cross border payments: SWIFT (global, 2-5 days, correspondent bank fees), SEPA (EUR-only, 41 countries including the UK, cheap and fast), card networks (near-global, consumer-facing), local rails (corridor-specific like US ACH, Indian UPI, Brazilian PIX), and API-based Open Banking (UK domestic GBP via Faster Payments, with EUR settlement handled separately via payout partners). The right rail depends on currency, corridor, and settlement speed – not on whichever system the business used first.
What Are Cross Border Payments?
Cross border payments are transactions where the sender and recipient hold accounts in different countries or currencies. The payment must cross at least one national boundary, often involving currency conversion, regulatory differences, and multiple financial intermediaries.
For UK businesses, cross border payments typically fall into two categories: outbound (paying overseas suppliers, contractors, or platforms) and inbound (receiving payment from international customers). The right rail depends on the direction, the currency, and the geography – not on whichever system the business used first.
The 5 Types of Cross Border Payments
Each rail has a different job. The wrong default costs time and money.
| Type | Best for | Speed | Cost | Coverage |
|---|---|---|---|---|
| SWIFT wire transfer | High-value B2B, global corridors outside EU | 2-5 business days | High – correspondent bank fees at each hop | 200+ countries |
| SEPA / SEPA Instant | EUR payments within Europe (41 countries) | Next business day / under 10 seconds | Low | EU + EEA + select non-EU |
| Card networks | Consumer-facing, B2C international payments | Seconds to 24 hours | Medium – interchange and FX fees apply | Near-global |
| Local payment rails | Specific corridors – US, India, Brazil | Seconds to minutes | Low within the corridor | Country or region specific |
| API-based (Open Banking) | Outbound GBP domestic payouts; GBP-to-EUR via licensed payout network partners (separate arrangement) | Instant via Faster Payments (UK) | Low – no intermediary banks | UK domestic + EU via payout partners |
1. SWIFT Wire Transfers

SWIFT is the global messaging network connecting 11,500+ financial institutions across 200+ countries. It does not move money itself – it transmits standardised payment instructions between banks, which then settle the funds through correspondent banking chains.
That correspondent chain is the source of both SWIFT’s global reach and its main limitations. Each intermediary bank can deduct a fee, so the amount received at the other end may differ from what was sent. Settlement typically takes 2-5 business days, though SWIFT GPI corridors have improved speed on major routes.
For UK businesses, SWIFT is the right choice when no local alternative exists – high-value transfers to markets outside SEPA coverage, or payments to countries where direct rail access is not available. Traditional banks and SWIFT-based correspondent banking handled an estimated 92% of global B2B cross border transactions in 2023 (Wise). That dominance reflects global reach, not universal fit.
Where it falls short: predictable costs are difficult when multiple intermediary banks are involved, and transparency over where a payment is in the chain has historically been limited – though ISO 20022, which SWIFT completed its migration to in November 2025, is improving structured data and tracking across the network.
2. SEPA and SEPA Instant

SEPA – the Single Euro Payments Area – covers 41 countries including all EU member states, EEA countries like Norway and Iceland, and non-EU members including Switzerland and the UK. It handles EUR-denominated transfers only.
SEPA Credit Transfer settles next business day. SEPA Instant – mandated for all EU and EEA payment service providers under the Instant Payments Regulation from 2026 – targets settlement in under 10 seconds, though rollout is ongoing across all providers. For platforms evaluating cross border instant payments more broadly, SEPA Instant is the most relevant real-time option for EUR flows within Europe.
For UK businesses paying EUR-denominated invoices to European suppliers, SEPA is almost always cheaper and faster than routing the same payment through SWIFT. The constraint is EUR only: the payment must be denominated in euros, and the recipient account must be in a SEPA member country.
Post-Brexit, the UK remains within SEPA’s geographical scope as a non-EEA participant – confirmed by the European Payments Council and unchanged as of 2026. UK banks and payment providers can still send and receive SEPA Credit Transfers and SEPA Direct Debits in euros.
The practical caveat: UK businesses need a euro-denominated account with a valid IBAN to use SEPA directly. Some EU banks require additional data fields (such as the debtor’s postal address) for payments from UK IBANs. If your bank does not offer a EUR account, a payment provider with direct SEPA access is the more practical route.
3. Card Networks

Visa, Mastercard, and Amex operate their own global payment rails, entirely separate from SWIFT or bank transfer infrastructure. They are designed primarily for consumer-facing transactions – accepting payments from international customers at checkout, or issuing corporate cards for staff spend.
For outbound B2B payouts to suppliers, contractors, or marketplace sellers who hold bank accounts, card rails tend to be the more expensive option. Interchange fees, FX conversion spreads, and potential chargeback exposure make high-volume outbound flows costly compared to account-to-account alternatives.
Card push products like Visa Direct and Mastercard Send have expanded into disbursement use cases – paying gig workers, insurance claims, or small business payouts. These can work well where payees do not have easily accessible bank account details, or where consumer familiarity with card receipt matters. For most UK B2B platform payouts, they are not the default fit.
4. Local Payment Rails

Every major economy has its own domestic clearing infrastructure. These are purpose-built to move money within a specific country or currency corridor faster and at lower cost than routing through SWIFT.
The most relevant examples for UK platforms paying internationally:
- FedNow / ACH (United States) – for USD payments to US recipients; ACH settles in one to two business days, FedNow in seconds
- UPI (India) – instant account-to-account transfers to Indian bank accounts, operated by NPCI
- PIX (Brazil) – real-time payments launched by Brazil’s central bank in 2020, now processing more transactions than card networks in the country
- BECS (Australia) – batch electronic clearing for AUD payments
For UK platforms paying contractors, freelancers, or marketplace sellers in specific markets at volume, local rails reduce cost and settlement time significantly versus SWIFT. The constraint is single-corridor coverage. A platform paying in 15 countries needs either direct connections to 15 local rails or a payout provider that aggregates access to them.
For UK platforms managing high-volume outbound disbursements across corridors, bulk payment services UK infrastructure reduces the operational overhead of managing multiple rails.
5. API-Based Payments and Open Banking

API-based payments sit above a payment rail and handle initiation, routing, confirmation, and reconciliation through a single integration. The underlying rail varies by corridor – Faster Payments for UK domestic, SEPA for EUR, local networks for specific markets.
For UK domestic outbound payouts specifically, Open Banking Payment Initiation Services provide a direct account-to-account route via Faster Payments. Faster Payments is a UK domestic rail – it moves GBP between UK bank accounts only. The payment instruction goes directly to the sending bank, with no card network or correspondent banking chain on the domestic GBP leg.
For GBP-to-EUR payouts, Open Banking PIS covers only the UK domestic GBP leg via Faster Payments. The EUR settlement leg requires a separate arrangement with licensed payout network partners or FX providers – this is not part of the Open Banking PIS scope itself. Platforms using this model manage two separate provider relationships: the UK PIS layer and the overseas settlement layer.
ISO 20022 – whose migration SWIFT completed in November 2025 – is also being adopted across Open Banking and local rails, enabling richer, structured reference data that reduces reconciliation exceptions at scale.
Where Open Banking Fits in the International Payment Systems Landscape
Open Banking PIS is not a replacement for SWIFT or SEPA. It solves one specific problem: UK platforms sending money outward at volume, where SWIFT adds cost and delay on the domestic leg.
Two scenarios where it makes a difference in practice:
A payroll SaaS processing monthly salary run for 300 UK employer clients does not need SWIFT. Every payment is GBP, domestic, account-to-account. Open Banking PIS via Faster Payments handles the full volume – instant settlement, per-employee confirmation, no card network fees.
A B2B marketplace settling UK suppliers weekly uses Faster Payments via Open Banking PIS – instant settlement, per-payment references, no SWIFT intermediaries on the domestic leg. For German supplier payments, a separate GBP-to-EUR arrangement with a licensed payout provider handles the EUR leg alongside the PIS integration.
Finexer provides FCA-authorised Open Banking PIS for UK domestic payment workflows – batch initiation, per-payment webhook confirmation, and payout reconciliation references built in.
Open Banking Limited recorded 37.46 million payment transactions in March 2026, concentrated in inbound consumer flows. For platforms replacing SWIFT on UK-domestic GBP flows, the international payments API layer is where the operational difference is most visible.
- FCA-authorised (FRN 925695)
- 3 to 5 weeks of hands-on onboarding support
- Usage-based pricing, commercial terms agreed based on use case
Which type of cross border payment is cheapest for UK businesses?
SEPA for EUR payments within Europe. Local rails for specific corridors like US ACH or Indian UPI. Open Banking PIS for outbound GBP payments via Faster Payments. SWIFT is typically the most expensive option – necessary where no better alternative exists.
What is the difference between SWIFT and SEPA?
SWIFT covers 200+ countries in any currency but typically takes 2-5 business days, with fees deducted at each correspondent bank hop. SEPA is EUR-only across 41 European countries – cheaper, next business day or under 10 seconds with SEPA Instant. For EUR payments within Europe, SEPA is almost always the better choice.
What are international payment systems?
The networks that move money across borders. Main categories: SWIFT (global bank messaging), SEPA (EUR Europe), card networks (consumer flows), local rails like ACH, UPI, and PIX (specific corridors), and API-based layers that handle routing and confirmation above those rails. Each serves a different geography, currency, and speed profile.
How does Open Banking fit into cross border payments?
Open Banking PIS initiates UK domestic GBP payments via Faster Payments – instant, account-to-account. It removes the correspondent bank layer on the domestic GBP leg. For GBP-to-EUR flows, a separate payout network partner handles the EUR settlement leg – Open Banking PIS itself only covers the UK domestic portion.
Stop defaulting to SWIFT for UK outbound payouts
by
Tags:

