Guest Articles / Learning brief
Domestic Payment Schemes in the UK – Part 1
Your notes
In simple terms / 01
What this means in plain language
Uses simple transfer examples to trace the evolution from same-bank ledger moves to the UK's principal interbank payment schemes.
When two customers use the same bank, a transfer can often be completed through entries on that bank's own ledger. When they use different banks, the institutions need agreed rules, messaging, clearing, and a way to settle what they owe each other. Domestic payment schemes provide that shared arrangement. The UK developed multiple schemes because payroll, bills, retail transfers, and urgent high-value payments have different needs. Understanding this evolution helps analysts separate the customer's instruction from the interbank processes that make the transfer possible.
Complete lesson / 02
Understand the full idea, step by step
If a UK salary has ever landed in an account overnight while a transfer to a friend arrived in seconds, two different payment schemes were at work — and neither of them was the button on the banking screen. The United Kingdom runs several account-to-account rails side by side, each built for a different job. This lesson maps them.
Why schemes exist at all
If both parties banked with Bank Alfa, each payment would be a pair of entries in one ledger and no scheme would be needed. The moment the payee banks elsewhere, Bank Alfa needs three things it cannot supply alone: a shared rulebook every bank interprets the same way, an agreed way to exchange instructions, and a way to settle what the banks now owe each other. A payment scheme packages exactly that — rules, membership, messaging, and a settlement arrangement. The UK grew several of them because payroll files, urgent property money, and everyday transfers make very different demands.
Who runs what
- Bacs
- Retail batch scheme — operated by Pay.UK
- Faster Payments
- Near-real-time retail scheme — operated by Pay.UK
- CHAPS
- High-value scheme — operated by the Bank of England
- Settlement
- All three settle across accounts at the Bank of England
- Currency
- GBP only — these are domestic sterling rails
Bacs — originally Bankers' Automated Clearing Services
The UK's batch workhorse. Banks and their corporate customers submit files of payments in advance, and the scheme processes them on a cycle measured in days — submit now, beneficiary credited on a later, scheduled day. Bacs carries two products: Direct Credit, where the payer pushes money out (payroll, pensions, supplier runs), and Direct Debit, where a biller pulls money in under a mandate the customer signed. Slow by design, and priced and controlled for volume.
Faster Payments — the UK's Faster Payments System (FPS)
The rapid retail rail: single credit transfers that typically reach the beneficiary's account within seconds, around the clock, every day of the year. When a UK banking app moves money to a friend on a Sunday night, this is almost always the scheme underneath. Forward-dated standing orders commonly ride it too. Amounts are capped by the scheme and by each bank's own limits.
CHAPS — Clearing House Automated Payment System
The high-value scheme, operated by the Bank of England itself. CHAPS handles payments that are too large or too consequential for the retail rails — property completions, corporate treasury moves, banks' own obligations — on business days, with each payment settling individually across accounts at the central bank. Its promise is not speed for its own sake but certainty: once a CHAPS payment settles, it is final.
| Bacs | Faster Payments | CHAPS | |
|---|---|---|---|
| Built for | Planned, high-volume runs | Everyday single transfers | Urgent, high-value payments |
| Speed to payee | A cycle of days | Typically seconds | Same business day |
| Availability | Business-day submission windows | 24/7, every day | Business days |
| Direction | Push (Direct Credit) and pull (Direct Debit) | Push only | Push only |
| Operator | Pay.UK | Pay.UK | Bank of England |
COMMON CONFUSION
“The name on the banking screen tells you which scheme is carrying the payment.”
Product labels are the bank's own. A screen that says "standing order" may execute over Faster Payments; a button that says "same-day transfer" may be CHAPS or FPS depending on amount and the bank's routing rules. The scheme is chosen by the bank underneath, and support teams investigating a delay need the actual rail, not the label the customer saw.
You may be wondering: if Faster Payments is fastest, why not send everything over it?
Three reasons. First, the scheme and each participating bank cap the amount a single FPS payment may carry — the current figures live in the scheme documentation, not in this lesson. Second, very large payments demand the settlement certainty CHAPS is engineered for, and banks manage the liquidity for them differently. Third, Faster Payments cannot pull: Direct Debit's mandate model, which powers most UK bill collection, has no equivalent there. Each rail's design fits its job.
STRICTLY SPEAKING
Strictly speaking, this landscape has moved and will move again. Bacs and Faster Payments began life under separate scheme companies and were later consolidated under Pay.UK; CHAPS was transferred to the Bank of England's direct operation. Many banks reach these schemes indirectly, through a direct participant, which changes timings and controls. Amount limits, submission windows, and participation rules belong to the current scheme documentation — always check before quoting one.
FOR NOW, REMEMBER
- Interbank payments need shared rules, messaging, and settlement — that package is a scheme, and the UK runs several because needs differ.
- Bacs is the batch rail (Direct Credit pushes, Direct Debit pulls) on a cycle of days; Faster Payments moves single transfers in seconds, 24/7; CHAPS carries urgent high value with settlement finality.
- Pay.UK operates the two retail schemes; the Bank of England operates CHAPS — and all three settle across accounts at the Bank of England.
- Bank product names sit on top of scheme names: the route underneath is the bank's choice and the fact that matters in an investigation.
TRY IT YOURSELF
Asha Traders must get the GBP 850,000.00 lease payment to the solicitor at Meridian Bank before 13:00 today, and the outcome must be final — no possibility of the money coming back short. Which routing judgement is right?
You can now name the three rails and their jobs. The next brief asks the settlement clerk's question: for each scheme, when exactly are the banks themselves square — and why does the answer differ so much?
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
Same-bank transfers can stay within one ledger.
- 02
Interbank transfers require shared rules and settlement arrangements.
- 03
Different customer needs led to multiple domestic schemes.
Practical use cases / 04
Where you would use this
A trainee compares an internal book transfer with an interbank payment.
A business analyst identifies which systems participate after a beneficiary bank changes.
A product designer explains why two transfer options have different timing and cost.
Worked example / 05
Put the idea into a real situation
Illustrative example: Ava and Ben both bank with Bank A, so Bank A can debit Ava and credit Ben on its own books. If Ben moves to Bank B, Bank A must send an instruction through an appropriate domestic arrangement and settle with Bank B. Bank B then posts the beneficiary credit. The customer action looks similar, but the second route adds interbank rules, messages, controls, and reconciliation.
Operational sequence / 06
Follow the message and decision path
This compact sequence is a learning model. Exact routing and rulebook behavior can vary by scheme, participant, and implementation.
Read the steps as text
- 01MessageRiya asks Bank Alfa to pay ArjunRiya (payer) → Bank Alfa (sending bank)
On a Sunday evening Riya opens her banking app and instructs Bank Alfa to send GBP 500.00 to Arjun at Nordbank. Faster Payments runs 24/7, so time of day does not matter. Nothing has moved yet — this is only a request.
- 02ProcessingBank Alfa checks the payment in real timeBank Alfa (sending bank)
Bank Alfa validates the account details, confirms Riya has the funds, screens for sanctions, and checks the amount against the FPS single-payment limit and its own limits — all in seconds, because the customer is waiting.
Screening checkpoint: Real-time transaction screening — Near-real-time rails force screening to be fast and automated — there is no overnight batch window to absorb the delay.
- 03PostingBank Alfa debits RiyaBank Alfa (sending bank)
Bank Alfa reduces Riya's balance by GBP 500.00 on its own books. The money has left Riya, but Arjun does not have it yet and the banks have not settled — those are separate steps.
- DR Riya's current account at Bank Alfa — GBP 500.00
- 04MessageThe payment goes through Faster Payments in real timeBank Alfa (sending bank) → Faster Payments (Pay.UK)
Bank Alfa submits the payment to the central Faster Payments infrastructure, which routes it to Nordbank immediately. This real-time clearing leg carries the instruction — it does not move central bank money.
- 05MessageNordbank receives the payment within secondsFaster Payments (Pay.UK) → Nordbank (receiving bank)
Faster Payments forwards the payment to Nordbank in real time and expects a fast answer. The message tells Nordbank exactly whose account to credit and with how much.
- 06PostingNordbank validates and credits Arjun within secondsNordbank (receiving bank)
Nordbank checks the beneficiary account, screens the payment, and credits Arjun on its own books — all within seconds of Riya pressing send. Nordbank now owes this money and will recover it from Bank Alfa at settlement.
- CR Arjun's current account at Nordbank — GBP 500.00
- 07ProcessingArjun can spend the money immediatelyNordbank (receiving bank) → Arjun (payee)
Arjun sees GBP 500.00 in his account and can spend it straight away, even though the banks have not yet settled between themselves. This gap — payee paid now, banks settled later — is the exposure Nordbank carries.
- 08SettlementLater, the banks settle their net positions at the Bank of EnglandFaster Payments (Pay.UK) → Bank of England (settlement)
On a defined settlement cycle — after Arjun already has the money — Faster Payments calculates each bank's net position and the banks settle those net amounts in central bank money across their Bank of England settlement accounts. This is deferred net settlement, not payment-by-payment RTGS.
FPS clears in real time but settles on a deferred, netted basis. Only one net figure per bank per cycle moves at the Bank of England — not GBP 500.00 on its own.
- DR Bank Alfa net position at the Bank of England — GBP 500.00 (as part of the net cycle)
- CR Nordbank net position at the Bank of England — GBP 500.00 (as part of the net cycle)
Read the steps as text
- 01MessageBank Alfa submits the CHAPS paymentBank Alfa (sending bank) → CHAPS · pacs.008
Bank Alfa must pay a high-value sterling obligation — the completion monies on a property purchase — to Nordbank, so it sends an interbank payment (a pacs.008) into CHAPS. Since the ISO 20022 migration on 19 June 2023 the message carries richer structured data, including the Purpose Code and Legal Entity Identifier (LEI). Nothing has moved yet — it is an instruction.
- 02ProcessingCHAPS checks Bank Alfa's available liquidityCHAPS → Bank of England (RTGS)
Before it settles anything, CHAPS checks whether Bank Alfa's settlement account in the Bank of England's RTGS infrastructure holds enough available liquidity to cover the full GBP 850,000.00 amount.
- 03SettlementThe Bank of England settles the payment in central-bank moneyBank Alfa (sending bank) → Nordbank (receiving bank)
With liquidity confirmed, the Bank of England debits Bank Alfa's settlement account and credits Nordbank's, one payment at a time. CHAPS settles each payment individually in central-bank money, without any prior netting, and the transfer is final the instant it settles.
- DR Bank Alfa's settlement account at the Bank of England — GBP 850,000.00
- CR Nordbank's settlement account at the Bank of England — GBP 850,000.00
- 04MessageNordbank is confirmed of the settled paymentCHAPS → Nordbank (receiving bank)
CHAPS tells the receiving bank that the funds are on its settlement account at the Bank of England and are final, with the payment details — including the Purpose Code and LEI — it needs to apply.
- 05PostingNordbank books the incoming fundsNordbank (receiving bank)
Because the interbank leg already settled with immediate finality, Nordbank records the credit on its own ledger without waiting for anything else. The property completion is paid, end to end.
- CR Incoming settlement account at Nordbank — GBP 850,000.00
Evidence & review / 07
Evidence & review
UK domestic sterling account-to-account schemes (Bacs, Faster Payments, CHAPS) as currently operated by Pay.UK and the Bank of England
What this brief simplifies: Treats each scheme through one representative use case; omits cheque clearing, LINK, card rails, indirect-participation mechanics, and exact limits, windows, and timetables, which belong to current scheme documentation.
Sources for this brief3
- Scheme-specific rule
CHAPS ↗ — Bank of England · CHAPS purpose, operator, and settlement at the Bank of England
The Bank of England has operated CHAPS directly since November 2017; participant-facing reference documents are published separately.
- Market practice
Fast payments - enhancing the speed and availability of retail payments ↗ — CPMI, Bank for International Settlements · Characteristics of fast retail payment systems
Predates several major instant payment launches; this site uses it for concepts, not current statistics.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.