XRP community researcher “SMQKE” has uncovered what they describe as direct evidence from Ripple’s and R3 Corda’s codebases, confirming XRP’s compatibility with ISO 20022.
The post also emphasized XRP’s potential to integrate seamlessly with the SWIFT network.
Notably, in the screenshot from RippleNet’s JSON schema, the term “ISO20022 ExternalClearingSystemIdentificationCode List” is explicitly referenced under the “externalClearingSystem” definition.
SMQKE interpreted this as confirmation that Ripple’s architecture aligns with ISO 20022 standards, the global messaging format that governs financial data exchange across SWIFT and other major payment systems.
The prevailing view is that by structuring its schema around ISO 20022 identifiers, Ripple sets XRP up for regulatory and technical compatibility with banks and financial institutions already transitioning to this new messaging standard.
Significantly, Ripple is among the first crypto firms to claim alignment with ISO 20022. XRP proponents often use this connection to suggest that XRP itself is part of the standard. However, this view is widely debated.
Despite counterstatements from Ripple’s CTO, David Schwartz, the debate has not subsided, and proponents like SMQKE continue to advance this narrative.
“XRP has nothing to do with ISO 20022.”
ISO 20022 is a messaging standard for payments, XRP is a cryptocurrency. While there could certainly be projects using both of these things, there is no real inherent overlap between them. 8/13— David ‘JoelKatz’ Schwartz (@JoelKatz) April 8, 2023
XRP and SWIFT Services Imported in R3 Corda Code
Meanwhile, SMQKE’s post also included a second image from R3 Corda’s codebase, revealing imports for both XRP and SWIFT services within the same module. Lines of code clearly show imports for:
- XrpPayment
- XrpSettlement
- SWIFTService
- SWIFTPaymentStatusType
According to SMQKE, this integration suggests that XRP and SWIFT-based operations can coexist within the same enterprise blockchain infrastructure. However, some in the XRP community disagree. They stress that XRP aims to replace legacy systems like SWIFT rather than coexist with them.
In the tweet, SMQKE emphasized that this supposed technical alignment enables Ripple and the XRP Ledger (XRPL) to host seamless settlement capabilities for SWIFT-enabled institutions, potentially leading to broader institutional adoption.
Clarifications about the XRP Appearance in the Codebases
While speculation around XRP’s ISO 20022 readiness and its use in R3 Corda for settlement has circulated for years, proponents frequently point to these direct code references as concrete proof.
However, critics note that these codes stem from an initial proof of concept involving XRP. The full integration never materialized and even led to legal complications between R3 Corda and Ripple.
The persistence of this debate, despite clarifications, shows the enthusiasm within parts of the XRP community to promote a promising future for the asset. Still, even some community members have grown indifferent, arguing that ISO 20022 compliance—assuming it even exists—is not particularly extraordinary or meaningful.
What exactly is your point? Being “ISO20022”-compliant is not that of a big deal tbh. At the end, you just have to support that message format.
— Sabr (@_lonedd) May 6, 2025
Leave a Reply