A fresh flare-up over XRP’s oft-repeated “ISO 20022 compliance” claim is forcing a basic but consequential distinction back into view: Ripple, the private company that builds enterprise payment software, is not the XRP Ledger, the open, decentralized network that settles XRP transactions. The latest round was ignited by investor Jake Claver, who asserted that “before any other cryptocurrency, XRP prioritized… ISO 20022 compliance,” adding that “the network processes more than $434 billion in transactions every day,” and casting ISO 20022 as the bridge that will let Ripple “tokenize and transfer massive volumes of assets” across banking rails. Claver’s post went viral. It also drew a categorical rebuttal from Matt Hamilton, Ripple’s former Director of Developer Relations.
That context also explains why Ripple’s corporate announcements reference ISO 20022 at the network-integration layer. Ripple joined the ISO 20022 Registration Management Group in 2020, billing itself as the first DLT-focused participant and positioning RippleNet’s single API and data model to interoperate with banks’ ISO-native flows. None of that turns the asset into an “ISO-compliant coin,” because compliance, in this domain, attaches to message formats, systems integration, and operational processes.
None of this means XRP cannot be used in workflows that originate from ISO 20022-formatted instructions. Hamilton himself has repeatedly said anyone can make payments on the ledger, and that RippleNet can translate ISO 20022 messages into whatever internal calls are needed to orchestrate settlement, including ODL-style flows that source and settle liquidity with the token. What he objects to is the rhetorical shortcut that collapses corporate messaging compliance into token-level attributes, particularly when it is leveraged to imply privileged regulatory status or inevitable valuation upside.
At press time, XRP traded at $3.22.
