ISO 20022 is often presented in crypto markets as a bridge between bank modernization and a select group of tokens. That framing skips the most important question: What, exactly, would the token do?
A bank can adopt a common messaging format without using a public blockchain. It can test distributed-ledger infrastructure without holding a volatile network asset. It can also settle a tokenized obligation without giving the underlying token a meaningful role in liquidity, collateral or balance-sheet management.
Those distinctions matter for XRP, XLM, XDC, HBAR, ALGO, VeChain and every other asset marketed around the “new financial system.” Compatibility with financial messaging is not the same as adoption by financial institutions. Nor does compatibility establish that a token is required for settlement.
The latest source set offers no new bank announcement, production transaction data or regulatory action establishing a fresh adoption milestone for those assets. That absence should not be filled with inference. For US investors and businesses, the practical task is to separate three layers that crypto promotion routinely compresses into one: messages, ledgers and settlement assets.
ISO 20022 standardizes information, not economic value
Payment systems need structured instructions. A transfer message may identify the sender, recipient, institutions involved, purpose of payment and other information needed for processing or compliance.
ISO 20022 provides a common framework for such financial messages. That can improve the quality and consistency of information moving among institutions. It does not, by itself, dictate whether final settlement occurs through commercial-bank deposits, central-bank money, a stablecoin, a tokenized deposit or a crypto asset.
This is the first test for any ISO 20022 token claim: Is the project participating in the message flow, the settlement flow, or both?
A system might translate standardized bank messages into instructions for a blockchain application. That would demonstrate integration at the messaging layer. It would not necessarily create demand for the network’s native asset beyond whatever amount is needed to pay transaction fees.
Likewise, a bank could use software associated with a crypto company while avoiding the company’s affiliated token. Vendor adoption and asset adoption are separate events.
The distinction is easy to lose because “payments” can refer to several different activities:
- Creating and transmitting payment instructions - Screening a transaction for compliance - Converting between currencies - Providing liquidity during the transfer - Recording changes in ownership - Reconciling records among institutions - Achieving final settlement
A token thesis becomes materially stronger only when the token has a specified role in one or more of those functions—and when that role is documented in a live system rather than inferred from technical compatibility.
A ledger can be useful without its public token becoming bank money
The Ethereum Foundation recently argued that governments and institutions need shared, neutral digital infrastructure outside the control of a single centralized actor. That is a broad infrastructure case, not proof that any institution will use a particular public token for settlement.
Still, it highlights a genuine design question. Banks exploring tokenized finance must decide who controls the ledger, who can validate transactions, who can reverse errors and which law governs the resulting obligations.
A public network offers one possible answer. A permissioned network offers another. Institutions may also combine components, using public infrastructure for verification while keeping regulated liabilities and sensitive transaction details within controlled systems.
None of those architectures automatically requires banks to hold the native asset as working capital.
For XRP, XLM, XDC, HBAR, ALGO and VeChain, investors should therefore ask two separate questions:
1. Is the network or related software being used? 2. Is the publicly traded token necessary to the production workflow?
The first can be true while the second remains unresolved.
Transaction fees alone do not settle the issue. A network can process substantial activity while requiring only limited token inventory if fees are low and tokens can be replenished quickly. A stronger demand mechanism would require evidence that participants must hold the asset for liquidity, collateral, security, governance or another persistent operational purpose.
Without that evidence, an infrastructure announcement should not automatically be converted into a valuation claim.
Cross-border payments raise the bar
Cross-border settlement is a popular use case because the current process can involve multiple institutions, currencies and compliance regimes. But that complexity also makes bank adoption harder than a simple demonstration suggests.
A production system must address more than transaction speed. Banks need to know how liquidity will be sourced, how exchange-rate exposure will be managed and what happens when one side of a transfer fails. They need procedures for sanctions screening, fraud investigations, mistaken payments and disputes.
They also need legal clarity about the asset being transferred. A token moving between wallets may represent a bank liability, a claim on a reserve pool, a security, a commodity-like crypto asset or something else. Those categories create different capital, custody and compliance consequences.
For US institutions, the important evidence would include a named banking function, a defined regulatory perimeter and a clear description of the settlement asset. Investors should look for answers to practical questions:
- Does the institution hold the token, or does a service provider handle it? - Is the token used only momentarily, or maintained as inventory? - Who supplies liquidity in each currency corridor? - Is the system live with customers or confined to a pilot? - How are failed and disputed transfers handled? - What entity owes the recipient money if the platform becomes unavailable? - Does finality on the ledger also constitute legal finality?
A press release that does not answer those questions may still describe legitimate experimentation. It just does not establish durable token demand.
Retail interest is not institutional settlement evidence
A Bitcoin Policy Institute study covered by CoinDesk reportedly suggests that everyday Americans respond to themes such as control and micro-investing. That may help explain how digital assets are presented to consumers, but retail preferences should not be confused with bank infrastructure requirements.
Consumers can favor access, small purchases and direct control while banks prioritize legal certainty, predictable liquidity and operational recovery. A product can satisfy one audience without satisfying the other.
This difference is especially important when “new financial system” narratives combine consumer ownership, cross-border payments and institutional tokenization into a single trade. Those markets may share technology, but they do not share identical buyers, risks or adoption timelines.
A consumer-facing wallet integration, for example, is not evidence that banks are settling their own obligations with the wallet’s supported assets. Similarly, the availability of a token on a payment interface does not show that merchants receive it or that financial institutions use it between themselves.
Build a settlement map before accepting the narrative
Investors and businesses assessing payment-focused altcoins should diagram the transaction rather than start with the ticker.
Identify the payer’s asset, the recipient’s asset and every intermediary obligation created between them. Then mark where conversion occurs, which party provides liquidity and what asset extinguishes the debt at final settlement.
That map exposes whether a public token is central, incidental or absent.
It also makes competing networks easier to evaluate without treating them as one category. XRP, XLM, XDC, HBAR, ALGO and VeChain can have different architectures and target markets. A claim involving one network does not validate the others merely because all appear on an “ISO 20022” list.
The evidence threshold should remain straightforward: standardized messages prove standardized communication. A ledger integration proves some use of a ledger. Only documented production flows can show whether a particular token is necessary to settlement and whether that use creates persistent economic demand.
Until those flows are visible, ISO 20022 is best understood as part of the financial plumbing—not an institutional endorsement of any crypto asset.