XRP and ISO 20022: what is really behind the compliance claim

No, XRP is not “ISO 20022 compliant”, and for a reason that settles the whole debate: a coin cannot be. ISO 20022 is a format for payment messages between banks and describes how a transfer is written down in technical terms. The standard says nothing about which means of payment moves in the end. Ripple, the company behind XRP, does indeed sit on the body that maintains this standard. That is a membership, not an approval of the token.

There is a second point that hits the widespread expectation even harder: the big migration many investors are waiting for happened long ago and was completed on November 22, 2025. The one deadline still open in 2026 has since been cancelled. Anyone reading today that “ISO 20022 arrives in November and will lift the price” is being given a date that no longer exists in that form. XRP trades at around $1.32 or €1.19 on October 27.

ISO 20022 governs the message, not the means of payment

ISO 20022, often written ISO20022 without a space in search queries and product sheets, is an international standard for data exchange in finance. Put simply, it sets out which fields of a payment message carry which details: originator, beneficiary, amount, currency, remittance information, address data. Before this standard, banks sent their instructions in an older message format called MT, in which many details were crammed into a single text field. ISO 20022 breaks the same information into structured data that software can process automatically.

The benefit lies in what happens next. When the beneficiary address and the remittance information sit in separate, clearly named fields, a bank can screen sanctions lists automatically, allocate payments faster and avoid queries. That is precisely why the industry is pushing the migration forward. The standard describes only the messaging layer, that is, the form of the notification. Which balance moves behind that notification, whether euros in a bank account, dollars at a correspondent bank or a token on a blockchain, ISO 20022 does not govern.

That fixes the decisive distinction for any compliance claim. A messaging standard can be met by software, by a payment system, by a bank. An asset does not meet it, just as a banknote does not meet a file format. Once you have drawn the line between message and value, you read the circulating lists of “ISO 20022 coins” with different eyes.

The coexistence of MT and ISO 20022 ended on November 22, 2025

For cross-border payments over Swift there was a multi-year transition in which both formats were permitted side by side. That coexistence expired on November 22, 2025. Since then ISO 20022 has been the binding format for the Swift messages covered by the CBPR+ programme, short for Cross-Border Payments and Reporting Plus, and the old MT families for customer payments, interbank payments and statements no longer meet the requirements there.

This date is the heart of the misunderstanding. The story that ISO 20022 is about to be introduced and will then pull certain coins upwards describes an event in the future. In fact the most important step is almost a year behind us, and in the days around November 22, 2025 the XRP price showed no special effect that could be traced back to the format change. Banks switched a message format, not a means of payment.

The migration is not finished with that. After the end of coexistence one further obligation remained open, and all the talk about a November 2026 deadline hangs on it.

When ISO 20022 takes effect: the November 14, 2026 deadline has been cancelled

The open obligation concerns postal addresses. Until now addresses could be sent in payment messages in unstructured form, with street, house number, city and country in one block. From a fixed date, only structured or hybrid address fields were to be admissible, with separate fields for house number, street, town and postcode. The date set was November 14, 2026, as part of the so-called Standards Release 2026.

That date no longer exists. At the request of its own user community, Swift conceded that many institutions would not be ready in time and rescheduled the package. The release was split into two parts in the process. The deferred part covering securities, funds, trade finance, treasury and foreign exchange has been moved to June 12, 2027. The changes for payments, that is CBPR+, SCORE+, SwiftGo and MT category 1, were carved out and pushed to a future release whose scope and date are not yet fixed. Standards Release 2025 stays in force until it is replaced.

The postponement also shifted deadlines in other systems. The US payment service Fedwire Funds Service moved its own release from November 2026 to November 2027 after Swift communicated its decision. One point matters for the interpretation: the industry stretched the timetable, it did not change course. The direction towards structured data stands unchanged, and institutions are expected to continue their preparations even without a confirmed date.

