The Anatomy of a Faster Payment, End to End

Tap send on a UK bank transfer and, within seconds, the money appears in someone else's account. It feels instantaneous and simple. Underneath, a coordinated sequence of messages, checks, and obligations plays out across multiple institutions. This post traces a Faster Payment end to end so you understand what each step is actually doing.

Step one: initiation and the sending bank's checks

The journey starts when a customer instructs their bank to make a payment, either as a single immediate payment, a forward-dated payment, or a standing order. Before anything leaves the bank, the sending institution performs its own controls: verifying the account has sufficient funds, running fraud and sanctions screening, and increasingly checking the beneficiary name against the account via Confirmation of Payee. If any check fails, the payment never enters the scheme.

Once cleared internally, the sending bank formats the instruction as a scheme message and submits it to the central infrastructure. Faster Payments messaging historically uses an ISO 8583-derived format known within the scheme, carrying the sort codes and account numbers of both parties, the amount, and a reference.

Step two: the central switch

The message travels to the Faster Payments central infrastructure, the switch operated on behalf of Pay.UK. The switch validates the message structure, checks that both the sending and receiving institutions are participants, and routes the payment to the beneficiary bank. It also records the obligation created between the two banks, because although the customer experience is instant, the actual movement of money between banks happens later.

This is the key mental model: Faster Payments separates clearing (the exchange and acceptance of payment instructions in real time) from settlement (the actual transfer of funds between the banks). The customer sees clearing; the banks care about settlement.

Step three: the beneficiary bank decides

The receiving bank gets the routed message and runs its own validation: does the account exist, is it open and able to receive funds, does the payment trip any fraud or sanctions rules? The scheme sets a tight response window — the beneficiary bank is expected to accept or reject within seconds. If it accepts, it credits the beneficiary's account and sends a positive response back through the switch to the sending bank, which confirms success to the customer.

Crucially, the beneficiary bank credits the customer before interbank settlement has happened. It is effectively extending short-term credit against the promise of settlement, which is why the scheme imposes limits and controls to manage that risk.

Step four: deferred net settlement

Individual payments are not settled one by one between banks. Instead, Faster Payments uses deferred net settlement. Throughout the day, the switch tallies what each bank owes and is owed across all its counterparties. At defined settlement cycles — multiple times per working day — the net positions are calculated and settled across accounts held at the Bank of England in central bank money.

To protect the system if a bank fails between cycles, participants pre-fund or post collateral to cover their maximum possible net obligation. This means a settlement default by one member does not cascade into losses for others; the collateral covers it. Net settlement dramatically reduces the number of interbank transfers needed while central bank money settlement removes counterparty risk at the final step.

What can go wrong

• Rejections. The beneficiary bank can reject for a closed account, a failed name check, or a fraud flag, and the sender is notified in near real time.
• Misdirected payments. If a customer types the wrong account details and Confirmation of Payee is bypassed or unavailable, funds can land in the wrong account, triggering a recovery process.
• Authorised push payment fraud. The payment works perfectly but the customer was tricked into sending it, which is why prevention has shifted upstream to name-checking and warnings.

Key takeaways

• A Faster Payment separates real-time clearing (instruction exchange) from later settlement (actual movement of funds between banks).
• The sending bank screens and formats the instruction; the central switch validates and routes it; the beneficiary bank accepts and credits within seconds.
• The beneficiary is credited before interbank settlement, so the receiving bank briefly extends credit against the promise of settlement.
• Banks settle net positions in central bank money across multiple daily cycles at the Bank of England, backed by pre-funding or collateral to cover default risk.
• Most failure modes are rejections, misdirected payments, and authorised push payment fraud, which is why upfront checks like Confirmation of Payee matter.