Swift Defers 2026 ISO 20022 Address Deadline as Over 60% of Payment Addresses Remain Unstructured
Oct. 24, 2026 • Deep Dive • Banking & Payments
Swift has deferred the payments changes planned for its 2026 standards release, withdrawing a November 14 deadline that would have led to the rejection of cross-border payment messages with unstructured postal addresses. The decision has prompted related postponements for CHAPS, Fedwire and SEPA, although Switzerland’s SIX-operated payment infrastructure is retaining its November deadline. Swift expects to determine a revised timeline for payment-related address requirements after industry consultations by December 2026.
The delay exposes a gap between adopting ISO 20022 messages and supplying the structured data they are designed to carry. Swift monitoring found that 61.2% of debtor addresses and 62.9% of creditor addresses still arrived as unstructured text, even as more than 98% of cross-border instructions transmitted in ISO 20022 envelopes. Banks face work beyond changing message formats: customer records, payment systems and screening processes must handle address components accurately from the point where payment details first enter the system.
Swift has deferred the payments changes in its Standards Release 2026, withdrawing a November 14, 2026 deadline that would have required the rejection of cross-border payment messages carrying unstructured postal addresses. The August 27 decision gives banks more time to change how they capture and transmit address data, but leaves the revised payment deadline unresolved.
The distinction matters because adopting an ISO 20022 message format has not necessarily meant adopting structured data inside it. Swift’s 2026 monitoring found that 61.2% of debtor addresses and 62.9% of creditor addresses still arrived as unstructured text lines. That was the case even though more than 98% of cross-border instructions successfully transmitted in ISO 20022 message envelopes.
Deadlines diverge across payment systems
Swift’s decision was followed by changes to other payment-system schedules. The Bank of England postponed its November 2026 RTGS standards release governing CHAPS, while Federal Reserve Financial Services rescheduled the corresponding Fedwire Funds Service release to November 2027. On September 10, the European Payments Council delayed November 2026 enforcement of its plan to phase out unstructured postal addresses across all five SEPA payment scheme rulebooks.
The timetable is not uniform. The Swiss payment market infrastructure operated by SIX retained its November 14, 2026 structured address enforcement deadline, diverging from the other postponements. Banks handling payments across these systems therefore face different implementation schedules rather than a single revised date.
Swift confirmed on September 21 that non-payment changes covering securities, trade and MT messages other than Category 1 would move to June 12, 2027. That date does not settle the timetable for payment-related structured address mandates: Swift said a revised schedule would be determined following industry consultations by December 2026.
Why an ISO 20022 message can still contain a flat address
Swift retired the legacy MT103 and MT202 core payment instruction formats on November 22, 2025, moving production cross-border volume to ISO 20022 pacs.008 and pacs.009 messages on FINplus. But changing the format used to transmit an instruction did not, by itself, restructure the underlying customer and counterparty records.
Many commercial banks met the 2025 transition by using edge translation middleware to wrap existing flat-format messages in XML, the structured format used for ISO 20022 messages. Their internal ledgers and downstream payment engines could continue to work with address data held as undivided lines. This helps explain why a payment can pass through an ISO 20022 channel while its postal address remains unstructured.
The problem extends beyond banks’ message gateways. Enterprise resource planning platforms, including those from SAP and Oracle, and core banking systems have historically stored counterparty addresses in three or four flat lines. Separating a town, country, street or building number into distinct ISO 20022 fields can require changes to those underlying records and the systems that use them. Moving text into an XML message is not the same as verifying which part of the text belongs in each field.
Address quality starts before the payment reaches Swift
Payments Market Practice Group guidance sets out how address information should be represented. Under PMPG-020 and PMPG-040, a hybrid address must place the town name in <TwnNm> and the country in <Ctry>, without repeating those values in free-text <AdrLine> fields. Hybrid formatting therefore retains some free text but still requires two reliably identified address components.
Incorrectly dividing an existing address can create another problem. Automated parsing scripts may put a street name into the wrong XML element, such as <StrtNm> or <BldgNb>, causing a transaction to fail or be rejected. Screening systems calibrated for the flat free-text fields used in older MT messages can also generate false-positive anti-money-laundering or sanctions alerts when processing unstructured XML address lines.
PMPG-050 moves address validation upstream to the initial customer-channel point of entry, with the aim of avoiding repairs by intermediary banks later in the payment chain. That approach places greater importance on the information collected before an instruction reaches the cross-border network, rather than relying on translation or correction during processing.
The readiness gap was visible before Swift’s deferral. RedCompass Labs surveys reported that 44% of global banks were behind schedule and that 20% of Tier-1 banks, defined in the research as holding more than $250 billion in assets, had warned the original timeline was technically unachievable. The postponement changes the deadline, not the underlying need to identify and validate address components. Banks now await Swift’s revised payment timetable while accounting for the November 2026 deadline still in place in Switzerland.
Revolut’s expansion into UK consumer lending is facing closer regulatory scrutiny. The Financial Times reported on October 27, 2026, that the Bank of England’s Prudential Regulation Authority had ordered a Section 166 skilled-person review of the bank’s product approval processes and internal risk governance. The review comes as Revolut offers unsecured personal loans and prepares to introduce a domestic credit card, with mortgages planned later. Revolut UK CEO Francesca Carlesi has said the bank intends to package and sell loans through securitisation rather than retain substantial long-term credit exposure. Revolut is targeting a loan-to-deposit ratio of roughly 6%, far below the roughly 100% typical of incumbent British high-street banks. The strategy could support lending growth while limiting loans held on its balance sheet, but it does not eliminate credit risk. S&P Global has cited the possibility of higher credit losses as Revolut expands lending across multiple jurisdictions.
Sumitomo Mitsui Banking Corporation (SMBC) and Ant International signed a memorandum of understanding on October 26, 2026, to explore cross-border payments and digital treasury services. Their initial focus is Japan, Singapore and wider Southeast Asia. Engineering teams will examine whether Ant International’s Whale RTP platform can be integrated with SMBC’s institutional transaction banking and digital asset platforms. The agreement is exploratory, not the launch of a live settlement service. SMBC’s multi-market transaction banking rails are expected to support operations involving Ant International’s Alipay+, Antom and WorldFirst businesses. Ant International says its Whale platform processed more than US$600 billion in global treasury flows in 2025, with over 95% of transactions settling on the same day. Those figures describe the existing platform, not activity under the SMBC agreement. The MoU follows separate tokenized-deposit work involving Ant International and other banks, including a live OCBC solution and an HSBC pilot.
Tech Mahindra and Finastra announced on October 23, 2026, that Tech Mahindra had completed its acquisition of Finastra’s cash management products and related intellectual property. The deal moves Tech Mahindra beyond implementing banking software for clients and into owning transaction banking products. Financial terms were not disclosed. The acquired portfolio includes Fusion Cash Management, Fusion Virtual Accounts and Fusion Liquidity Management, along with CashPlus, Global CashPlus and associated transaction banking APIs. Finastra product engineering and customer success personnel are being moved into Tech Mahindra’s banking, financial services and insurance division. Tech Mahindra plans to integrate the products into its existing Finastra Centre of Excellence to maintain service continuity for banking clients. The acquisition follows Tech Mahindra’s earlier purchase of an 85% stake in Canadian fintech Avant Techno Solutions and comes as Finastra divests businesses to concentrate on lending and payments software.
The European Payments Council implemented Version 1.1 of its Verification of Payee scheme rulebook on September 20, 2026, clarifying operations, API specifications and security after feedback from live deployment. Its directory service, operated with SWIFT, has also completed a live transition supporting provider reachability and routing. The changes come as non-eurozone EU payment providers work toward a July 9, 2027, compliance deadline. Required under the EU Instant Payments Regulation for both instant and standard SEPA credit transfers, Verification of Payee checks recipient details before authorization and must be offered free to users. The inter-provider exchange has a five-second operational maximum and can return a match, close match, no match or verification-not-possible result. A close match supplies the verified recipient name for the payer to review. A warning does not necessarily prevent a transfer: liability depends on whether a payer proceeds despite it or a provider fails to perform a required check.
Fireblocks has rejected an Axios report that Visa was in advanced talks to acquire the digital-asset infrastructure company for about $2.5 billion. Fireblocks said the reported discussions were not taking place at present. Visa declined to comment on the claim, while Coinbase separately denied reports that it was considering a bid. None of the companies has confirmed an acquisition process. The reported price would be about 69% below Fireblocks’ $8 billion valuation from its January 2022 Series E funding round. The company generated $124 million in revenue in 2024 but remained unprofitable, and it has initiated plans to cut 60 to 70 jobs amid the rumors. Visa already uses Fireblocks as an institutional client and works with it on an interoperability initiative. Those existing links provide context for the speculation, but do not establish that a transaction is under discussion.
TerraPay and J.P. Morgan have connected TerraPay Verify with Kinexys Liink so participating financial institutions can check recipient details before sending cross-border payments to mobile money wallets or bank accounts. Announced on October 22, 2026, the integration allows Liink participants to configure bi-directional API queries with TerraPay Verify. It extends a validation network that already covers account details in more than 70 countries to wallet-related checks. The partnership targets a source of payment failures: a 2026 LexisNexis Risk Solutions study cited during the rollout attributed 10% to 15% of cross-border payment failures to incorrect recipient or beneficiary details. Wallet identifiers can differ from conventional bank-account formats, making early checks useful but not a guarantee that a payment will complete. The companies have not publicly disclosed commercial terms, query pricing or country-by-country rollout plans, and the available information does not establish how much the integration will reduce failures in practice.