So anyone asking when ISO 20022 takes effect gets a three-part answer. For cross-border messaging the standard has applied since November 2025. For structured addresses in payments no date is fixed. For the remaining business areas, June 12, 2027 applies.

The ISO 20022 compliance coin lists and their missing evidence

Lists of coins said to be compliant circulate in forums and on advice sites. XRP is almost always there, usually alongside Stellar, Algorand, XDC Network, Quant, Hedera and IOTA. These lists have no basis in any directory held by the standards organisation. There is no register of vetted cryptocurrencies, no compliance test for tokens and no body that issues such a seal.

What does exist are three weaker statements, fused into one strong statement in the lists. First, a company can be a member of a working group of the standard. Second, payment software can produce and read messages in the ISO 20022 format. Third, a network can be built in a way that lets it process such messages. None of those statements concerns the properties of a token, and none is a certification. It is revealing who is missing from these lists: Bitcoin never appears, although Bitcoin also moves value across borders. The difference lies solely in the fact that the listed projects have companies behind them that address banks.

So it pays to look at the evidence behind such a claim. Anyone asserting compliance would have to name who certified it, for which product and under which test procedure. All three details are missing from the circulating coin lists. Critics in the crypto community have pointed this out for years, and so have analysts and trade publications from the payments industry. The debate is therefore less contested than a search engine's result list suggests.

Ripple sits on the standards body, the XRP token is not approved there

The hard fact behind the story sits on Ripple's own page, and it is more precise than the retellings of it. Ripple stated that it is part of the Registration Management Group of the ISO 20022 standards body and the first member there with a focus on distributed ledger technology, or DLT for short. The company also describes its corporate network RippleNet as aligned with ISO 20022 from the outset. You can read that in the company's own statement.

Three things stand out about it. The membership concerns Ripple, the company, not the XRP token, and it relates to RippleNet, the product for banks and payment service providers, not to the public XRP Ledger. And the wording is “aligned with”, not “certified to”. At this point Ripple itself claims less than the lists that cite Ripple.

Membership of a working group is still not nothing. The company gets a say in developing the standard, and the seat shows that the payments industry treats blockchain providers as interlocutors. For the question of whether the XRP token carries a seal of approval, it has no bearing. Apply the same logic to other members and you see it at once: banks and software houses sit on that same body, and nobody infers a jump in their share price from it.

What XRP is used for: bridge currency and the Interledger Protocol

The factual role of XRP lies one layer below the message format. XRP is intended as a bridge currency. To move from one currency into another without holding a separate funding account for every currency pair, you can route through a common intermediate value. That is exactly the design: payment in currency A into XRP, XRP into currency B, settled within seconds on the XRP Ledger. The advantage would be tied-up liquidity that is freed.

Alongside it stands the Interledger Protocol, ILP for short, which comes from the same environment. ILP describes how payments are passed on across different payment systems, much as data packets travel across different networks on the internet. Here too the subject is interoperability between systems, and here too the question of the message format is separate from it.

That allows the relationship between the two worlds to be stated cleanly. ISO 20022 governs how one bank tells another that an amount should flow. XRP would be a means by which that amount actually changes hands. A value transfer needs both, and neither replaces the other. Compatibility arises where software connects both ends, and that is a provider's work, not a property of a token.

For getting started with XRP in practice, other things decide the outcome anyway. Which venues list XRP in euros, what deposits and withdrawals cost and whether a provider holds a licence for the European market can be looked up in the crypto exchange comparison. Those points have a measurable effect on the result of a purchase; the state of a messaging standard does not.

The real November 2026 deadline concerns German DTAZV files and corporate clients

There is a genuine deadline in November 2026, only it has nothing to do with crypto. In Germany, banks will stop accepting classic DTAZV files from that month, that is the old file format for foreign payments, and will require ISO 20022 in its 2019 version instead. For SEPA payments the format versions pain.001.001.09 for credit transfers and pain.008.001.08 for direct debits are added.

