The New Payments Architecture (NPA): What Replaces Faster Payments

The UK's Faster Payments Service (FPS) launched in 2008 and has quietly become critical national infrastructure, clearing billions of transactions a year. But the platform it runs on is old, and the industry has spent more than a decade planning its successor: the New Payments Architecture (NPA). If you build payment products in the UK, or you simply want to understand where domestic instant payments are heading, the NPA is the programme to watch.

Why replace something that works?

FPS does its job, but it carries structural limitations. It uses ISO 8583-derived messaging with tight field constraints, so remittance data and structured references are limited. It was designed as a single centralised scheme with a single infrastructure provider, which concentrates risk and slows innovation. And Bacs, the UK's older batch rail for Direct Debit and Direct Credit, runs on a separate three-day cycle that most consumers find baffling.

The NPA is the industry's answer. Coordinated by Pay.UK, the retail payments operator, it aims to provide a single, modern clearing and settlement layer that eventually carries both instant single payments and the recurring flows that Bacs handles today. The guiding idea is to separate the thin, competitive layer of overlay services from a stable, standardised central infrastructure.

What actually changes

Several things distinguish the NPA from the rails it replaces:

• ISO 20022 messaging. The NPA is built on the ISO 20022 standard, replacing the legacy formats FPS uses. That means richer, structured data: full creditor and debtor details, structured remittance information, and purpose codes travel with the payment.
• A push-payment core. The central infrastructure focuses on clearing and settlement of credit transfers, with overlay services (like Request to Pay or confirmation of payee) built on top rather than baked in.
• Competitive procurement. Rather than one permanent supplier, the clearing and settlement infrastructure is procured competitively, with the aim of avoiding single-vendor lock-in.
• Fraud and data tooling. Because more structured data travels with each message, the architecture is meant to support better real-time fraud detection and reconciliation.

The timeline reality

The NPA has been in planning since the mid-2010s, and its scope has repeatedly narrowed. Early visions imagined a sweeping overlay ecosystem; regulators later pushed Pay.UK to focus first on replacing FPS's core clearing and settlement capability to avoid cost overruns. The programme has seen multiple resets, and delivery dates have slipped by years. Anyone planning a product around the NPA should treat published dates as directional rather than firm.

This is a useful lesson in payments infrastructure generally: replacing a live rail that clears billions of transactions is extraordinarily hard. The migration cannot break existing flows, every participant must move in lockstep, and the fallback if something goes wrong is a national payments outage. Caution is rational.

How it relates to Bacs and FPS today

For now, FPS and Bacs both continue to operate. FPS handles near-instant single payments, typically settling to the beneficiary within seconds and carrying a value limit that has risen over time to £1 million per transaction (individual banks may set lower limits). Bacs continues its three-working-day cycle for Direct Debits and salary or supplier Direct Credits. The NPA's long-term goal is to bring these onto a common ISO 20022 core, but the transition is incremental. In the meantime, the UK also runs Confirmation of Payee, a name-checking overlay that reduces misdirected and authorised push payment fraud, and is rolling out Request to Pay as a messaging layer for billers.

What builders should take away

If you are integrating UK payments, design for ISO 20022 now. Even before the NPA fully lands, the direction of travel is unambiguous: structured data, richer references, and a clearer separation between core clearing and value-added overlays. Products that assume the thin, unstructured world of legacy FPS messaging will need rework. Products that model payments as structured, data-rich objects will migrate more gracefully.

Key takeaways

• The NPA is the UK's programme, led by Pay.UK, to replace the ageing Faster Payments and eventually Bacs infrastructure.
• Its defining features are an ISO 20022 messaging core, a push-payment clearing and settlement layer, competitively procured infrastructure, and support for overlay services.
• The programme has repeatedly narrowed in scope and slipped in timeline; treat published dates as directional.
• FPS (near-instant, up to £1 million) and Bacs (three-day cycle) still run today alongside overlays like Confirmation of Payee.
• Build for structured ISO 20022 data now, because that is the durable direction regardless of exact NPA dates.