Beyond Bacs & SWIFT: How Stablecoins Are Upgrading UK Payments

For anyone moving money in the UK, understanding the types of UK bank transfer systems (Bacs, FPS, CHAPS, SWIFT) is table stakes. 

The rails you choose determine settlement speed, operating cutoffs, reconciliation workload, and, especially for cross-border flows, fees and predictability. This matters even more when GBP payments touch global counterparties and multiple intermediaries.

This guide explains the major UK transfer systems, where they’re used, and what changes post-Brexit have meant for cross-border GBP payments. It also frames where stablecoins can complement existing rails for faster, more transparent settlement without replacing the controls institutions need.

Use cases for GBP transfers (B2B, ecommerce, international trade)

GBP transfers are a backbone for both consumer and commercial activity:

• B2B operations: supplier payments, invoice settlement, payroll, treasury movements
• Ecommerce: bank transfer checkout options for customers who prefer account-to-account payments
• International trade and services: paying UK counterparties, settling invoices, and managing GBP exposure
• Financial services: high-value transfers, clearing and settlement, client money movements

UK adoption is high. UK Finance reported 3.6 billion Faster Payments transactions in 2021 and noted 86% of UK adults use remote banking. For high-value flows, UK Finance reported 48 million CHAPS transactions in 2021, with total value exceeding £86.3 trillion. Bacs also remains high volume, including 1.9 billion direct credit payments in 2021.

Types of UK bank transfer systems (Bacs, FPS, CHAPS)

Different rails exist because payment needs differ: bulk vs. real-time, low-value vs. high-value, domestic vs. cross-border. Here’s the practical breakdown.

Bacs (Bankers Automated Clearing Services)

What it is: A standard UK electronic clearing system for account-to-account payments.

Common uses: salaries, pensions, benefits, bill payments, and other regular bulk transfers.

Key facts:

• Processing time: typically up to three business days
• Cost: generally low or no-fee for consumers (business pricing varies by provider/bank)
• Limits: no official upper limit, but bank policies can vary
• Oversight: UK payments operate under UK regulatory frameworks (see regulation section below)

Faster Payments Service (FPS)

What it is: The UK’s real-time domestic payment rail.

Common uses: immediate transfers via online/mobile banking, time-sensitive bill payments, and many B2B/B2C transfers.

Key facts:

• Processing time: often within minutes, 24/7
• Limits: up to £1 million per transaction at the scheme level (bank limits may be lower)
• Availability: widely supported across UK banks
• Cost: often free for personal banking customers

CHAPS (Clearing House Automated Payment System)

What it is: A same-day, high-value payment system.

Common uses: property transactions, large corporate payments, high-stakes treasury transfers.

Key facts:

• Processing time: same day if submitted before the bank’s cutoff time
• Limits: no minimum or maximum, but commonly used for payments above £10,000
• Cost: typically carries a bank fee
• Finality: designed for high assurance and operational certainty

Direct debit (for collections)

What it is: A customer authorization that allows a business to pull funds from the customer’s bank account.

Common uses: recurring bills (utilities), subscriptions, memberships.

Key facts:

• Consumer protection: covered by the Direct Debit Guarantee (refunds for errors)
• Setup: requires a direct debit mandate
• Operational note: best suited for predictable collections rather than instant payout use cases

Internal bank transfers

What it is: Transfers between accounts at the same bank.

Common uses: treasury moves, personal account management.

Key facts:

• Processing time: often instant
• Constraints: only works within the same institution

International and cross-border GBP payments (SWIFT and correspondent banking)

What it is: GBP transfers from a UK bank to an overseas account (or vice versa), typically using SWIFT messaging and correspondent banks.

Common uses: international purchases, overseas suppliers, global payroll, remittances.

Key facts:

• Processing time: variable; can take several days
• Cost drivers: correspondent bank fees, FX conversion spreads/fees (if conversion occurs), and operational overhead
• Predictability: total fees and arrival times can be harder to forecast than domestic rails

International and cross-border GBP payments: what changes after Brexit

Cross-border GBP payments involving Europe became more operationally complex after Brexit, primarily due to changes in market access and routing.

Impact of Brexit on cross-border payments

Key changes commonly cited by industry participants:

• Loss of passporting: UK banks lost EU single-market passporting rights, limiting direct access to some EU payment infrastructure.
• More reliance on correspondent banks: additional intermediaries can introduce extra fees and longer settlement times.
• Reduced ease vs. SEPA-like experience: UK users who previously benefited from fast, low-cost intra-EU transfer conditions can face more friction depending on bank/provider setup.

Regulatory coordination continues via:

