Former SWIFT Exec Denies Reports of XRP Integration

Ex-SWIFT innovation chief refutes XRP integration claims

Tom Zschach, SWIFT's former Chief Innovation Officer, has publicly denied recent social media reports suggesting that the global financial messaging network plans to integrate or directly support the XRP token. The statements, which circulated widely on X and other platforms, implied that SWIFT would adopt a public cryptocurrency rather than stick to bank-issued digital liabilities. Zschach called those reports 'not happening' and emphasized that the project's public materials do not name XRP as a settling asset.

What SWIFT's blockchain project actually targets

SWIFT is building a shared ledger designed to enable faster, 24/7 cross-border payments by tokenizing commercial bank deposits and linking payment flows between institutions. The organization confirmed in March that it completed the design phase and began developing a minimum viable product (MVP), with ambitions to process real transactions in 2026. Official statements have consistently described the initiative as focused on regulated bank liabilities and interoperability with legacy messaging, not on adopting a specific public cryptocurrency like XRP.

Tokenized bank deposits, not public crypto

The project's core use case is to connect tokenized versions of bank deposits—regulated, on-ledger representations of existing bank liabilities—so banks can settle payments more quickly and around the clock. That approach underlines SWIFT's emphasis on working within regulated frameworks, where settlement assets are likely to be bank-issued and supervised, rather than volatile public tokens. This distinction weakens claims that SWIFT has chosen XRP for direct integration.

Why the rumor gained traction

The latest speculation followed SWIFT's announcement of a pilot involving 17 financial institutions testing blockchain-based cross-border flows. Several participating banks—such as Standard Chartered and UBS—have existing commercial ties with Ripple or use services that interface with the XRP Ledger. Market observers interpreted those overlapping relationships as potential evidence that SWIFT might adopt XRP, which briefly pushed up XRP prices on some exchanges.

Partnerships don't equal protocol adoption

However, Zschach and other informed observers stressed that banks often maintain multiple vendor relationships and participate simultaneously in competing pilots. A bank's partnership with Ripple does not automatically translate into the SWIFT network incorporating XRP. Pilot participation enables banks to test different settlement mechanics and rails, but it doesn't constitute an endorsement of a single public token for all network settlement needs.

Zschach's consistent skepticism about public tokens

During his tenure at SWIFT, Zschach repeatedly questioned whether banks would willingly rely on volatile public tokens for settlement. He has publicly doubted narratives that expect Ripple and XRP to replace established financial infrastructure wholesale. In the recent exchange on X, he even used an AI assistant to check whether SWIFT currently uses XRP—underscoring his view that the social posts lacked a factual basis and official confirmation.

Ripple's evolving strategy: connection over replacement

Ripple historically positioned its network as a faster alternative to SWIFT, with XRP offered as a bridge asset for on-demand liquidity. More recently, Ripple has pivoted toward integration and interoperability: offering custody solutions, stablecoins such as RLUSD, and regulated payment rails that can connect to existing banking systems. That strategic shift increases the potential for collaboration between Ripple-linked services and traditional infrastructures, but it does not automatically create demand for XRP within third-party platforms such as SWIFT.

XRP's role versus other settlement options

XRP can still function as an optional bridge asset inside some Ripple products, but Ripple's technology also supports stablecoins and bank-backed digital liabilities for settlement. The flexibility means that, even if banks use Ripple-associated services, they could choose settlement using RLUSD or tokenized deposits rather than XRP itself. SWIFT's stated focus on regulated bank liabilities aligns with that broader market trajectory toward safer, supervised settlement assets.

Previous unconfirmed claims and market impact

Earlier social-media-driven reports suggested SWIFT was testing public tokens such as XRP and HBAR. Those accounts relied on third-party sources and lacked direct confirmation from SWIFT, leaving the market with uncertainty. While rumors can influence short-term price moves in crypto markets, observers and regulators emphasize the importance of official announcements when evaluating infrastructure-level integrations between institutions and public blockchains.

Bottom line: no confirmed XRP integration

For now, SWIFT's public roadmap centers on a shared ledger for tokenized bank deposits and interbank payment links, not on the adoption of XRP as a network-wide settlement token. Tom Zschach's direct rebuttal of the latest integration claims adds a credible voice to the narrative that the reports were speculative. Banks participating in SWIFT pilots may have existing Ripple relationships, but those ties do not constitute proof that SWIFT is integrating XRP into its core payment infrastructure.