Adoption of Cross Border Payments and Reporting (CBPR+) Hybrid Address and Local Market Compliance
Effective November 2026, SWIFT CBPR+ message validation requirements and leading Payment Market Infrastructures (PMIs) will require that cross-border payment messages subject to those rules include both a town/city name and a country code in beneficiary payment postal address fields, as part of the Cross Border Payments and Reporting Plus (CBPR+) initiative. These updates are intended to support compliance efforts and increase automation in payment processing.
What’s changing?
Currently, you must use one of three formats for postal addresses in your payment messages:
- Fully unstructured:
This format will be phased out by November 14, 2026. After that, all addresses must use either the structured or hybrid format. - Fully structured:
Address details are separated into specific fields, such as street name, post code, town, and country. - Hybrid:
Combines structured elements (Town name and Country code) with up to two unstructured address lines for flexibility during the transition.
Who is impacted?
These requirements apply to cross-border payments sent over the SWIFT network and to payments processed through clearing systems that require hybrid or fully structured addresses, such as SEPA, Swiss payment systems, Fedwire, and CHIPS. Payments that do not follow the new address formats may be rejected or delayed, which could impact your processing timelines.
What you need to do
- Make sure your systems can provide a structured Town name and Country code (ISO 2-letter format) for each party in your payment messages.
- The impacted APIs listed below have no technical changes, but payments may be rejected or delayed if required address elements are missing.
- If you don’t have Town name and Country code details for your payees, please reach out to them and collect this information as soon as possible to avoid disruptions.
- The details about the impacted APIs along with mocks will be available on our Developer Portal. Please stay tuned for updates to data dictionary and mocks on these pages.
Impacted APIs
Impacted APIs | Scope |
Wires Payments v1 | Global |
Wires Payments v2 | Global |
Global Payment v1 | SEPA region only |
Global Payments v2 | Wires, SEPA region only |
Global Mass Pay | Global |
Low Value ACH – Credit Transfer | SWISS & SEPA region only |
Low Value ACH – Direct Debit | SWISS & SEPA region only |
SEPA Instant API (Deprecated) | Existing clients only |
Example:
The sample below shows how to update address fields for one party. Please be sure to apply these changes to all parties where address information is required in your API specifications.
Additional values to be populated for CBPR+ changes
This guidance does not replace any legal or regulatory requirements
This guidance does not replace any legal or regulatory requirements and is not legal, tax, or compliance advice. You are responsible for ensuring payment information is complete and accurate and that your payment practices comply with applicable requirements. Requirements and timelines may change based on market practice or network rules.
We are here to help
Start your internal assessments early to help ensure a smooth transition. If you have any questions or need support as you prepare for this change, contact our support team at at hybrid.address.migration@jpmchase.com.