--- path: /learn/stablecoin-routing/ title: Stablecoin routing across chains, assets, and payment rails description: Learn how stablecoin routing connects deposits, transfers, and conversions, and how payment teams evaluate coverage, quotes, delivery, and failed payments. image: /og/2026-q4/og_2026-q4_learn_stablecoin-routing_title-f5_v01.png publishDate: 2026-10-26 keywords: stablecoin routing, stablecoin payment routing, cross-chain stablecoin transfers, stablecoin orchestration label: Payments timeToRead: 5 seoTitle: "Stablecoin routing: how payment paths are selected" faq: - question: Is stablecoin routing the same as bridging? answer: No. A bridge handles movement between supported blockchains. Routing coordinates a payment path that may also need asset conversion, deposit handling, delivery tracking, or a separate bank payout. - question: Does a listed route guarantee that a payment can execute? answer: No. Catalog coverage identifies a supported combination. The operation, amount, organization access, current quote, and provider conditions determine whether a particular payment can proceed. - question: Does routing require the platform to hold customer funds? answer: Not necessarily. Custody depends on the wallet, provider, smart contracts, and operating model. Determine who can authorize movement and who controls funds at each step rather than inferring custody from the word routing. locale: en canonical: https://tempo.xyz/learn/stablecoin-routing/ --- # Stablecoin routing across chains, assets, and payment rails _Stablecoin routing coordinates the supported steps between a source balance and a destination. It helps payments teams work across assets and networks while keeping quotes, delivery, and exceptions visible. [Explore Tempo Routes](/routes/) for the supported stablecoin legs in your flow._ A customer holds one stablecoin on one blockchain. Your product accepts another asset on another network. The customer sees a deposit or withdrawal; your business needs a path that connects the two correctly. Routing starts by identifying valid paths. Price matters after eligibility, asset compatibility, and the required destination have been established. ## What is stablecoin routing? Stablecoin routing selects and coordinates a supported path for moving stablecoin value between specified endpoints. A path may include a token conversion, a cross-chain transfer, or a connection to a separate bank payout provider. This differs from card-payment routing, where a system may select an acquiring bank or processor to improve authorization performance. [Stripe's explanation of intelligent payment routing](https://stripe.com/resources/more/intelligent-payment-routing) describes that card-oriented use case. Stablecoin routing must additionally account for the exact token, blockchain, and destination delivery conditions. |Component|Responsibility| |-|-| |Route catalog|Describe supported source and destination combinations and operations| |Quote|Price a particular amount under current terms| |Bridge or transfer provider|Move value between supported networks| |Conversion venue or liquidity provider|Exchange supported assets| |Ramp provider|Connect an eligible stablecoin flow to bank money| |Application|Apply customer policies, maintain payment records, and handle the customer experience| One integration can coordinate several components. It does not make their responsibilities, eligibility rules, or failure modes identical. ## Define the destination before comparing paths Specify the source asset and network, destination asset and network or bank account, payment size, and permitted recipient. Include the exact token contract where applicable, rather than relying on a symbol alone. An invoice requiring pesos in a Mexican bank account has a different completion condition from a transfer requiring a dollar stablecoin in a wallet. Both can use stablecoins, but only the first needs a peso payout. A route that reaches the wallet has not yet paid the invoice. Also specify whether the customer is depositing from outside your application or your application is initiating an outgoing transfer. The available operations can differ even for the same pair of assets. ## Compare valid routes using complete quotes Assess routes against the same amount and destination. The useful comparison includes the amount delivered, separately paid fees, quote expiry, expected timing, and any limits or access conditions. A low-cost route is not useful if it does not support the payment size, the required operation, or the business's organization. An indicative rate is also not the price of an executable payment. [Tempo's quote documentation](/developers/docs/routes/quotes/) distinguishes route coverage from amount-specific pricing. Decide whether your product fixes the amount sent or the amount received. That choice affects who bears changes in fees or conversion. Use only the amount mode that the specific route supports. ## Deposits and outgoing transfers are different workflows With a deposit workflow, a business gives a customer an address for a supported asset and network. Funds arriving there trigger the applicable processing. The application needs to handle unexpected amounts, unsupported assets, and deposits that arrive after a quoted condition changes. With an outgoing transfer, the application reviews the created transfer's terms, then uses the source account's signer to execute the returned calls in order. These can include approvals and require multiple transactions. For Tempo Routes, register the actual source transaction hashes, then track delivery until the transfer is completed and reconcile the destination amount. A quote or successful creation response does not establish payment completion. Tempo documents these workflows separately in its [deposit-address guide](/developers/docs/routes/deposits/) and [transfer guide](/developers/docs/routes/transfers/). Verify the operation exposed by each route rather than assuming every route supports both. ## Track delivery across every step Record the internal payment ID, provider identifiers, and relevant onchain transactions. Keep the source transaction, route execution, and destination delivery distinguishable in your payment records. An onchain confirmation proves the event on that network. A multi-step route may still be processing. If a bank payout follows, its final status is another completion condition. Tempo's [delivery guide](/developers/docs/routes/delivery/) describes how to track the supported Routes workflow. For an ambiguous result, reconcile before retrying. A timeout can mean the application did not receive the response, while the payment still progressed. Retrying through another path before establishing the first payment's state can pay the recipient twice. Refunds also need an explicit flow. A finalized onchain payment is not reversed by resubmitting a request. Any return payment must follow the applicable provider process and authorization. ## Test the paths your customers will actually use Start with one deposit and one withdrawal flow that match real customer balances. Test a normal payment, an expired quote, a payment outside the supported limits, and an uncertain delivery state. Use provider test environments where available and follow their instructions for unsupported deposits rather than sending unsupported assets. Define what your customer sees while a payment is pending and how support locates it. Track completion rate, time to usable funds, effective cost, and manual interventions. This means the integration is judged on what customers experience, not only on whether a route exists. ## Where Tempo Routes fits Tempo Routes connects supported stablecoin deposits and transfers through one integration. Its [current supported-routes table](/developers/docs/routes/networks/) lists the relevant assets, networks, and operations. Access policy and the current quote determine what an organization can execute. Moving funds into an Earn product or Zone after arrival is a separate operation. Currency conversion and bank payouts should only be presented as supported where the required provider, route, and terms have been confirmed. See the [Routes overview](/developers/docs/routes/) for current implementation scope. ## FAQ **Is stablecoin routing the same as bridging?** No. A bridge handles movement between supported blockchains. Routing coordinates a payment path that may also need asset conversion, deposit handling, delivery tracking, or a separate bank payout. **Does a listed route guarantee that a payment can execute?** No. Catalog coverage identifies a supported combination. The operation, amount, organization access, current quote, and provider conditions determine whether a particular payment can proceed. **Does routing require the platform to hold customer funds?** Not necessarily. Custody depends on the wallet, provider, smart contracts, and operating model. Determine who can authorize movement and who controls funds at each step rather than inferring custody from the word routing. [Review the Routes integration guide](/developers/docs/routes/) or [talk with Tempo](/contact/?source_article=/learn/stablecoin-routing/&cta_location=article_footer) about your deposit and withdrawal flows. --- ## Site links - [Tempo home](/) - [Privacy policy](/privacy-policy/) - [LinkedIn](https://www.linkedin.com/company/tempo) - [X](https://x.com/tempo) - [YouTube](https://www.youtube.com/@tempo) ### Products - [Earn](/earn/) - [Routes](/routes/) - [Zones](/zones/) ### Solutions - [Agentic payments](/solutions/agentic-payments/) - [Cross-border payments](/solutions/cross-border-payments/) - [Institutional settlement](/solutions/institutional-settlement/) - [Stablecoin accounts](/solutions/stablecoin-accounts/) - [Tokenized deposits](/solutions/tokenized-deposits/) ### Developers - [Documentation](/developers) - [Tempo Explorer](https://explore.tempo.xyz/) - [Tempo API](/developers/docs/api/) - [Performance](/developers/performance) - [Status](https://status.tempo.xyz/) - [GitHub](https://github.com/tempoxyz) ### Resources - [Blog](/blog/) - [Customers](/customer-stories/) - [Learn](/learn/) - [OUSD](/ousd/) - [Partners](/partners/) - [Reports](/reports/) - [Stablecoin Advisory](/stablecoin-advisory/) ### Company - [About](/about/) - [Careers](/careers/) - [Brand kit](/brand/) - [FAQ](/faq/)