SMQKE’s recent post takes a different approach from the usual discussions around XRP’s role in global payments by centering entirely on technical documentation.
Instead of relying on assumptions or speculations, the researcher directs attention to specific code references from RippleNet and R3 Corda.
These materials form the basis of the argument that XRP-related systems are positioned to operate within ISO 20022 and SWIFT-aligned environments. The post encourages readers to review the data directly, making the conversation more grounded in what is observable within the files.
For anyone who wants to see the actual code linking XRP to ISO 20022 and SWIFT, here’s direct proof:
• Image 1 shows RippleNet’s Payment schema referencing the "ISO 20022 ExternalClearingSystemIdentificationCode List". ✅
This confirms XRP’s infrastructure is built on ISO… pic.twitter.com/cBQrCCqdni
— SMQKE (@SMQKEDQG) November 22, 2025
RippleNet’s ISO 20022-based payment schema
The first image shared focuses on a JSON schema from RippleNet’s Payment Object. Inside this structure, the schema explicitly references the “ISO 20022 ExternalClearingSystemIdentificationCode List.” This reference sits within RippleNet’s messaging architecture, which outlines how payment information is formatted and identified within its system.
SMQKE interprets this as confirmation that RippleNet’s design directly incorporates ISO 20022 standards. Since ISO 20022 is required for institutions interacting with SWIFT’s updated messaging framework, the schema indicates RippleNet is structured to be compatible with those requirements.
Corda modules combining XRP and SWIFT functionality
The second image comes from R3 Corda’s codebase. The list of imported modules includes components such as “XrpPayment,” “XrpSettlement,” “SWIFTPaymentStatusType,” and “SWIFTService.” SMQKE highlights this combination to show that Corda can handle XRP-linked actions and SWIFT-related messaging within the same system.
In this context, XRP becomes operable through a platform that already aligns with ISO 20022 standards. The implication is that enterprise environments using Corda are technically able to run payment and settlement processes involving XRP while remaining integrated with SWIFT-compatible architectures.
The relevance of ISO 20022 alignment
SMQKE states that any organization or token intending to operate in a SWIFT-connected environment must align with ISO 20022. According to the post, the two images demonstrate that RippleNet and Corda already operate at that standard, making XRP compatible within those systems.
We are on X, follow us to connect with us :- @TimesTabloid1
— TimesTabloid (@TimesTabloid1) June 15, 2025
The point made is not about theoretical capability but what the underlying code shows: that ISO 20022 compliance exists at the infrastructure level, enabling XRP to function within those rails when transmitted through those compliant environments.
Clarification from the Community Response
X user Lion of Kishnar added further context beneath the post. They noted that RippleNet and Corda may be ISO compliant, but the XRP Ledger itself is not. Their view is that XRP does not need to be ISO 20022 compliant as an asset to be sent through a compliant system. They further explained that the images confirm exactly this distinction.
The post shared by SMQKE relies on specific technical files to outline how RippleNet and Corda integrate ISO 20022 and SWIFT-aligned functions while supporting XRP-related operations. The follow-up comments from Lion of Kishnar introduce a clear distinction between platform compliance and asset compliance, offering readers a fuller picture of how the technology fits together.
Disclaimer: This content is meant to inform and should not be considered financial advice. The views expressed in this article may include the author’s personal opinions and do not represent Times Tabloid’s opinion. Readers are advised to conduct thorough research before making any investment decisions. Any action taken by the reader is strictly at their own risk. Times Tabloid is not responsible for any financial losses.
Follow us on X, Facebook, Telegram, and Google News
