The cross-border payment address can no longer be filled in casually.
Whether a cross-border payment will be declined or delayed, it may first get stuck on a seemingly inconspicuous field: the address.
The payment industry has noticed that Swift recently issued an ISO 20022 payment migration action reminder, pointing to the key node of November 2026.
According to Swift’s arrangement, after November 14, 2026, unstructured addresses will be removed, and only fully structured addresses or mixed structured addresses will be accepted in cross-border payment messages.
The address has always been part of the cross-border payment information, but in the past it was more like an auxiliary description, and in the future it will become a basic field that affects whether the payment can be transmitted smoothly.
The so-called unstructured address can be understood as writing the address information as a whole piece of free text.
People may be able to determine the country, city, street and zip code after seeing it, but the system may not be able to stably separate and identify it.
The structured address requires relevant information to be put into corresponding fields, so that different institutions, different systems and different market infrastructures can more accurately identify, verify and process payment information when transmitting it.
April data disclosed by Swift shows that 61.2% of payments still contain unstructured payer postal addresses, and 62.9% of payments contain unstructured payee information.
This set of data shows that there is still a lot of room for structural transformation of addresses in global cross-border payment links before the key node of November 2026.
The more direct impact is on payment processing.
Swift made it clear that there are no Swift emergency measures for non-compliant messages.
Payments that do not contain structured or mixed structured address data may be declined or delayed in the payment chain.
Financial institutions therefore need to establish corresponding processes to handle issues such as rejection, remediation and customer communication when customers do not provide structured data or provide incorrect information.
This is also the most underestimated aspect of this announcement.
On the surface, it is an adjustment of message fields in the ISO 20022 migration, but it actually points to an improvement in the quality of basic cross-border payment data.
The longer the cross-border payment link, the more parties involved, and the less blurry the basic data must be.
If an address information cannot be accurately identified, subsequent steps may increase the cost of manual repair, compliance screening and customer communication.
For financial institutions, address structuring is not a modification of a single field, but a set of process adjustments from customer notification, channel collection, system verification to exception repair.
Swift mentioned in the action reminder that financial institutions need to explain the requirements to corporate customers and partners to ensure that at least the payee city and country information can be obtained; at the same time, they must coordinate system updates with technical partners and transform channel applications so that they can structure address information and verify whether customer data conforms to the target format before initiating payment.
This will involve bank front-end channels, bank-enterprise direct interfaces, customer payment templates, data verification rules and back-end operation processes.
In the past, customers submitted a piece of free text, and the bank or system might be able to continue processing it; in the future, after the rules are switched, financial institutions need to complete data verification as much as possible before initiating payment to avoid problems being exposed in the middle and later stages of the payment chain.
An important signal from this reminder is that the ISO 20022 migration is being transmitted from the banking system to the source of corporate payment.
Swift mentioned that starting from November 2026, enterprises can continue to send MT101 initiation messages to financial institutions, and there is currently no deadline for enterprises to migrate to SCORE+.
However, as the unstructured postal address field is removed, businesses that continue to use MT101 will need to upgrade to field 59 option F to meet the structured address requirements.
Enterprises also need to obtain the payee address information through their own channels, save it in the ERP or fund management system, and provide it to the bank when initiating payment.
As per Swift instructions, the minimum requirements include city name and country.
This requirement applies to different channels, including MT101 SCORE, pain.001 SCORE+ and bank-owned channels.
The bank requires this information to execute the payment.
This is a practical reminder for companies that often initiate cross-border payments.
Cross-border payments cannot just temporarily fill in the payee information when the payment is initiated. The payee’s address, city, country and other basic information need to be entered into the supplier database, payment template and fund management system in advance.
ISO 20022 migration does not only occur between banks, but will also be transmitted to enterprises.
The earlier the company organizes the basic information of the payee, the lower the uncertainty will be in subsequent cross-border payments.
If an enterprise relies on free text to save addresses for a long time, or if the address format is inconsistent between different systems, subsequent adaptation costs may rise.
For Chinese foreign trade companies, cross-border e-commerce sellers and group enterprises, the significance of this reminder is not to immediately change all payment processes, but to see in advance the direction of changes in cross-border payment data requirements.
When companies make payments with overseas suppliers, service providers, platforms and partners, the more standardized the basic information such as the payee’s address, city, and country, the lower the uncertainty will be when subsequent cross-border payments are initiated through banks or related channels.
For cross-border payment service providers, this announcement is also of reference significance.
As the requirements for structured data increase, service providers cannot only emphasize multi-currency, multi-channel, low rates and payment speed, but also need to provide more support in customer information collection, address format prompts, verification before payment initiation, return repair mechanism and bank interface adaptation.
In the future, the differentiation of cross-border payment services will not only be reflected in where funds can be delivered, but also in the ability to help customers reduce data errors, format inconsistencies and subsequent repair costs before payment is initiated.
Of course, Swift’s announcement is mainly aimed at financial institutions, corporate customers and payment market infrastructure.
Judging from industry trends, the closer the payment service chain is to customers, the more it is necessary to deal with data quality issues in advance before payment is initiated, rather than waiting until payment is rejected or delayed to remedy it.
Swift also mentioned that its open-source, AI-powered address structuring solution is free to use to help organizations meet ISO 20022 requirements and structure customer information.
Swift’s Data Quality Analytics is also available for free in 2026 to help institutions view the completeness, consistency and structure of ISO 20022 payment data.
The emergence of AI tools also shows that address management is not easy.
If the address information in different countries, different languages, and different writing habits is stored in the system as free text for a long time, subsequent unified sorting, identification, and verification will require costs.
AI can help identify and organize addresses, but the real transformation still has to start from the source of the data of institutions and enterprises themselves.
Payment industry analysts believe that competition in the cross-border payment industry is extending from channel coverage, price and payment speed to data quality and operational processing capabilities.
Customer information, payment messages, address fields and exception repair capabilities are becoming important components of cross-border payment services.
The more solid the relevant capabilities are, the fewer returns, delays, and backlogs there will be in the payment process.
Cross-border payments transfer not only funds, but also a complete set of data required for payers, payees, accounts, banks, addresses, purposes, fees and compliance screening.
Any ambiguity in any basic field may be amplified in cross-border links.
The longer the cross-border payment link, the less basic data can be treated as background details.
Address structuring is just an entry point, which points to whether the payment information can be stably recognized by different institutions, different systems and different markets.
After November 2026, the address field will no longer be just text information that can be filled in vaguely.
For financial institutions, corporate customers and related cross-border payment service participants, in order for cross-border payments to be faster, the first step is to make the data clearer.
