CBPR+ Changes: What to know

From speed to certainty: Why better address data is the missing link in faster payments

We live in a world shaped by immediacy. Food arrives in minutes, entertainment streams instantly, and information is available at the tap of a screen. This culture of instant gratification has reshaped customer expectations across industries—and payments are no exception. When a payment is sent, the assumption is simple: it should arrive quickly, smoothly, and without friction. 

Yet behind the scenes, payments are anything but simple. 

The paradox of modern payments

On the surface, global payment networks are already fast. The majority of cross‑border payments today reach the beneficiary bank within an hour, depending on corridor, currency, and  cut off times. From a pure network and settlement perspective, enormous progress has been made over the past decade. 

And yet, a paradox remains. 

A significant proportion of those payments are not credited to the final beneficiary within that same timeframe. Funds arrive at the bank but become stuck in the “last mile”—held up by investigations, compliance checks, or missing information. The issue is no longer how fast money moves across borders; it is how reliably and confidently it can be processed once it arrives. 

Speed is solved. Delivery is not. 

Why banks have to slow payments down

Banks operate in one of the most highly regulated environments in the world. Before funds can be credited, banks typically apply controls designed to identify and screen relevant parties to a payment, consistent with applicable laws, regulations, and risk-based compliance programs. This means banks must perform: 

• Party identification and verification 
• Sanctions screening 
• Anti‑money laundering (AML) checks 
• Local regulatory and compliance validations 

These controls may be applied at multiple points in the payment chain, including by the sending bank, intermediaries, and the beneficiary bank.  

When essential data is missing or ambiguous, banks have no choice but to pause the payment. Investigations are triggered, manual reviews begin, and the instant experience customers expect quickly disappears. 

The hidden problem: Poor address data

One of the most common reasons payments are delayed is surprisingly basic: insufficient or unstructured address information. 

Historically, payment messages allowed free‑text, unstructured address fields. While flexible, this approach can produce inconsistent, incomplete, or ambiguous information: 

• City names embedded in long text strings 
• Country names missing or abbreviated incorrectly 
• Sanction‑sensitive words appearing in unintended contexts 

These issues increase false positives during screening and make it harder for banks to confidently identify payment parties. The result is friction, delay, and uncertainty—especially in cross‑border and high‑value domestic payments. 

Enter ISO 20022 and CBPR+

To address this, the global payments industry—supported by SWIFT standards and market practice initiatives —is moving toward richer, more structured data standards under ISO 20022 and the CBPR+ (Cross‑Border Payments and Reporting Plus) programme. 

At the heart of this shift is a simple principle: the richer and more structured the data, the smoother the payment. 

As part of this evolution, unstructured postal addresses are expected to be phased out for certain in-scope payment messages under SWIFT CBPR+ and certain market infrastructures. Instead, payment messages must include hybrid or fully structured addresses, ensuring that at a minimum: 

• Town/City is clearly identified 
• Country is explicitly populated 

This change can help improve data quality and support more consistent automated processing. Outcomes (including exception rates and processing times) may vary by corridor, counterparty data quality, and screening configurations.  

Understanding address formats: Unstructured vs hybrid vs structured

To demystify the terminology: 

• Unstructured address: Free‑text lines with no clear separation of elements. Flexible, but prone to inconsistency and misinterpretation. 
• Hybrid address: A pragmatic industry compromise. Core elements such as Town/City and Country are structured, while additional address details can still be provided in limited free‑text lines. 
• Fully structured address: Each component—street name, building number, postcode, town, country—is placed into a defined field. This is the most data‑rich and future‑proof option. 

Hybrid addressing strikes a balance: it raises data quality significantly without requiring clients to immediately overhaul all legacy systems. 

Why local market infrastructure matters

Address requirements are not just a SWIFT or cross‑border issue. Many local payment market infrastructures—including high‑value domestic clearing systems—are adopting similar standards 

This means the change impacts: 

• Cross‑border payments 
• High‑value and Low-value domestic payments 
• Clearing systems with ISO 20022‑based message formats 

Each clearing system operates within its own regulatory, operational, and cut‑off constraints. Missing or unstructured data could force manual intervention, especially when payments arrive outside local operating hours or fail automated checks. 

Better data at the source can help reduce these dependencies and allows markets to process payments more consistently, regardless of geography. 

Data quality starts at the source

A critical insight from the industry migration is that high‑quality payment data can only be guaranteed at its point of origin. 

This requires coordination across the payment chain: 

• Originators and corporates must supply accurate, complete address information for counterparties. 
• Banks and debtor agents must validate, structure, and transmit that data correctly. 
• Market infrastructures and correspondent banks must interpret and process it consistently. 

When any link in this chain weakens, payment speed and certainty suffer. 

Meeting modern expectation

Today’s customers do not distinguish between a bank’s internal processes and their own experience. If a payment takes hours—or days—due to preventable data issues, confidence erodes. 

The move to hybrid and structured addressing is driven by evolving standards and market practices and can also help improve operational efficiency and data quality.  It is a response to how the world now operates: real‑time, digital, and expectation‑driven. 

Payments must evolve accordingly. 

What this means for the industry—and clients

As new standards take effect, clients across the ecosystem are encouraged to consider: 

• Review and uplift existing address data 
• Ensure town and country are consistently captured 
• Align payment file formats with ISO 20022 standards 
• Avoid over‑population of fields or unsupported characters 
• Treat structured address data as a permanent global standard, not a bank‑specific requirement 

Early preparation may help reduce exceptions and support more predictable processing, depending on payment type and counterparty data quality.  

In the final mile of this journey, J.P. Morgan has a defined set of APIs and payment channels that are being updated in line with these industry changes. Details of impacted services, technical specifications, and readiness guidance are available on the firm’s Payments Developer Portal, helping enable clients to adapt their integrations in a timely and structured manner. 

A positive step forward

As the industry collectively embraces ISO 20022, CBPR+, and structured addressing, we are witnessing a meaningful shift in the payments landscape. This is not merely about compliance or standards—it is about enabling faster, more transparent, and more frictionless payments for everyone involved. 

With richer data, clearer identification, and smarter processing, the future of payments moves one step closer to matching the speed of modern life—without compromising safety, trust, or integrity. 

And that is a transformation worth making. 

This blog post is provided for informational purposes only and does not constitute legal, regulatory, tax, or compliance advice.