UK Faster Payments vs India UPI

The UK's Faster Payments Service (FPS) and India's Unified Payments Interface (UPI) are both celebrated instant account-to-account systems. But they were designed a decade apart with different goals, and comparing them is a masterclass in how instant payments can be architected. Understanding the contrast helps you appreciate the design choices behind any instant rail.

Origins and goals

FPS launched in 2008 to give the UK near-instant electronic transfers, replacing the slow three-day cycle for many payments. It was built as a bank-centric scheme: a way for existing banks to move money between accounts faster.

UPI launched in 2016, built by the National Payments Corporation of India (NPCI). Its goal was broader: to drive financial inclusion and a cashless economy at massive scale, with a design that invited fintechs and apps to build on top. Where FPS modernised bank transfers, UPI reimagined the interface layer entirely.

Addressing: account numbers versus virtual IDs

A defining difference is how you tell the system where money should go.

• FPS uses the traditional sort code and account number. To pay someone you need their bank details, and the UK layered Confirmation of Payee on top to check that the name matches the account, reducing misdirected and fraud payments.
• UPI introduced the Virtual Payment Address (VPA) — a human-friendly handle like name@bank — so users can pay without sharing bank account numbers. UPI also popularised paying by QR code and by mobile number, abstracting the underlying account entirely.

This addressing difference shapes the whole user experience. UPI's identifiers are designed for phones and merchants; FPS's are the banking details customers already had.

Architecture: scheme versus interface layer

FPS is fundamentally a clearing scheme with a central switch that routes payments between banks, settling on a deferred net basis in central bank money at the Bank of England. Banks connect and expose the capability to their customers through their own apps.

UPI is an interoperable interface layer sitting above bank accounts. NPCI operates a central switch, but the genius of UPI is the separation of the payment interface from the bank. A single app can let a user transact across any of their bank accounts, and any UPI app can pay any other, because they all speak to the common NPCI layer. This open architecture is why hundreds of banks and dozens of third-party apps interoperate seamlessly, and why third parties rather than banks own much of the user experience.

Scale and behaviour

The two systems operate at very different magnitudes. UPI processes an extraordinary volume — many billions of transactions per month — driven by ubiquitous person-to-merchant QR payments for even the smallest purchases. It has become the default way to pay across India. FPS handles very large value and high volumes too, but its usage skews more toward person-to-person transfers, bill payments, and business payments rather than tap-and-QR retail at the point of sale.

Both share core instant-payment properties: near-real-time crediting, push-based transfers, and general finality once settled. Both also confront the same fraud reality — instant and irrevocable payments demand strong upfront controls, whether that is Confirmation of Payee in the UK or PIN-based authorisation and app-level protections in UPI.

Two philosophies

The deepest contrast is philosophical. FPS made bank transfers fast, keeping the bank at the centre and the account number as the identifier. UPI made payments open, pushing the interface out to any app and replacing account numbers with virtual handles and QR codes. Neither is simply better; they solved different problems for different markets. FPS modernised an existing banking population; UPI built rails for rapid inclusion and a mobile-first retail economy. The takeaway for anyone designing an instant scheme is that the settlement engine and the addressing and interface layer are separable choices, and the second often shapes adoption more than the first.

Key takeaways

• FPS (2008) modernised UK bank transfers; UPI (2016, by NPCI) built an open, mobile-first payments layer for inclusion at scale.
• FPS uses sort code and account number with Confirmation of Payee; UPI uses Virtual Payment Addresses, QR codes, and mobile numbers.
• FPS is a bank-centric clearing scheme; UPI is an interoperable interface layer that separates the payment app from the bank account.
• UPI processes billions of person-to-merchant transactions monthly; FPS skews toward P2P, bills, and business payments.
• Both are instant, push-based, and largely final, so both depend on strong upfront fraud controls.