UK edition: Faster Payments vs BACS vs CHAPS for platform payouts
The three UK payment rails compared for marketplace payouts: Faster Payments for speed, BACS for cheap batch runs, CHAPS for high-value — and when to use which.
By Valeria VahorovskaUpdated 7 September 2026
The UK gives a platform three account-to-account payment rails, and the right answer is almost never “pick one”: Faster Payments is the experience lane (seconds, 24/7), BACS is the economy lane (three-day batch, cheapest at volume, plus Direct Debit for pull), and CHAPS is the exception lane (same-day, no ceiling, priced like it). A payout operation that routes per payment — amount, urgency, recipient bank — gets the seller experience of “instant” at close to BACS economics.
This is the UK companion to our US rails explainer: different three-letter names, same buyer’s question underneath — what does “instant” actually mean, and what does it cost when it isn’t? It is also the rails chapter of Fynex for UK businesses, where the outcome — the business runs and pays everyone it owes — matters more than the scheme names.
Faster Payments vs BACS vs CHAPS: the comparison table
The three UK rails differ on four axes: speed, settlement cycle, limits and cost. Faster Payments is real-time, every day of the year. BACS is a three-working-day batch scheme. CHAPS is same-day, banking hours only, no ceiling. Fynex is not a fourth rail; it is the routing and reconciliation layer that picks between them per payout. Figures below come from Pay.UK, Bacs, the Bank of England and the published help pages of Barclays and Santander.
| Rail | How fast | Settlement cycle | Typical cut-off | Typical limits | Typical cost | Best used for |
|---|---|---|---|---|---|---|
| Faster Payments (FPS) | Seconds to minutes; the scheme allows up to two hours | Real-time, 24/7, 365 days a year | None | Scheme ceiling £1M; each bank sets its own lower cap | Varies by bank; often inside the account tariff | Seller and gig payouts, refunds, anything wanted today |
| Fynex (routing layer, not a rail) | As fast as the rail each payout qualifies for | Per payout: FPS by default, BACS for scheduled runs, CHAPS for exceptions | Inherits the chosen rail’s window; falls back when a cut-off is missed | Inherits the rail’s and the bank’s limits | Fynex’s own per-payout fee on top of the rail; no rail markup | Platforms paying many parties from one incoming payment, reconciled |
| BACS (Direct Credit / Direct Debit) | Three working days — sent Monday, paid Wednesday | Input day → processing day → entry day; English bank working days | Files accepted 07:00–22:30 on input day; bureaux set earlier deadlines | Varies by bank and sponsoring PSP | Varies by bank or bureau; per item, so the volume rail | Payroll, supplier runs, pensions, scheduled payouts; Direct Debit for collections |
| CHAPS | Same working day | Gross settlement at the Bank of England, 06:00–18:00 Mon–Fri; customer payments by 17:40 | Bank-set, typically mid-to-late afternoon; earlier by phone or in branch | No minimum, no maximum | A fixed bank fee per payment, tens of pounds | Property completions, treasury moves, the payout too big for FPS that cannot wait |
For scale: Pay.UK reports 6.86 billion Bacs payments worth £6.05 trillion in 2025 against 5.55 billion Faster Payments worth £4.84 trillion, and eight in ten UK employees are paid by Bacs Direct Credit.
BACS vs CHAPS: what is the difference?
BACS and CHAPS sit at opposite ends of the UK rail spectrum. BACS is a batch scheme: a file goes in on day one and the money lands on day three, priced per item for volume. CHAPS is the Bank of England’s same-day, real-time gross settlement system, with no upper limit and a fixed fee per payment.
Each was built for a different job. BACS (Bacs Direct Credit, plus Direct Debit for collections) lets a company pay a thousand people on Friday from one file submitted on Tuesday. CHAPS lets one large payment settle with finality before 18:00 today — a property completion, a treasury transfer, a supplier who will not ship without cleared funds.
The cost gap follows. A CHAPS fee — £15 for a Barclays business customer online, £25 at Santander — is immaterial on a £400,000 completion and absurd on a £120 invoice. Rule of thumb: large and urgent, CHAPS; scheduled and repeating, BACS. The Friday-night seller payout is neither; that is Faster Payments territory.
BACS vs Faster Payments: is BACS the same as Faster Payments?
No. BACS and Faster Payments are separate schemes, both operated by Pay.UK, and they behave differently in every way that matters to a payout. Faster Payments is real-time, 24/7, 365 days a year, with a £1M scheme ceiling. BACS is a three-working-day batch cycle with Direct Debit attached. A bank-app transfer is FPS; payroll is BACS.
The recipient sees both as a plain credit to a sort code and account number; the sender sees the difference. A Faster Payment arrives, in Barclays’ words, “almost immediately” — evenings and weekends included, though it can take up to two hours. A BACS Direct Credit is submitted as a file, sits through processing day, and credits on entry day.
For UK platform payouts the two are complementary. The weekly seller settlement goes out on BACS three days ahead at volume pricing; the seller who asks for their balance on Saturday gets it on FPS. BACS and Faster Payments each have a glossary entry with the scheme mechanics.
Faster Payments vs CHAPS: when does same-day beat real-time?
Faster Payments beats CHAPS for almost every payout under the bank’s limit: it is faster, it runs at weekends, and it is cheaper. CHAPS wins in two cases — the payment exceeds the Faster Payments ceiling the sending bank applies, or the counterparty requires CHAPS settlement finality, as in conveyancing.
Limits are the dividing line. Pay.UK’s scheme maximum is £1M, but its per-bank limits page shows the spread: Lloyds caps business online payments at £99,999, while Barclays, HSBC and NatWest business accounts go to £1M. CHAPS has no maximum but has hours — 06:00–18:00 on working days, customer payments by 17:40, Barclays’ own cut-off 17:00. Miss it and the payment goes the next working day. Faster Payments has no window, which is why it is the default and CHAPS the exception.
Are BACS payments instant?
No. A BACS payment is never instant. The Bacs scheme runs on a three-working-day cycle: input day, processing day and entry day. A file submitted on Monday is processed on Tuesday and credited on Wednesday. Weekends and English bank holidays do not count, so a Friday run lands the following Tuesday.
Bacs publishes the mechanics. On input day the service user or bureau transmits the file between 07:00 and 22:30. On processing day Bacs delivers it to the recipient banks. On entry day the recipients are credited and the sender’s account is debited simultaneously, so the money leaves and arrives together.
That predictability is the point: a finance team knows exactly when a BACS run settles. What BACS cannot do is react — the seller who wants funds tonight, the refund promised within the hour. Those are Faster Payments jobs, and a payout stack with only BACS is a fallback plan waiting to be written.
What is a BACS payment run, and what is a BACS bureau?
A BACS payment run is one batch of Bacs Direct Credit payments submitted to the scheme as a single file under a Service User Number (SUN) — a payroll, a supplier run, a scheduled payout. A BACS bureau is a commercial organisation with Bacs-approved status that submits those files on behalf of other businesses.
The Bacs glossary is precise. A Service User is a company, group or charity sponsored to use a Bacs service; the SUN is its unique six-digit number. A Bacs Approved Bureau (BAB) is a commercial bureau awarded approved status and inspected against the scheme’s standards. A sponsoring PSP — usually your bank — authorises organisations and bureaux to submit.
A direct submitter holds its own SUN and sends files through Bacstel-IP software or the Bacs payment services website. An indirect submitter goes through a provider or bureau, as over half of organisations using Bacs do. Cut-offs, multiple SUNs and returns are covered in How to scale BACS payments.
BACS payment cost comparison: what each rail actually costs
The cost order is clear even where the exact BACS per-item price is not: CHAPS is a fixed fee of tens of pounds per payment, Faster Payments is low or bundled into the account tariff, and BACS is priced per item for runs of thousands. The honest BACS answer is “varies by bank or bureau”.
CHAPS is the only rail whose fees banks publish plainly. Barclays charges business customers £15 online and £25 by phone or in branch, plus £20 to cancel or amend; Santander charges £25. BACS and Faster Payments pricing sits inside business-account tariffs and bureau contracts, so any single figure would be wrong for most readers. The shape holds everywhere: BACS per-item cost falls with volume, which is why payroll and Direct Debit live there; Faster Payments costs more per item than BACS at scale but nothing like CHAPS.
Routing them like a platform, not a policy
The naive setup picks one rail for everything and inherits its weaknesses everywhere: all-FPS pays a premium and hits bank limits on big payouts; all-BACS makes sellers wait three days in a market where waiting is churn. The routing that works is per payment:
- Default: FPS — everything inside limits where the recipient’s bank receives in real time. This is what makes your “instant payout” claim true on Friday night, when gig earnings peak and BACS is asleep.
- Scheduled volume: BACS Direct Credit — the weekly seller run, the monthly partner run, anything with a known date three-plus days out. The per-item saving compounds at thousands of payouts.
- The outliers: CHAPS — the five-figure payout above FPS ceilings that can’t wait. Rare, expensive, and exactly what it’s for.
- The fallback, disclosed. When FPS can’t reach a recipient in real time, what happens instead — and who tells them — is the difference between a support ticket and a lost seller. UK-specific wrinkle: under the APP-fraud reimbursement regime, banks now hold and question more payments; a payout stuck on hold with no explanation to the recipient reads as your platform failing.
And in contracts, name the rails, not the adjective — “instant” is marketing until it’s defined: “payouts via Faster Payments where supported, falling back to BACS Direct Credit; CHAPS available on request for payments above scheme limits.” The same logic holds off the marketplace: a physical business paying subcontractors and suppliers from one incoming payment puts B2B supplier payments on BACS where the date is known and Faster Payments where it is not.
Where Fynex fits
Fynex routes UK payouts across all three rails per payment: FPS by default, BACS for the scheduled runs where the economics win, CHAPS for the exceptions — each payout verified before it moves, each recording the rail it took, recipients told what to expect when a payment falls back. Because Fynex is an FCA-authorised EMI and owns no rails, the routing optimises your cost and your sellers’ Friday night rather than any network’s volume — and every payout reconciles itself into your books behind the run.
Related: ISO 20022 structured addresses covers the SWIFT data deadline — delayed from November 2026 — that lands on the payout file regardless of which of the three you send on, and SEPA vs SWIFT picks up where the domestic rails stop.
Three rails, one rule: match the rail to the payment, not the platform to the rail. Sellers get “instant” where it’s real, your finance team gets BACS economics where speed is wasted, and CHAPS waits quietly for the day you actually need it.