Stablecoin payments in 2026 rarely move on a single rail. A customer pays from a Coinbase account in ETH, the merchant settles in USDC on Stellar, and the value crosses chains, tokens, and custodians in seconds. The layer that decides which rails to use, in what order, is what the industry has started calling stablecoin orchestration. This piece walks through what orchestration means, the three sub-layers that compose it, and the projects building in each one.
What stablecoin orchestration means
Stablecoin orchestration is the layer above wallets, exchanges, and chains that takes a payment intent ("merchant wants $1,000 in USDC on Solana") and routes it through whichever combination of source asset, settlement chain, and transport mechanism best fits cost, latency, and reach. It is plumbing, not a stablecoin itself. The category exists because stablecoin liquidity is now fragmented across at least a dozen tokens and twenty-plus chains.
The three sub-layers of orchestration
Orchestration in 2026 is not one product. It is three structurally distinct jobs, often handled by different vendors and stitched together at integration time. Most production payment stacks now touch all three.
Source aggregation: connecting the customer's wallet or exchange account and pulling the source asset.
Settlement routing: choosing the stablecoin and chain the merchant actually receives.
Cross-chain transport: moving value between chains when the source and settlement chain differ.
Source aggregation: networks like Mesh
Source aggregation is the front door. The customer arrives holding something (BTC in a Coinbase account, ETH in MetaMask, USDT on Tron) and the orchestration layer has to authenticate, fetch balances, and initiate the transfer without the merchant integrating each wallet or exchange individually.
Mesh (meshpay.com) is the most visible example of this layer. Per Mesh's public material, the network connects 300+ wallets and exchanges through a single integration, supports 120+ tokens across 24+ chains, and lets the merchant settle in USDC, PYUSD, USDT, RLUSD, or local fiat. Mesh's branded pattern for this, SmartFunding, decouples the customer's source asset from the merchant's settlement asset so a Coinbase user paying in BTC can settle the merchant in USDC without the merchant ever holding BTC.
Peer projects working the same source-aggregation layer in different shapes include Coinbase Commerce (Coinbase-side connect), BitPay (broad wallet support, multi-coin), and the wallet-connect rails used by Stripe's crypto checkout and PayPal Crypto. Each makes different tradeoffs about which wallets and exchanges are first-class versus pass-through.
Settlement routing: chain and stablecoin selection
Once the source side is solved, the orchestration layer has to pick the merchant's settlement chain and stablecoin. The choice is rarely arbitrary. Ethereum mainnet carries deep USDC and USDT liquidity but per-transaction gas in the dollars range. Solana and Stellar offer sub-cent fees and sub-5-second finality, with smaller (though growing) stablecoin float. Tron carries the largest USDT supply by some measures. New payments-purpose L1s like Tempo, which Mesh announced a formal partnership with in May 2026 per the PRNewswire release, are being positioned specifically as settlement venues for payment networks.
Settlement routing logic typically weighs:
Fee on the destination chain at current gas/load.
Stablecoin the merchant has elected to hold (USDC, PYUSD, USDT, RLUSD, or a regional stablecoin).
Finality requirements (a coffee shop tolerates different settlement windows than a B2B invoice).
The merchant's downstream off-ramp, since settlement chain often dictates which fiat off-ramp partners are available.
Most payment networks today expose this as merchant configuration ("settle me in USDC on Solana") rather than per-transaction logic, but the dynamic version is what the orchestration framing points toward.
Cross-chain transport: moving value between chains
When the source chain and the settlement chain differ, something has to move value across. This is the transport layer, and it is the most architecturally diverse of the three.
The major mechanisms in production in 2026:
CCTP (Circle's Cross-Chain Transfer Protocol): burns native USDC on the source chain and mints native USDC on the destination chain. Covered in detail in our CCTP explainer.
LayerZero: a messaging layer that token issuers use to build OFT-style cross-chain tokens.
Hyperlane: a permissionless interoperability framework with modular security.
Intent routers: a newer category where the user expresses an intent ("I want USDC on Base") and solvers compete to fulfill it, often by fronting liquidity on the destination chain. Eco Routes is one example of this pattern; others include Across and the broader solver-based bridge ecosystem covered in our bridge stack overview.
Orchestration platforms typically don't pick one transport. They pick whichever fits the route. A USDC-to-USDC hop between two supported chains often goes via CCTP because it preserves native issuance. A path that requires a token swap mid-route may go through an intent router so the solver handles the swap and the bridge in one step.
How do the three layers compose in a real payment?
Consider a concrete flow. A travel platform sells a $1,200 hotel booking. The customer pays from a Coinbase account holding ETH. The travel platform's treasury holds USDC on Stellar (per Mesh's May 2026 Stellar integration announcement, Stellar is a supported settlement chain).
Source aggregation: Mesh's connect flow authenticates the customer's Coinbase account, fetches the ETH balance, and initiates a transfer of $1,200 worth of ETH out of Coinbase.
Settlement routing: the platform's merchant config says "settle in USDC on Stellar." The orchestration layer converts ETH to USDC at the source side (Coinbase liquidity or an integrated venue) and prepares to deliver USDC to a Stellar address.
Cross-chain transport: if conversion already produced USDC on a CCTP-supported chain, the orchestrator can burn there and mint on Stellar once Stellar CCTP is live; otherwise the path may go via an alternative bridge or via Stellar's anchor-based issuance, depending on what Mesh's integration documents specifically.
The merchant sees one line item: $1,200 USDC arrived on Stellar. The three layers each did their job, and the orchestrator hid the seams.
Major projects per orchestration layer
The table below is structural, not a ranking. Each project below was chosen for the layer where it is most active per its own public material. Some span layers.
Layer | Project | What it does at this layer |
Source aggregation | Mesh | Connects 300+ wallets and exchanges, source-asset decoupled from settlement (per Mesh's public material) |
Source aggregation | Coinbase Commerce | Coinbase-native checkout, multi-asset accept |
Source aggregation | BitPay | Broad wallet support, multi-coin acceptance |
Settlement routing | Bridge (Stripe) | Stablecoin issuance and settlement API, merchant-side stablecoin handling |
Settlement routing | BVNK | Stablecoin-to-fiat settlement, merchant treasury |
Settlement routing | Circle Mint / Web3 Services | USDC issuance and programmable wallets across chains |
Cross-chain transport | CCTP (Circle) | Native USDC burn/mint across supported chains |
Cross-chain transport | LayerZero | Messaging layer for cross-chain tokens |
Cross-chain transport | Hyperlane | Permissionless interoperability with modular security |
Cross-chain transport | Eco Routes | Intent-router pattern where solvers fulfill cross-chain payment intents |
Why is orchestration a 2026 category?
Three things converged. First, stablecoin float crossed a threshold where chain choice meaningfully affects unit economics, not just developer preference. Second, payment-network funding rounds in 2025 and 2026 (Mesh's $75M Series C at a $1B valuation per the PRNewswire release, Bridge's acquisition by Stripe, BVNK's growth) put real product budget into the category. Third, the GENIUS Act created a clearer US regulatory perimeter for payment stablecoins, which gave enterprise merchants the cover to treat stablecoin settlement as a primary rail rather than an experiment.
The result is that a 2026 stablecoin payment stack is rarely one vendor end-to-end. It is a source-aggregation network plus a settlement-routing layer plus a transport mechanism, glued together with API calls. Orchestration is the framing for designing that glue intentionally rather than ad hoc.
What's still maturing
Dynamic per-transaction routing (choosing chain and stablecoin at payment time based on live fees and liquidity) is mostly aspirational in 2026. Most networks expose merchant-level configuration, not per-payment optimization. CCTP coverage is expanding but not universal across the chains payment networks support. Solver-based intent routing works well on common pairs but has thinner liquidity on long-tail routes.
The direction of travel is toward less merchant configuration and more orchestrator-side decisioning, but the production reality today is a stack of vendor choices made once at integration.
Related reading
Methodology and sources
Primary sources: Mesh public material at meshpay.com, the PRNewswire Series C release ($75M at $1B valuation, 2026), the May 2026 Mesh + Stellar integration release, and the May 2026 Mesh + Tempo partnership release. Secondary sources: Circle public documentation for CCTP and USDC mechanics, Stellar Development Foundation documentation at stellar.org for anchor and pathfinding mechanics, LayerZero and Hyperlane public documentation for transport mechanics, and Eco Routes public material for intent-router mechanics. Where a claim originates with a project's own marketing, it is attributed (for example, "per Mesh's public material") rather than restated as independent fact. No third-party performance benchmarks are cited.