Those affected are corporate clients and their accounting systems, especially users of large enterprise resource planning systems. Fail to convert your file formats in time and you risk rejected payment instructions. That is a serious deadline, but one for finance departments, not for holders of coins.

This confusion explains part of the muddle. Several migrations carry the same standard name with different dates: the end of coexistence in November 2025, the deferred address obligation with no date, June 12, 2027 for other business areas, and November 2026 for German foreign payment files. Pick up one of those dates and place it in a price context, and you turn a genuine deadline into a false expectation.

What a real Swift connection looks like, shown by the Chainlink case

For comparison it helps to look at a case where a connection between blockchain and the banking world is actually documented. The Swift ledger project with Chainlink is about a concrete technical connection with named institutions, which we reported on at the end of September: 11,500 institutions on the Swift ledger, with an attributed statement from Chainlink's chief. There you have a project, participants and a description of what is being connected.

Every claim about a banking connection can be measured against that yardstick. A real connection has a name, a set of participants and a status. Membership of a standards body does not, and a mention in a coin list certainly does not. The difference is not academic, because it decides whether a headline has a process behind it or an attribution.

How to check a compliance claim in three steps

The ISO 20022 question keeps coming back in many variants, and it comes up with other standards and partnerships just the same. Three checks are usually enough to separate a solid statement from an attribution.

First the source. Does the claim appear with the organisation that administers the standard, or with the company itself, or only on an advice page that points to another advice page? If the trail runs in a circle after two clicks, there is no primary source.

Then the subject. Is this about a company, about a product of that company, or about the token? Those three are regularly mixed up in headlines, although they are legally and technically separate. Ripple's statement is a good example, because it names its own subject clearly while the retellings shift it.

Last, the evidence of the test. A certification has an issuing body, a scope and a date. If one of those is missing, there is no certification, only a self-description. The same grid helps with licences held by trading venues, except that there you can follow it to the end: which providers hold a European authorisation under the MiCA regulation is set out in the overview of regulated crypto exchanges, including the authority that granted it.

The link between a payment standard and the XRP price

That leaves the question behind the whole search: if ISO 20022 is not a price driver, what drives XRP? Here it pays to set two readings side by side rather than assert one.

The confident reading does not rest on the messaging standard but on demand from institutions. If banks and payment service providers deploy Ripple's products and need XRP as an intermediate value for them, demand arises that is independent of speculation. This reading only becomes solid with figures on actual payment volumes, and the company discloses those only in part.

The sceptical reading counters that banks manage cross-border payments without a token too, and have only just lifted their existing correspondent relationships onto the new message format. Precisely because the ISO 20022 migration in messaging is complete, there is no occasion to switch the means of payment on top. This reading is an expectation as well, not a measurement.

What can be documented, by contrast, is the market data of the day. XRP stands at around $1.32 on October 27 and is therefore about two percent above the previous day. We continue tracking these levels and the analyst views on them on the XRP price prediction page, with every price target and source attributed by name. A seal of approval for message formats will not turn up there, because none exists.

XRP and ISO 20022: the message format says nothing about the price

The story of the compliant cryptocurrency sells a seal of approval that no body issues, and a deadline that no longer exists. What remains is a company with a seat on a standards body and a token whose price lives on demand. Three steps follow from that.

1. Check the claim at its source. Before any purchase that rests on a compliance or partnership announcement, look for the primary source and the subject. The same check applies to the venue: whether an exchange holds a European authorisation is shown by the overview of regulated crypto exchanges.
2. Compare the costs that actually arise. Trading fee, spread and withdrawal costs bear on every position, independently of standards and deadlines. The providers' terms for XRP in euros are set out in the exchange comparison.
3. Document the holding period from the start. In Germany a gain on cryptocurrencies stays tax free after a holding period of one year; below that, the exemption threshold for private disposals applies. A purchase receipt with a date is the basis for this, and the tools for it are covered by the comparison of tax tools and portfolio trackers.

(As of October 27, 2026. This article is not investment advice. Prices and fee structures change; check the terms with the provider before you buy.)