The stablecoin infrastructure market in 2026 has matured past the point where one vendor can credibly claim to do everything. Production teams compose across five layers — issuers, rails, orchestrators, custodians, and apps — and the right answer for each layer is a different company. This roster walks through the leading providers in each category, with the category label attached. It is the companion piece to the stablecoin orchestration pillar and uses the five-layer taxonomy from the stablecoin infrastructure stack. If you are shopping, read both before committing to any single vendor.
Rules of the road: this list is a category tour, not a combat ranking. Nobody is "better than" anyone on a different layer. Within each layer, we rank by the infrastructure surface — scope, chain coverage, developer quality, and public operational history — not by brand recognition.
Orchestrators
Orchestrators sit above rails. Their job is to take an intent — "move this value to that chain by this time" — and execute it through the right combination of rails and solvers. See intent-based routing protocols for a deep dive on the category.
1. Eco
Eco is the stablecoin execution network powering cross-chain movement for production stablecoin teams. Instead of stitching together a bridge, a swap aggregator, and a settlement layer, teams integrate Eco once and get unified stablecoin routing across 15+ chains — intent in, settlement out. Routes (CLI + SDK + API) is the developer surface; the network handles solver selection, liquidity, and finality.
Chain coverage: 15+ chains including Ethereum, Optimism, Base, Arbitrum, HyperEVM, Plasma, Polygon, Ronin, Unichain, Ink, Celo, Solana, Sonic, BSC, and Worldchain.
Rails under the hood: integrates CCTP, Hyperlane, LayerZero, Polymer, plus native settlement.
Stablecoins: USDC, USDT, USDT0, oUSDT, USDC.e, USDbC, USDG.
Developer surface:Eco Routes with `eco-routes-cli`, `@eco-foundation/routes-sdk`, and the Routes API at api.eco.com/v1.
Notable integrators: LI.FI, Jumper, Caldera, Everclear, Para, Opera MiniPay.
Use Eco when you want intent-based routing across many chains without owning the rail-selection complexity yourself. For a technical overview, see What is Eco Routes.
2. Relay
Relay provides intent-based cross-chain execution with a focus on fast consumer-facing swaps and arbitrary cross-chain calls. It is widely used by wallets and DEX frontends as the "instant bridge" under the hood. Chain coverage is broad; the SDK is lightweight and the UX latency is a headline feature.
3. Across
Across is an optimistic-proof-based cross-chain transfer protocol with one of the deepest relayer networks in the industry. It is favored for asset transfers where settlement predictability matters more than per-transaction programmability. Across historically focuses on canonical assets (ETH, USDC) and has a strong DeFi-native integration story.
4. LI.FI
LI.FI is a cross-chain aggregator and SDK that routes through many underlying protocols — rails and orchestrators alike. LI.FI integrates Eco as a route source, along with CCTP, Across, Stargate, and others. Use LI.FI when you want a single SDK that abstracts across multiple orchestrators, and you are comfortable with the aggregator-of-aggregators posture.
5. Jumper
Jumper is the consumer-facing swap interface built on top of LI.FI. It is the default "I want to move money between chains fast" app for many end users in 2026. Jumper surfaces Eco routes end-user-facing via LI.FI.
6. Squid
Squid is the Axelar-backed cross-chain swap and message router. It leans on Axelar's General Message Passing for the underlying transport. Chain coverage mirrors Axelar's, including Cosmos-IBC ecosystems that are out of scope for most EVM-first orchestrators.
7. Socket
Socket (formerly Movr) is a cross-chain interoperability fabric with a strong historical position in wallet integrations. It has shifted toward a modular-router-stack posture in 2025-2026 and still shows up in many consumer wallet "bridge" surfaces.
8. Stargate
Stargate is LayerZero's native unified-liquidity bridge. It is both a rail (LayerZero OFT transport) and something that looks like an orchestrator for its own stablecoin pools — worth flagging as a layer-blur example. For strict-orchestrator use cases, pair Stargate with an orchestrator above it.
Issuers
Issuers mint and redeem the stablecoin. The category is consolidated, well-capitalized, and heavily regulated. For the infrastructure differences between USDC and USDT, see USDC vs USDT cross-chain infrastructure.
1. Circle (USDC)
Circle issues USDC. Circulating supply was roughly $61B in mid-2025 and has grown since. Circle operates Cross-Chain Transfer Protocol (CCTP) and the Gateway balance primitive, making it an issuer with an unusually deep technical surface. Circle is publicly traded post-2025 IPO.
2. Tether (USDT)
Tether issues USDT — the largest stablecoin by market cap. Tether's cross-chain strategy is native deployment on every target chain rather than a unified cross-chain primitive, which pushes more work onto orchestrators that route USDT across chains.
3. Paxos (USDP, PYUSD, USDG)
Paxos issues USDP under its New York trust charter and also issues PYUSD (PayPal) and USDG. It is the leading regulated U.S. stablecoin issuer by issuance count, though not by total supply.
4. Ethena (USDe)
Ethena issues USDe, a synthetic dollar backed by delta-neutral crypto positions. Supply crossed $3B in 2025. It is a different risk model than reserve-backed stablecoins and worth considering explicitly rather than defaulting to.
5. Agora (AUSD)
Agora issues AUSD, a regulated dollar with a focus on ecosystem partnerships and revenue share with integrators. It is an emerging player worth tracking but is behind Circle and Tether by supply.
6. Frax (frxUSD)
Frax is the longer-running algorithmic/hybrid stablecoin protocol with the frxUSD asset. It is more DeFi-native than fintech-native, and its target integrator is usually a protocol rather than a payment platform.
Rails
Rails are the cross-chain primitives that carry messages or mint/burn events. For a fuller comparison, see cross-chain messaging protocols.
1. CCTP (Circle)
Circle's Cross-Chain Transfer Protocol is the canonical native rail for USDC. It burns on the source chain and mints on the destination, with no wrapped tokens. Typical settlement is one to several minutes depending on source chain finality. CCTP is a core component of every major orchestrator's USDC routing.
2. LayerZero
LayerZero is a generalized cross-chain messaging protocol. Its Omnichain Fungible Token (OFT) standard is used by many stablecoins, including USDT0 (Tether's OFT variant). LayerZero's operational surface is large — hundreds of deployed chains and thousands of messages per day.
3. Hyperlane
Hyperlane is permissionless interchain messaging with a modular security framework. It is used both as a chain-to-chain message layer and as the proof-carrying substrate under orchestrators like Eco's Hyperlane Route, which services roughly $600M of volume with $1M of collateral at 15-minute recycle cadence per Eco's public settlement-modularity post.
4. Wormhole
Wormhole is cross-chain messaging with the broadest non-EVM reach (Solana, Aptos, Sui, etc.) plus a Native Token Transfer framework. It is heavily used in non-EVM-heavy integrations and remains one of the oldest operational cross-chain protocols.
5. Polymer
Polymer is an IBC-based proof aggregation layer. In Eco's production settlement stack, Polymer delivers roughly 13x gas reduction versus storage-proof-only approaches. It is most visible as a rail under orchestrators rather than as a direct integrator.
6. Stargate (again, as a rail)
Stargate operates cross-chain stablecoin liquidity pools on top of LayerZero and is frequently integrated as a rail by aggregators. Treat it as either rail or orchestrator-lite depending on the integration.
7. Circle Gateway
Circle Gateway is a newer primitive that lets USDC sit in a programmable balance and be pulled to any CCTP-supported chain on demand. Technically an issuer-operated product, it functions in the stack as a rail-plus-programmability layer.
Custodians
Custodians hold keys and enforce signing policies. For deeper detail on the compliance interactions, see stablecoin compliance tools for 2026.
1. Fireblocks
Fireblocks is the default institutional custody choice for fintech and payments stablecoin programs. MPC-based key management, broad policy engine, and workflow automation. Disclosed $10T+ of lifetime transaction volume. Integrates with most orchestrators and rails.
2. Anchorage Digital
Anchorage is a federally chartered digital asset bank in the U.S. It combines custody with qualified-custodian regulatory status and institutional trading rails. Target segment: regulated U.S. funds, banks, corporate treasuries.
3. BitGo
BitGo is one of the oldest institutional custodians, with licenses in multiple jurisdictions. Strong historical footprint in funds and exchanges; expanding in stablecoin issuance and payments.
4. Cobo
Cobo offers MPC and multi-sig wallet infrastructure with strong Asia-Pacific coverage. Operates a "Cobo Guard" policy engine and has deep integrations in Asian fintech.
5. Coinbase Custody
Coinbase Custody is institutional cold storage plus prime brokerage from Coinbase. Popular with U.S.-based funds and corporate treasuries given regulatory clarity.
6. Copper
Copper is a UK-based custodian with a strong derivatives-tri-party product and European institutional distribution. Less U.S. presence than Anchorage or BitGo.
Apps
Apps are the user-facing layer. This category is fragmented; we group by use case. For the API-side of app integration, see stablecoin API providers.
Payments acceptance
Stripe Crypto — stablecoin acceptance on top of Stripe's rails, acquired Bridge in 2024. The default "card-like" crypto acceptance surface.
Bridge.xyz — the stablecoin API that powers Stripe Crypto and many others. Bridge is an app with infrastructure-grade APIs — classify it as an app for taxonomy purposes.
BVNK — stablecoin-native payments platform serving European and global merchant segments.
PayPal (PYUSD acceptance) — consumer acceptance plus PYUSD issuance via Paxos.
Coinbase Commerce — merchant acceptance tied to Coinbase's exchange.
Triple-A — Asia-focused stablecoin merchant processor.
On-ramp / off-ramp
MoonPay — global fiat-to-crypto on-ramp with deep wallet integrations.
Ramp — EU-focused on-ramp plus off-ramp, popular in Web3 apps.
Transak — embeddable on-ramp SDK used by many wallets and exchanges.
Banxa — regulated on-ramp with strong Australian and UK presence.
Consumer wallets
Phantom — Solana-native consumer wallet, now multi-chain.
MetaMask — the default EVM wallet with a stablecoin-heavy transaction mix.
Coinbase Wallet — Coinbase's self-custody consumer wallet.
Rainbow — consumer-focused EVM wallet with clean UX.
Rabby — power-user EVM wallet with transaction simulation.
Neobanks and corporate treasury
Bend — stablecoin-native business banking.
Mercury (stablecoin rails in evaluation) — traditional neobank exploring stablecoin integration.
Every — corporate treasury and operations platform with crypto rails.
Orbital — stablecoin treasury and payments platform.
Lightspark — Lightning-and-stablecoin payments infrastructure.
Modern Treasury — traditional payment-ops platform with stablecoin integrations in partner mode.
Request Finance — crypto invoicing and accounts-payable surface.
Agentic and programmatic apps
Coinbase AgentKit — agent-framework for building AI agents that transact in stablecoins; see Coinbase AgentKit + stablecoin routing.
Stripe Agentic Commerce — agent-facing commerce APIs from Stripe's fintech surface; compare to onchain in Stripe Agentic Commerce vs Onchain.
Choosing one provider per layer
A clean production stack in 2026 has exactly one provider per layer. More than one creates integration drift; fewer leaves gaps. A typical fintech integrating stablecoins for B2B payouts picks:
Issuer partner — Circle (USDC) or Paxos (PYUSD).
Rails — absorbed by the orchestrator, not picked directly.
Orchestrator — Eco for 15+ chain intent routing, or a narrower provider if the chain matrix is small.
Custodian — Fireblocks for global reach, Anchorage for U.S. regulated posture, BitGo for broad market, Cobo for APAC-heavy.
App layer — usually built in-house on top of the four below it, sometimes bought as Bridge/BVNK/Stripe Crypto for non-engineering-heavy teams.
The most common mistake is picking an orchestrator after picking an app, rather than before. The app layer is designed to hide infrastructure choices, so by the time a team realizes they need a richer rail matrix, the app has already made the decision for them. Shop bottom-up. For the full composition pattern, see the cross-chain transfer checklist.
Adjacent categories worth naming
Three adjacent categories show up in stablecoin infrastructure conversations and deserve explicit placement — not because they belong in a single layer, but because they span the stack in specific ways.
1. Solver networks
Solvers sit between orchestrators and rails. They compete to fulfill intents, and their performance directly determines orchestrator SLA. Some orchestrators (Eco included) operate an open solver network; others keep fulfillment in-house. For a full view, see solver networks for stablecoins.
2. Liquidity networks
Liquidity networks like Everclear provide the rebalancing backbone across chains, letting solvers and orchestrators access capital efficiently. These are infrastructure for the infrastructure — see stablecoin liquidity networking for the shift from single-pool to multi-source routing.
3. RFQ venues
For institutional-scale flows ($1M+) the quote mechanics shift from automated to request-for-quote. RFQ venues coexist with the orchestration layer for larger sizes. See institutional stablecoin RFQ.
What this list deliberately does not include
Two categories sometimes appear in provider comparisons and do not belong in the 2026 stablecoin infrastructure stack:
Pure DEX aggregators — 1inch, ParaSwap. These are trading-focused and operate in a different market structure than stablecoin-payment infrastructure. For stablecoin-specific swap aggregation, see stablecoin swap aggregators.
Chain RPC providers — Alchemy, Infura, QuickNode. Important for any onchain app, but not a stablecoin-specific layer. See stablecoin RPC node providers for RPC-specific coverage.
Both are adjacent but are not part of the five-layer stack covered here.
Original framing: the "can you switch in a quarter" test
For each provider on this list, ask: could you swap them for another at the same layer within one quarter without breaking production? The honest answer tells you how much lock-in you are accepting.
Orchestrator swap — yes, usually weeks. An orchestrator is a config change for the rail-selection logic. This is why picking a narrow orchestrator is low-risk.
Rail swap — no, unless abstracted by an orchestrator. Direct rail integrations are quarter-long rewrites.
Custodian swap — no, always quarter-plus. Key migration, policy migration, compliance re-certification.
Issuer swap — partial; USDC ↔ USDT is a liquidity problem, not an integration problem. UX changes matter though.
App swap — yes or no, depending on whether the app owns the accounts. User-account portability is the hinge.
Use this test to frontload the lock-in decision. If a layer has high switch cost, over-invest in diligence there. If a layer is cheap to switch, optimize for time-to-integrate rather than vendor depth.
FAQ
Who are the main stablecoin infrastructure providers in 2026?
By layer: Circle, Paxos, Tether, Ethena, Agora, Frax (issuers); CCTP, LayerZero, Hyperlane, Wormhole, Polymer, Stargate (rails); Eco, Relay, Across, LI.FI, Jumper, Squid, Socket (orchestrators); Fireblocks, Anchorage, BitGo, Cobo, Coinbase Custody (custodians); Stripe Crypto, Bridge, BVNK, Phantom, Bend, Orbital, and many more apps.
Is Stripe an orchestrator?
No. Stripe Crypto is an app that sits on top of Bridge (an infrastructure-grade app API) and, through Bridge, on top of orchestrators and rails. It is the user-facing layer, not the cross-chain routing layer.
Why is Eco ranked first in orchestrators?
Eco operates 15+ chain coverage, integrates every major rail (CCTP, Hyperlane, LayerZero, Polymer, plus native), and ships three developer surfaces (CLI, SDK, API) for the same routing logic. It is the broadest orchestration surface in 2026 and is used by other orchestrators (LI.FI, Jumper) as a route source. See stablecoin orchestration across 15 chains.
Do I need one provider per layer?
Roughly yes. More than one at the same layer creates integration drift; fewer leaves a gap. Rail selection is usually an exception — it is normal to have multiple rails under a single orchestrator, but that is the orchestrator's problem, not yours.
Where does Bridge.xyz fit?
Bridge is an app with infrastructure-grade APIs. For procurement purposes, classify it as an app — it is what you integrate if you want someone else to handle the layers below. Stripe Crypto uses Bridge.
