ISO 20022 Is Entering Its Next Phase: How Payment Providers Can Prepare for CHAPS 2027

For years, ISO 20022 has been framed as a migration story. Could banks and payment providers move off legacy formats, meet scheme deadlines, and keep payments flowing while the plumbing changed underneath?

That was the challenge then. This is the challenge now: can you actually operationalize the richer data ISO 20022 was designed to deliver?

Because the next phase of ISO 20022 is not about supporting a new message format. It is about capturing, governing and acting on more structured payment data across customer channels, operations, fraud controls, compliance workflows, and downstream systems. That is where the real value is. It is also where the real strain begins.

The Bank of England’s policy statement on CHAPS makes that clear. From November 2027, Purpose Codes will become mandatory for CHAPS payments submitted through channels under the direct control of direct participants, building on the enhanced data requirements already introduced in May 2025. The stated goal is not administrative neatness. It is better straight-through processing, stronger payment prioritization, improved analytics, and better fraud prevention.

That shift matters because many organizations are still treating ISO 20022 as a compliance exercise, when in reality it is becoming an operational readiness test.

It is one thing to pass richer fields through a payment message. It is another to ensure those fields are captured properly at source, interpreted consistently across systems, and used confidently in genuine business processes. That is the difference between technical compliance and practical advantage.

This is where many payment providers will feel the pressure.

Not because they do not understand ISO 20022, but because their payment data lives across fragmented estates: core systems, channel applications, fraud tooling, sanctions controls, customer service environments, reporting stacks, and case management processes. Richer payment data exposes those seams. A new field like a Purpose Code may look simple on paper, but in practice it introduces questions about customer journeys, validation rules, downstream usage, governance, and accountability.

That challenge is already visible in industry feedback. UK Finance highlighted concerns around change capacity, legacy complexity, customer education, the practical use of Purpose Codes and the risk of unintended consequences if richer data is applied inconsistently in operational controls.

This is why 2027 should not be treated as another date on the payments roadmap. It should be treated as a prompt to rethink the data foundation behind payments modernization.

The institutions that do this well will not simply be more compliant. They will be more adaptive.

They will be better able to validate richer data at source, apply it consistently across fraud and compliance workflows, improve payment transparency, reduce manual intervention and respond faster as requirements evolve. That was always the promise of ISO 20022. The difference now is that the market is moving from message modernization to data operationalization. SWIFT has long positioned ISO 20022 around richer, more structured data that improves automation, interoperability and processing quality across the payments chain. The value only materializes when that data is reliable and usable in practice.

This is exactly where the Progress Data Platform changes the conversation.

The Progress Data Platform helps organizations unify, govern and activate distributed data without forcing them to rip and replace the systems they already depend on. It works alongside existing architectures, connecting enterprise data, applying shared context and governance and delivering trusted information to the applications and services that drive the business.

In payments, that matters because ISO 20022 is not just creating more data. It is creating more meaning.

A Purpose Code is not valuable simply because it exists in a message. It becomes valuable when the business can trust it, validate it and use it dynamically across the payment lifecycle. That might mean applying policy rules consistently, improving prioritization decisions, supporting fraud detection, enriching case handling or strengthening downstream insight. To do that well, you need more than a schema update. You need a governed context layer.

That is what the Progress Data Platform is built to provide.

By securely connecting to existing data sources, enriching them with semantic meaning and enforcing governance, the platform helps organizations turn scattered payment information into trusted operational context. That makes it easier to work across structured and unstructured data, apply consistent meaning across systems and support explainable, policy-driven outcomes. It also means organizations can adapt more easily as scheme guidance, customer expectations and regulatory demands continue to evolve.

And that adaptability is going to matter.

CHAPS migrated to ISO 20022 in 2023. Enhanced data requirements expanded in 2025. Mandatory Purpose Codes arrive in 2027. This is not a one-time migration. It is an evolving operating environment, and payment providers should expect richer data requirements, stronger expectations and more scrutiny over how payment information is captured and used.

That is why the smartest response is not to ask, “How do we meet the next requirement?”

It is to ask, “How do we build a payment data foundation that can keep up with change?”

For payment providers, that means focusing on three things now.

• Can you capture richer data in ways that fit real customer and operational journeys, not just message specifications?

• Can you apply consistent meaning and policy to that data across payments, fraud, compliance and service operations?

• Can you adapt as scheme requirements evolve, without rebuilding the estate every time the market moves?

Those are no longer side questions. They are fast becoming the real measure of payment modernization maturity.

The next competitive advantage in payments will not come from having richer ISO 20022 fields available. It will come from being able to trust them, use them and adapt around them. That is why this next phase of ISO 20022 matters so much. It marks the point where messaging modernization becomes a context, governance and operational agility challenge.

And that is exactly where the Progress Data Platform can help payment providers move from compliance to confidence.

If ISO 20022 was the language change, 2027 is the operational test.

So, what next?

Preparing for CHAPS 2027 means looking beyond message compliance and building the governed, adaptable data foundation payments modernization now demands. Explore the Progress Data Platform to see how Progress helps organizations unify payment data, apply context and governance, and respond to change with more confidence.