Retail Payments Need a New Core

Why the next phase of payment regulation is moving toward infrastructure design, resilience and fraud-ready systems

Retail payments are often judged by what users see.

A checkout screen.
A bank app.
A transfer confirmation.
A payment request.
A refund notification.

But the real strength of a payment system depends on what sits underneath: clearing, messaging, settlement logic, resilience, fraud controls, data quality and the rules that connect participants across the ecosystem.

That is why the latest consultation on the UK’s next-generation retail payments infrastructure is important.

It is not only about upgrading payment rails.

It is about asking a deeper question: what kind of core infrastructure should modern retail payments be built on?

From payment products to payment foundations

The payment industry often focuses on products.

Cards, wallets, bank transfers, instant payments, request-to-pay, account-to-account payments, merchant tools and payment apps all compete for attention.

But products can only scale reliably when the infrastructure underneath them is strong enough.

Core payment infrastructure needs to support safety, resilience, interoperability, competition and innovation. It needs to allow different providers to build user-facing services while relying on a trusted foundation for clearing, messaging and inter-participant obligations.

This is where regulation and infrastructure meet.

Regulators are no longer only asking whether payment firms follow rules. They are increasingly asking whether the underlying system can support the next generation of payment journeys.

Why clearing and messaging matter

Clearing and messaging may sound technical, but they directly shape the user experience.

They affect how payment information moves between participants, how quickly payment status can be confirmed, how exceptions are handled, how fraud signals can be shared, how reconciliation data is structured and how new payment products can be built.

A payment system with weak messaging creates operational friction.

A payment system with limited data makes reconciliation harder.

A payment system with poor exception handling creates support workload.

A payment system without strong fraud-prevention capabilities exposes users and firms to higher risk.

This is why the core layer matters.

It is not visible to the end user, but it determines how reliable, safe and adaptable the payment experience can be.

Regulation is becoming more design-led

The next phase of payment regulation is becoming more design-led.

It is not enough to set broad policy objectives such as competition, innovation, safety and consumer protection. Those objectives need to be translated into infrastructure choices.

Should the core support richer data?

Which fraud-prevention capabilities should sit at the infrastructure level?

How should account-to-account payments evolve?

How should new payment journeys be enabled without weakening resilience?

How should interoperability with future forms of money be supported?

How should the system balance innovation with operational stability?

These are not abstract policy questions.

They are design questions.

And the answers will shape how payment firms, banks, fintechs, businesses and consumers experience retail payments over the coming years.

Fraud prevention belongs in the infrastructure conversation

One of the most important themes is fraud prevention.

As payments become faster and more digital, the time available to detect and stop fraud becomes shorter. This means fraud controls cannot only exist as after-the-event investigations or customer reimbursement processes.

They need to be built into the payment workflow.

That may include stronger payee verification, richer transaction data, risk signals, better beneficiary information, customer warnings, delay mechanisms, exception workflows and data-sharing models.

The infrastructure layer can play an important role here.

Not every fraud control needs to sit at the core. But some capabilities may be more effective when they are enabled, standardised or coordinated at system level.

The challenge is to design fraud prevention without making payments unnecessarily slow or difficult to use.

That balance will become central to the next generation of retail payments.

Digital identity and trust signals

Another important area is digital identity.

Retail payment systems increasingly need better ways to establish trust between parties.

For example, credentials and verified attributes could help users understand whether a requested payment is legitimate, whether the recipient is correctly identified, or whether a business relationship is genuine.

This matters because fraud is no longer only about stolen credentials.

It is increasingly about manipulation, impersonation and social engineering.

Digital identity frameworks, legal entity identifiers and verifiable credentials could become part of the trust layer around payments.

If implemented well, they could reduce fraud, improve payment confidence and support better business-to-business and consumer payment experiences.

But they also need careful governance.

Identity tools must support privacy, proportionality, security and interoperability. Otherwise, they can create new risks or unnecessary complexity.

Interoperability with future forms of money

Retail payment infrastructure also needs to be future-ready.

The payments landscape is changing quickly. Instant payments, account-to-account payments, digital wallets, tokenised deposits, regulated stablecoins, central bank digital currencies and other forms of digital money may all play different roles in the future.

No one can predict the exact shape of the payment market.

That is why infrastructure needs adaptability.

The core system should not be designed only for today’s payment journeys. It should be flexible enough to support new use cases, new data requirements, new settlement models and new forms of money as they emerge.

This is not about chasing every trend.

It is about avoiding infrastructure that becomes obsolete too quickly.

Why businesses should pay attention

For businesses, retail payment infrastructure may sound distant.

It is not.

The design of the core payment system affects checkout, supplier payments, refunds, reconciliation, customer communication, treasury visibility and fraud exposure.

If the next generation of infrastructure supports richer data, businesses may gain cleaner reconciliation and fewer manual investigations.

If it supports better fraud controls, businesses may face fewer scams and misdirected payments.

If it supports stronger account-to-account journeys, merchants may gain more payment choice.

If it supports interoperability, businesses may find it easier to adopt new payment methods without rebuilding their entire operating model.

Payment infrastructure decisions eventually become business operating conditions.

The operational lesson

The practical lesson is clear: retail payments need more than faster rails.

They need a stronger core.

That core should support resilience, data quality, fraud prevention, interoperability, operational clarity and innovation.

The future of payments will not be defined only by user-facing apps or new payment brands. It will be defined by whether the underlying infrastructure can support safe, trusted and efficient payment journeys at scale.

This is where regulation and market design become inseparable.

MetaNord’s view

At MetaNord, we see the next generation of retail payments as an infrastructure question first.

The most valuable payment systems will not only move money quickly.

They will make payments easier to verify, easier to reconcile, easier to monitor and easier to operate across different business workflows.

Regulation is increasingly moving in that direction.

It is no longer only about rules after the fact. It is about designing payment systems that are resilient, fraud-aware and adaptable from the beginning.

Retail payments need a new core because the market around them has changed.

Speed matters.

But trust, data, resilience and operational control matter just as much.