Global stablecoin transaction volume hit $33 trillion in 2025, larger than global credit card volume. The institutions moving most of it aren't betting on a single asset. They're operating across RLUSD, USDC, USDT, EURC,, and local-currency stablecoins simultaneously, because different corridors, counterparties, and regulatory environments call for different assets. The question for payments infrastructure teams is no longer whether the market will pluralise. It already has. The question is whether your infrastructure keeps up.
The GENIUS Act, signed into law in July 2025, did something more consequential than define reserve requirements and audit schedules. It started a clock. Institutions that committed to stablecoin settlement infrastructure before the law passed were early movers. Institutions committing now are on schedule. Institutions that delay into 2026 and 2027 will be implementing under competitive pressure, with peers already live, volumes already consolidated, and counterparty relationships already formed around assets and platforms that they chose.
The switching cost argument is well understood. What is less discussed is the opportunity cost of waiting. $33 trillion in stablecoin transaction volume in 2025 is not a forecast, it is settled activity. That volume is flowing through platforms that are live today. The institutions capturing it made infrastructure decisions. The institutions watching it did not.
In fact, Ripple is already powering a significant portion of these stablecoin transaction, cross-border payments at scale across 60+ markets and $100B+ in volume. Firsthand, we're seeing that the institutions capturing stablecoin volume mde infrastructure decisions
The window for deliberate infrastructure selection, as opposed to reactive infrastructure adoption, is narrowing. What gets decided now, which platform, which architecture, which settlement model will go on to define institutional payments operations for the next several years. That context matters when evaluating what kind of platform to build on.
The market is already multi-stablecoin. Infrastructure that doesn't reflect this is behind.
This is the structural reality that single-asset payments platforms are not built to address: the global stablecoin market did not converge on one token. It pluralised. And the pluralisation is not theoretical or future-tense, it is visible in live payment flows right now.
An institution doing cross-border settlement across three regions is already in a world where the settlement asset varies by market. A platform that can only process one of these is not a global payments platform.
The pluralisation is happening on the counterparty side as well. Enterprise buyers increasingly have their own stablecoin preferences, shaped by their custody provider, their banking relationships, and the regulatory frameworks they operate under. A payments platform that settles only in USDC is not interoperable with counterparties who prefer or are required to use a different asset. That is not a feature gap. It is a structural incompatibility that compounds with every new corridor and every new counterparty relationship.
Regulatory differentiation is accelerating this. MiCA in Europe does not treat all stablecoins equally. Institutions with European operations may be required to settle certain transactions in a MiCA-compliant asset. A single-asset platform cannot serve that requirement without adding assets, and adding assets to an architecture that was not designed for it is not the same as building on an architecture that was designed for it from the start.
The market has already made the multi-stablecoin decision. The question is whether payments infrastructure reflects the market or lags it.
What single-issuer dependency actually costs
For institutions evaluating stablecoin settlement infrastructure, the single-issuer question tends to surface as a risk management point. It should also surface as a market access question and a counterparty alignment question, and in that order.
- Your counterparties are already multi-stablecoin: If your platform settles in one asset and your counterparties operate in others, you are not serving the full scope of what they need. As stablecoin adoption deepens across emerging markets, financial institutions, and enterprise buyers, the range of assets in active use will expand, not contract. Infrastructure built around a single issuer's token is infrastructure built for a narrower version of the market than the one that will exist in two years.
- Counterparty concentration is a risk category treasury teams understand well: A single stablecoin issuer changing its fee structure, reserve composition, or redemption mechanics, or facing a liquidity event or regulatory action, leaves an institution with no alternative settlement rail. That is a single-counterparty dependency that would trigger a risk review in any other context. The fact that it is framed as 'stablecoin infrastructure' does not change the underlying exposure.
- Regulatory fragility is the third dimension, and in cross-border contexts it compounds: A stablecoin issuer's operating licence is jurisdiction-specific. An institution running APAC, LatAm, and EMEA corridors through a single stablecoin is exposed to regulatory shifts in any of those markets that could affect the issuer's ability to operate or redeem. As global stablecoin regulation matures, and it is maturing faster than most infrastructure procurement cycles, the jurisdictional exposure of a single-asset architecture will only become more visible.
- What asset-agnostic payments infrastructure actually means in practice: Asset-agnostic is a design principle, not a feature list. It means the settlement layer is decoupled from any single issuer's token. The platform can settle across USDC, USDT, RLUSD, and fiat simultaneously, not because it is trying to be everything, but because that is what institutional payments infrastructure across 60-plus live markets actually requires.
Ripple's payments solution is built on this principle. It processes cross-border settlement across multiple stablecoins and fiat rails, with managed custody, liquidity, and conversion built into the one stop shop platform, so institutions are not stitching together five vendors to handle what should be a single payment flow. The platform supports multiple stablecoins — including USDC, USDT, and RLUSD — reflecting how cross-border payments already operate across markets, with architecture designed to integrate additional assets as corridors and requirements evolve.
The proof that this works in practice is live across multiple institutions. AMINA Bank, a FINMA-regulated Swiss crypto bank, became the first European bank to adopt Ripple Payments, using Ripple's infrastructure to power near real-time cross-border flows for its institutional and crypto-native clients, bridging stablecoin and fiat rails simultaneously.
The reason matters as much as the outcome. As AMINA Bank's Chief Product Officer put it: "Our clients need payment infrastructure that can handle both fiat and stablecoin rails simultaneously, but traditional correspondent banking networks weren't designed to support this." That is not a future requirement. It is a current operational reality for a FINMA-regulated institution managing clients whose world is already multi-stablecoin. The platform has to match where those clients are, which means settling across RLUSD, USDC, USDT, and fiat without requiring the bank to choose one.
This is not an isolated case. Ripple’s Payments solution is already in production across global financial institutions and payment providers, supporting live cross-border flows across fiat and stablecoin rails. This is not a future state, it is how payments are already operating today.
RLUSD the Institutional Stablecoin
Ripple built RLUSD to be the best regulated stablecoin available for institutional use cases. The platform was built so that institutions do not have to use it.
Ripple's stablecoin business is subject to the highest oversight as a trust company at both the state and federal levels— offering a dual layer of regulation and compliance that few issuers can claim. AMINA Bank was the first bank globally to support RLUSD, offering custody and trading services to its clients, a choice driven by RLUSD's regulatory profile, not by platform lock-in. In APAC, SBI Holdings selected RLUSD for Japan distribution for the same reason: an asset that meets institutional due diligence requirements in a region where compliance credentials matter at least as much as settlement speed.
Infrastructural Decisions to Consider
Two questions frame the evaluation well, one defensive, one aspirational, and both worth asking before selecting a platform.
The defensive version: what happens to your payments operations if your regulatory environment changes around the stablecoin your platform is built on? This is the risk management version of the multi-stablecoin argument, and it is the version that tends to surface in audit conversations and vendor due diligence. It is a valid question.
The proactive version for infrastructure planning: which corridors, counterparties, and use cases will your payments infrastructure be able to serve in 2027 that it cannot serve today, if it is built around a single asset? This is the market access version. It asks not what breaks, but what is left on the table.
The institutions that will win in cross-border payments over the next three years are not the ones that chose the right stablecoin. They are the ones that chose infrastructure capable of settling in whatever asset the market, the corridor, and the counterparty require, at the moment they require it, without pre-funding, and without rebuilding the stack when the market moves.
The market has already moved. The institutions that win won’t be the ones that chose the right stablecoin. They’ll be the ones that chose infrastructure already operating at scale across assets, rails, and markets, without needing to rebuild as the ecosystem evolves.
