Key points of this lesson, in order.
The UK payments landscape at a glance
What you will learn
Your objective. By the end of this lesson, you will be able to explain UK payments landscape at a glance. The United Kingdom runs its domestic sterling payments on three main systems that have grown up over different decades and now sit side by side, each serving a distinct purpose.
Why it matters. Together they move almost every pound that changes hands inside the UK, and a business analyst who works on UK payments must know all three, because a customer requirement that sounds simple, such as pay this supplier today, can mean three different things depending on the value, the urgency and the cost the customer will accept.
Chapter objective: Learner compares Faster Payments, CHAPS, and BACS in the United Kingdom, explaining speed, limits, finality, and use cases, and routes a sterling payment to the correct system. Learner practises this skill on realistic banking cases, explaining the reasoning clearly and using correct terminology throughout the work.
Key learning points
- United Kingdom runs its domestic
- Together they move almost every pound
- Pay.UK operates Faster Payments and BACS
- BACS: slow and cheap
- Direct debit
- Customer experience features
Key terms
Settlement: The final movement of funds between banks to discharge obligations created by cleared payments. Settlement is usually made in central bank money or through correspondent accounts.
Finality: The point at which a payment settlement becomes irrevocable and unconditional, so it cannot be reversed by the payer or the system.
Clearing: The process of exchanging payment instructions between banks and calculating what each bank owes the others.
Payment flow diagram showing The UK payments landscape at a glance.
Practise this lesson
Exercise
Decide which settlement model fits the scenario in this lesson and explain why.
Use the settlement models, the liquidity trade-off and the finality rules in this lesson.
- What to do. Name the model, state when settlement becomes final, and explain what happens if the sending bank does not have enough liquidity.
Correct result. Real time gross settlement settles each payment individually in central bank money with immediate finality, but it needs liquidity for every payment. Deferred net settlement nets payments and settles the net position, which needs less liquidity but leaves settlement risk until the net settles.
Why. Settlement is where money actually moves. The model decides the risk, the liquidity need, and when the payment is truly final.
Check your understanding
Practice question
A UK employer pays salaries that must reach staff accounts on the same day. Which system is normally used?
Takeaway and next step
What to remember
The analyst must understand these features as well as the systems, because they shape the customer experience more than the clearing mechanics do.
Follow a payment through every stage, from instruction to beneficiary credit, and note where it can stop.
Open the Payment Lifecycle Simulator →
Builds on "SEPA Instant Payments Regulation: phased obligations from 2025".
Transcript and full text
Show transcript
The United Kingdom runs its domestic sterling payments on three main systems that have grown up over different decades and now sit side by side, each serving a distinct purpose. Faster Payments Service, known as FPS, is the near real time system for retail and commercial payments. CHAPS is the real time gross settlement system for high value, time critical payments. BACS is the batch system that moves salaries, direct debits and regular bill payments in a three day cycle. Together they move almost every pound that changes hands inside the UK, and a business analyst who works on UK payments must know all three, because a customer requirement that sounds simple, such as pay this supplier today, can mean three different things depending on the value, the urgency and the cost the customer will accept. The three systems are operated by different organisations under the oversight of the Bank of England and the Payment Systems Regulator. Pay.UK operates Faster Payments and BACS, having brought the two schemes together under one operator, while the Bank of England operates CHAPS. This structure is the result of a long history. BACS dates from the late 1960s, CHAPS from 1984, and Faster Payments from 2008. Each system was built for the needs of its time, and each has been modernised since, but their fundamental characters have not changed. BACS is slow and cheap and built for volume, CHAPS is fast and expensive and built for finality, and Faster Payments is fast and cheap and built for the everyday payments that need to arrive today. The history explains the character of each system. BACS was created in the late 1960s to automate the paper based clearing of cheques and salary payments, and it still carries the batch logic of that era: files, a three day cycle, and control totals. CHAPS was created in 1984 for high value same day settlement, and it still carries the logic of a central bank settlement system: gross settlement, finality, and a cut off. Faster Payments was created in 2008 because a routine payment between two UK banks could still take three days through BACS, and it still carries the logic of a retail instant system: seconds to credit, deferred net settlement, and a per transaction limit. An analyst who knows the history can predict how each system will behave, because the history is the design. The volumes put the three systems in perspective. BACS processes billions of payments a year and is the highest volume system, because it carries every salary, every direct debit and every regular bill payment in the country. Faster Payments processes billions of payments a year as well, and its volume grows every year as more payments move from BACS and from cheques. CHAPS processes far fewer payments, tens of millions a year, but each one is large, and the total value is in the trillions of pounds. The lesson is the same as in the US: the system that moves the most payments is the cheapest and slowest, and the system that moves the most money per payment is the most expensive and the fastest. The analyst must choose between those poles for every payment. Addressing in the UK is by sort code and account number. The sort code is six digits and identifies the bank and the branch, and the account number is usually eight digits and identifies the account at that branch. There is no check digit algorithm on a UK account number comparable to the IBAN MOD 97 check, so a mistyped account number can pass format validation and still be wrong. Confirmation of Payee is the defence: it checks whether the name entered by the payer matches the name on the account that the sort code and account number identify, and it returns a match, a close match, a no match, or an account that cannot be checked. The analyst must design Confirmation of Payee into every payment journey, because it is the only check that catches a payment to the wrong person before the money moves. The UK also has a strong culture of direct debits, standing orders and confirmation of payee, which are features that sit on top of the three systems rather than being systems themselves. A direct debit is a BACS instruction that lets a biller collect from a customer account. A standing order is a regular payment instruction that a customer sets up with their bank, usually sent through Faster Payments today. Confirmation of Payee is a service that checks whether the name entered by the payer matches the name on the beneficiary account, and it is now a standard part of the UK payment journey. The analyst must understand these features as well as the systems, because they shape the customer experience more than the clearing mechanics do. A customer does not say they want a Faster Payments payment; they say they want to pay the supplier today, and the analyst translates that into the system. The New Payments Architecture is the future the analyst should know about. Pay.UK ran a programme called the New Payments Architecture to build a single new clearing infrastructure to replace the separate Faster Payments and BACS infrastructures, with a single set of ISO 20022 messages. That procurement was cancelled, and the work is now called Interbank Infrastructure Renewal (IIR); Pay.UK current focus is operating and optimising the existing Faster Payments and BACS systems, with a transition to next-generation infrastructure in the future. Source: Payment Systems Regulator, Interbank Infrastructure Renewal, updated 14 October 2025 and a single way of connecting. The migration will take years, and during it the three systems will continue to run side by side. The analyst should design new payment products on ISO 20022, because that is the message standard the new architecture uses, and should avoid building new dependencies on the old proprietary formats. The three systems in this chapter are the present; the New Payments Architecture is the future, and the analyst who understands both can design a product that works today and migrates tomorrow without a rebuild.
The United Kingdom runs its domestic sterling payments on three main systems that have grown up over different decades and now sit side by side, each serving a distinct purpose. Faster Payments Service, known as FPS, is the near real time system for retail and commercial payments. CHAPS is the real time gross settlement system for high value, time critical payments. BACS is the batch system that moves salaries, direct debits and regular bill payments in a three day cycle. Together they move almost every pound that changes hands inside the UK, and a business analyst who works on UK payments must know all three, because a customer requirement that sounds simple, such as pay this supplier today, can mean three different things depending on the value, the urgency and the cost the customer will accept.
The three systems are operated by different organisations under the oversight of the Bank of England and the Payment Systems Regulator. Pay.UK operates Faster Payments and BACS, having brought the two schemes together under one operator, while the Bank of England operates CHAPS. This structure is the result of a long history. BACS dates from the late 1960s, CHAPS from 1984, and Faster Payments from 2008. Each system was built for the needs of its time, and each has been modernised since, but their fundamental characters have not changed. BACS is slow and cheap and built for volume, CHAPS is fast and expensive and built for finality, and Faster Payments is fast and cheap and built for the everyday payments that need to arrive today.
The history explains the character of each system. BACS was created in the late 1960s to automate the paper based clearing of cheques and salary payments, and it still carries the batch logic of that era: files, a three day cycle, and control totals. CHAPS was created in 1984 for high value same day settlement, and it still carries the logic of a central bank settlement system: gross settlement, finality, and a cut off. Faster Payments was created in 2008 because a routine payment between two UK banks could still take three days through BACS, and it still carries the logic of a retail instant system: seconds to credit, deferred net settlement, and a per transaction limit. An analyst who knows the history can predict how each system will behave, because the history is the design.
The volumes put the three systems in perspective. BACS processes billions of payments a year and is the highest volume system, because it carries every salary, every direct debit and every regular bill payment in the country. Faster Payments processes billions of payments a year as well, and its volume grows every year as more payments move from BACS and from cheques. CHAPS processes far fewer payments, tens of millions a year, but each one is large, and the total value is in the trillions of pounds. The lesson is the same as in the US: the system that moves the most payments is the cheapest and slowest, and the system that moves the most money per payment is the most expensive and the fastest. The analyst must choose between those poles for every payment.
Addressing in the UK is by sort code and account number. The sort code is six digits and identifies the bank and the branch, and the account number is usually eight digits and identifies the account at that branch. There is no check digit algorithm on a UK account number comparable to the IBAN MOD 97 check, so a mistyped account number can pass format validation and still be wrong. Confirmation of Payee is the defence: it checks whether the name entered by the payer matches the name on the account that the sort code and account number identify, and it returns a match, a close match, a no match, or an account that cannot be checked. The analyst must design Confirmation of Payee into every payment journey, because it is the only check that catches a payment to the wrong person before the money moves.
The UK also has a strong culture of direct debits, standing orders and confirmation of payee, which are features that sit on top of the three systems rather than being systems themselves. A direct debit is a BACS instruction that lets a biller collect from a customer account. A standing order is a regular payment instruction that a customer sets up with their bank, usually sent through Faster Payments today. Confirmation of Payee is a service that checks whether the name entered by the payer matches the name on the beneficiary account, and it is now a standard part of the UK payment journey. The analyst must understand these features as well as the systems, because they shape the customer experience more than the clearing mechanics do. A customer does not say they want a Faster Payments payment; they say they want to pay the supplier today, and the analyst translates that into the system.
The New Payments Architecture is the future the analyst should know about. Pay.UK ran a programme called the New Payments Architecture to build a single new clearing infrastructure to replace the separate Faster Payments and BACS infrastructures, with a single set of ISO 20022 messages. That procurement was cancelled, and the work is now called Interbank Infrastructure Renewal (IIR); Pay.UK current focus is operating and optimising the existing Faster Payments and BACS systems, with a transition to next-generation infrastructure in the future. Source: Payment Systems Regulator, Interbank Infrastructure Renewal, updated 14 October 2025 and a single way of connecting. The migration will take years, and during it the three systems will continue to run side by side. The analyst should design new payment products on ISO 20022, because that is the message standard the new architecture uses, and should avoid building new dependencies on the old proprietary formats. The three systems in this chapter are the present; the New Payments Architecture is the future, and the analyst who understands both can design a product that works today and migrates tomorrow without a rebuild.
Full lesson text (all scenes)
Completing a lesson updates your progress dashboard on the homepage.
Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.