SWIFT is officially tightening the screw on ISO 20022 implementation, sunsetting the legacy messaging standard of CBPR+. On Friday afternoon, SWIFT’s community channel posted a message on X, warning that non-compliant banking institutions could be discontinued.
A Banking Upgrade XRP’s Bulls Have Been Waiting For
On November 14, 2026, CBPR+ messages will reject or delay those using fully unstructured postal addresses. No doubt, SWIFT is highlighting the need for early preparation: the attached video presents a simple, yet vivid example of how the legacy payment rejection works in practice.
The revamped gold standard drives evolution that’s particularly favorable for DLT-based chains like Ripple’s XRP & Hedera Hashgraph (HBAR). From SWIFT’s perspective, the urge to roll-out instant settlement options is a part of the job, meeting “G20 goals of improving data quality and transparency in cross‑border payments”.
With CBPR+ messaging no longer applicable, ISO 20022 could easily turn to the XRP-based RippleNet. The San Francisco tech giant’s native payments network has built-in compatibility with SWIFT’s ISO 20022. This way, banks can send & receive structured data without arduous conversions.
XRP vs. HBAR: Two SWIFT Darlings With Different Roles
RippleNet’s roster of partners now exceeds 300 banks & payment service providers, with many of them intertwined with SWIFT’s New Payments Scheme program, piloting beyond 30 banks this June. That being said, the dual edge Ripple’s XRP chain for SWIFT adoption revolves around On-Demand Liquidity (ODL).
Through ODL, XRP chain provides instant liquidity for cross-border transfers without pre-funding nostro accounts. ISO 20022 dramatically improves compliance screening, transparency and straight-through processing rather than waiting a couple of business days. With low-cost & immediate processing, XRP coin is bound to shine as a complement to SWIFT.
As for Hedera Hashgraph (HBAR), the purpose is different: HBAR Network’s unique positioning is suitable for logging ISO-related messages on-chain, a vast ecosystem of Real-World Assets (RWAs) & enterprise-level tokenization. In a nutshell, HBAR excels where structured data meets complex enterprise needs that are way more beyond pure payment maintenance.
This way, Hedera’s HBAR may be more suitable for a part of SWIFT-compliant banks – those who are looking for a broad spectrum of features rather than just payment digitization. While Ripple’s XRP chain has proven itself in processing billions of dollars in the cross-border field, Hedera’s HBAR has less payments-specific traction that’s evident in high RWA figures.
Delve into DailyCoin’s popular crypto news right now:
AI Crypto Tokens Slide Just as ETF Door Opens for Institutions
Kentucky Sues Polymarket and Kalshi, Challenging Trump-Era Crypto Policy
People Also Ask:
SWIFT announced that from November 2026, banks must use better-structured data in cross-border payments. Payments with messy or incomplete address information will risk being rejected or delayed. This is part of the global shift to ISO 20022 — a newer, smarter messaging standard.
Traditional banks are upgrading their systems to ISO 20022. Crypto projects that can work smoothly with this new standard have a better chance of being used by banks for real payments. It’s about making crypto more “bank-friendly.”
XRP (and the XRP Ledger) was built specifically for fast, cheap cross-border payments. Ripple has long worked with banks and already supports ISO 20022 standards. Many in the XRP community see this SWIFT update as another step toward real-world adoption of XRP for international transfers.
HBAR (Hedera) focuses heavily on enterprise use cases and data integrity. Hedera is also ISO 20022 compatible and has been pushing for adoption in regulated environments. Supporters believe HBAR’s strong governance and enterprise focus could help it win business from traditional finance as standards improve.
