The debate over which token belongs in a “new financial system” usually begins in the wrong place.
Supporters point to transaction speed, low fees, enterprise partnerships or compatibility with financial messaging standards. Banks and payment companies face a more difficult question: How would the asset fit into their treasury operations without introducing unacceptable liquidity, accounting and compliance risks?
That is the practical test for XRP, XLM, XDC, HBAR, ALGO, VeChain and any other network seeking a role in institutional payments. A token may move quickly across its native ledger, but the institution still has to acquire it, control it, value it, transfer it and convert it into the currency required by the recipient.
Those steps are not secondary details. They are the payment product.
For US banks and cross-border payment providers, the deciding factor will not be whether a blockchain can transmit value in seconds. It will be whether the entire process can operate predictably inside existing balance-sheet, risk and regulatory constraints.
Fast settlement can create a faster funding obligation
A conventional cross-border payment may involve several institutions, internal ledgers and currency accounts. Token-based settlement proposes to compress parts of that process by moving value over a shared network.
That compression can be useful, but it changes the timing of the funding requirement.
If an institution must purchase a token immediately before sending a payment, it needs reliable access to liquidity in the required size. If the recipient does not want to hold that token, someone must also provide an immediate exit into dollars or another destination currency.
The relevant metric is therefore not the token’s headline trading volume. Treasury teams need to know whether executable liquidity is available in the specific corridors, venues and time windows they use.
Questions include:
- How much can be bought or sold without materially moving the market? - Is liquidity available outside US business hours? - Which regulated entities provide access? - What happens if one exchange, broker or market maker becomes unavailable? - How long can the institution safely hold the token? - Who absorbs losses if its value changes during the transaction? - Can a payment be rerouted without breaking reconciliation?
A network can settle quickly while the surrounding liquidity process remains slow, fragmented or expensive. In that case, the token has accelerated one step without improving the end-to-end payment.
Banks need a balance-sheet case, not a standards label
ISO 20022 is relevant to how financial institutions structure and exchange payment information. It does not, by itself, determine which asset settles a transaction.
That distinction matters because messaging and settlement solve different problems. A bank can use standardized messages while settling through accounts, central-bank money, commercial-bank money, stablecoins, tokenized deposits or another permitted instrument.
For a public token to become part of that stack, it needs a defensible balance-sheet role.
A bank considering direct exposure would have to determine how the asset is classified internally, which entity may hold it, how positions are valued and what limits apply. It would also need procedures for custody, key management, transaction approval and exception handling.
An alternative structure could keep the token off the bank’s balance sheet. A liquidity provider might acquire and dispose of it during the transfer while the bank interacts only with fiat-denominated obligations. That can reduce direct exposure, but it does not eliminate counterparty or execution risk. It moves those risks to another part of the chain.
The useful question is not whether a token is “ISO 20022 compliant.” It is whether a complete transaction can use standardized payment data while meeting the institution’s settlement, control and accounting requirements.
The treasury model needs to work under stress
Any payment rail looks more efficient when all of its components are available. Institutional adoption depends on what happens when they are not.
A credible treasury model should define failure procedures before meaningful volume moves through the network. If token liquidity disappears in one corridor, the payment provider needs to know whether it will delay the transfer, quote a wider price, use another venue or return to a conventional rail.
It also needs limits.
A provider could cap the amount sent in each transaction, restrict certain corridors or require minimum liquidity across multiple venues. It could maintain prefunded fiat accounts as a fallback, although that would weaken the argument that the token removes the need for trapped liquidity. It could use more than one settlement asset, which improves resilience but adds operational complexity.
These trade-offs should be measured rather than hidden behind broad claims about efficiency.
Useful performance indicators would include:
- Total cost from payer initiation to recipient availability - Average and worst-case conversion spreads - Failed or delayed transaction rates - Time spent holding the settlement asset - Liquidity available during stressed conditions - Frequency of manual intervention - Reconciliation breaks across counterparties - Dependence on any single custodian, venue or market maker
Those figures would reveal more about institutional readiness than token price performance or transaction speed in isolation.
Bank adoption may not translate into token demand
Even if a bank uses infrastructure connected to a public network, the economic effect on its native token may be limited.
The institution might use software associated with a network while settling in fiat. It might rely on a service provider that holds a token only for seconds. It could use a private or permissioned environment without creating substantial activity on the public ledger.
Investors should therefore separate several different claims:
1. A bank is testing blockchain software. 2. A payment provider is connected to a network. 3. A token is technically available as a settlement option. 4. Customers are using that option in production. 5. The resulting activity creates sustained demand for the token.
These are not interchangeable milestones.
The gap is especially important when evaluating XRP, XLM, XDC, HBAR, ALGO and VeChain. Placing several assets under a broad “banking coin” or “ISO 20022 coin” label does not establish that they have the same architecture, legal treatment, liquidity or commercial use.
Each network needs to be evaluated through its actual transaction design. Who holds the asset? For how long? On which venues? Under whose compliance program? What does the recipient receive? How is the transfer reversed or corrected if payment information is wrong?
Without clear answers, the adoption thesis remains incomplete.
Small businesses should focus on the service contract
Most US small businesses will not integrate directly with a public blockchain to handle overseas payments. They are more likely to encounter tokenized settlement through a bank, payment processor, software platform or specialist provider.
That means the business decision should focus on the service rather than the token narrative.
A customer should ask whether the provider guarantees the exchange rate, discloses all fees and specifies when funds become available. The contract should explain which party is responsible for screening, failed transfers, refunds and disputes. It should also clarify whether the customer ever takes possession of a digital asset.
The best outcome may be invisible infrastructure: the business sends dollars, the recipient receives the expected currency, and the provider chooses the settlement route. If a token reduces the provider’s cost or funding burden, competition may eventually pass some of that benefit to customers.
But a faster internal rail does not guarantee a cheaper customer payment. Providers can retain savings, charge for convenience or incur new costs in liquidity and compliance. Businesses should compare the final price and reliability against existing options.
Settlement evidence matters more than affiliation
A serious payment-token thesis needs more than technical compatibility or an institutional logo. It needs evidence that value is moving through a repeatable operating model.
That evidence should show where liquidity comes from, how long exposure lasts, what controls govern transactions and whether the model remains economical at larger volumes. It should also distinguish a production payment from a pilot, integration or software relationship.
For US financial institutions, tokenized settlement will compete with other payment technologies, not with an imaginary system that never changes. The relevant benchmark is the best available regulated service on cost, speed, availability and risk.
XRP, XLM, XDC, HBAR, ALGO and VeChain may each be evaluated for roles in that environment. None earns institutional relevance merely by being fast, enterprise-oriented or associated with modern payment messaging.
The grounded takeaway is straightforward: before treating any payment token as part of a new financial system, look for the treasury model. If the liquidity, balance-sheet treatment, controls and fallback procedures are missing, the settlement story is still a proposal—not financial infrastructure.