• A UK–EU financial services agreement (FSA) intended to maintain market access in certain areas (not a full replica of pre-Brexit conditions).
• An FCA–ECB memorandum of understanding (MOU) to support cooperation and information sharing.

Operational implications for enterprises:

• Higher costs: more intermediaries and compliance steps can increase per-payment cost.
• Lower transparency: fee deductions and routing can be less predictable.
• Slower processing: especially when payments traverse multiple correspondent banks.

Security and regulation of traditional banking rails

UK payment rails are built on mature operational and regulatory controls, but the control model differs by rail and by participant (bank, PSP, gateway).

Oversight and compliance baseline

In the UK, payment services operate under regulatory supervision, including the Financial Conduct Authority (FCA) and the Payment Systems Regulator (PSR) (with roles that vary by activity and entity type). Across domestic and cross-border transfers, institutions also align with global expectations around:

• AML (anti-money laundering)
• KYC (know your customer)
• sanctions screening and transaction monitoring (where applicable)

How security differs by rail (practical view)

• FPS: strong customer authentication (often MFA), encryption, and real-time fraud monitoring are common controls in bank channels.
• Bacs: batch processing, validation, and structured reconciliation reduce some real-time exposure but introduce timing and exception-handling workflows.
• CHAPS: designed for high-value certainty, with strong access controls and auditability.
• SWIFT/correspondent banking: secure messaging standards plus layered compliance across multiple banks, which can increase both resilience and complexity.

For enterprise teams, the key is mapping these controls to your risk model: fraud exposure, dispute handling, operational resilience, and audit requirements.

Where stablecoins can complement GBP rails (without hand-waving)

Traditional rails are effective for many domestic use cases. The pain typically shows up in cross-border GBP payments: multiple intermediaries, non-uniform cutoffs, opaque fees, and settlement delays.

Stablecoins can help in specific scenarios because they are:

• programmable: payment logic, reconciliation hooks, and conditional release can be automated
• 24/7 native: settlement doesn’t depend on local banking hours
• transparent at the ledger layer: parties can verify transfer status end-to-end onchain

Important constraints (especially for institutions):

• Stablecoin flows still require on/off-ramps, compliance controls, and treasury policies.
• Legal, tax, and regulatory obligations remain—stablecoins change the transport layer, not the obligation to comply.
• Risk decisions include issuer risk (for fiat-backed stablecoins), wallet/key management, and operational controls.

Where this becomes practical for fintechs and enterprises:

• Cross-border B2B settlement: reducing time-to-settle and improving payment status visibility
• Treasury operations: faster rebalancing across entities or regions
• Platform payouts: near real-time disbursements where recipient banking rails are slow or costly

Polygon is infrastructure used by payment builders to move value onchain with low fees and high throughput, useful when stablecoins are part of the payment flow and you need predictable execution at scale.

Accepting and operating GBP transfers: implementation checklist (enterprise view)

If you’re supporting GBP transfers today, the operational requirements are usually more decisive than the “payment method” label.

For UK-based businesses

• Ensure your business bank account supports relevant rails (Bacs, FPS, CHAPS).
• Operationalize UK identifiers: sort code + account number.
• Maintain KYC documentation and internal controls aligned to your PSP/bank requirements.
• If collecting via direct debit, implement mandate management and exception handling (refunds, cancellations).

For international businesses moving GBP

• Set up a GBP-denominated account (domestic UK account or a provider with GBP capabilities).
• Plan for SWIFT/correspondent banking realities: fees, cutoffs, investigations, and repair workflows.
• Establish policies for FX conversion, including rate sourcing and fee allocation.

Common controls for all businesses

• Staff training and procedures for AML/KYC and transaction monitoring.
• Data security controls aligned with GDPR where relevant.
• Auditability: logging, reconciliation, and dispute processes.

If stablecoins are introduced into the stack, add:

• wallet and key management controls (custodial or noncustodial model)
• onchain monitoring and address risk screening
• clear treasury policies for stablecoin inventory and redemption

Conclusion

UK rails  are reliable foundations for domestic GBP movement, while SWIFT and correspondent banking still dominate many cross-border GBP flows. Post-Brexit, cross-border routing can be more expensive and less predictable, which is why many enterprises are reassessing how they settle internationally.

A practical next step is to map your GBP payment flows by corridor and use case (B2B, ecommerce, international trade), then identify where settlement speed, transparency, and operating hours are limiting outcomes. That’s where stablecoins on blockchain can complement bank rails—especially for cross-border settlement—while keeping compliance and control requirements intact. Polygon is one of the infrastructures teams use to build and operate those stablecoin payment flows at scale.

‍