Welcome to USD1routing.com

What routing means for USD1 stablecoins

At a minimum, routing answers one question: what sequence of systems will handle the transfer from start to finish? With USD1 stablecoins, that sequence can include on-chain steps (on-chain means recorded on a blockchain, which is a shared digital ledger), off-chain steps (off-chain means recorded in private systems like an exchange database), and hybrid steps (partly on-chain and partly off-chain).

A simple route might be:

• A sender uses a wallet (wallet means software or a device that manages addresses and private keys) to send USD1 stablecoins directly to the recipient on the same blockchain network.

A more complex route might be:

• The sender holds USD1 stablecoins on one network, uses a bridge (a service that moves tokens between networks) to reach the recipient’s preferred network, and then delivers the USD1 stablecoins to the recipient’s wallet address.

Or a route might leave token networks entirely:

• The sender sells USD1 stablecoins for U.S. dollars, sends the dollars through a bank transfer, and the recipient later buys USD1 stablecoins again.

These routes can all achieve a similar human goal, but they are not equivalent. They differ in:

• Finality (when a payment is truly finished and cannot be reversed by normal system rules).
• Credit and counterparty risk (the chance that a company or intermediary fails to deliver what it owes).
• Operational risk (the chance that a mistake in process causes loss or delay).
• Compliance controls (the checks required to meet anti-money-laundering rules and sanctions rules). The Financial Action Task Force (FATF) describes how a risk-based approach should apply to virtual assets and the businesses that service them.^[4]
• Transparency (how much transfer data is publicly visible).
• User experience (how many steps a human or a system must get right).

A helpful way to think about routing is to separate the value from the path. Value is USD1 stablecoins that track U.S. dollars. The path is the route those tokens take to arrive where they need to be, in the form the recipient can use.

A practical routing stack you can reason about

Routing decisions for USD1 stablecoins happen in layers. You do not need to be a developer to use this stack, but the stack is also useful if you are building a product.

Layer 1: Intent and constraints

Start by stating the intent in plain English:

• Who is sending and who is receiving?
• How fast does it need to arrive?
• Is the recipient a person, a merchant, or a business treasury?
• Does the recipient need USD1 stablecoins on a specific network, or do they just want dollar value in any form?

Constraints often decide the route more than best price does. Examples include business policy, local availability of exchanges, or network support by a custodian.

Layer 2: Identity and compliance gating

Many routes involve an intermediary: a wallet provider, exchange, payment processor, broker, or custodian. These are often called VASPs (virtual asset service providers, meaning businesses that handle transfers, custody, or exchange of digital assets). FATF guidance explains that these businesses may have obligations like KYC (know-your-customer identity checks), AML (anti-money-laundering controls), and the Travel Rule (a rule that requires certain identifying information to travel with some transfers).^[4][5]

In routing terms, compliance gating means a route may be fast and cheap but unavailable if the sender or recipient cannot or will not complete required checks.

Layer 3: Custody and wallet model

A custodial wallet (a wallet where a company holds the private keys, meaning the company ultimately controls the funds) can simplify routing because the company can support many networks and handle conversions internally. A non-custodial wallet (a wallet where you control the private keys yourself) can increase direct control but makes routing mistakes easier, because the user must select the correct network and address with fewer guardrails.

Custody also changes the risk profile. Public-sector reports often highlight operational resilience and risk management expectations for stablecoin arrangements and related services.^[2][3]

Layer 4: Network and settlement layer

A blockchain network has its own rules for transaction ordering, confirmation, and fees. This is where you encounter network fees (often called gas fees, meaning the cost paid to process a transaction) and confirmation times (how long it takes for the network to consider the transaction settled). Gas fees are typically paid in a native token (native token means the network’s built-in asset used to pay transaction costs), even when the transfer itself is in USD1 stablecoins.

Some USD1 stablecoins exist on multiple networks. Routing includes choosing the network that both parties can use, and choosing a path if they cannot use the same one.

Layer 5: Liquidity and conversion steps

If the sender and recipient use different networks or different token representations, the route may require conversion. Liquidity (how easily an asset can be exchanged without moving the price much) matters here. Low liquidity can lead to slippage (the gap between the expected and actual price received after fees and market movement).

Conversion steps can include:

• Swapping one token for another using an exchange.
• Using a bridge that locks or burns tokens on one network and mints or releases them on another.
• Using a broker that quotes an all-in price for delivery.

Conversion introduces extra failure points. It can also introduce extra parties that must behave correctly.

Layer 6: Delivery and confirmation

Delivery is the moment the recipient can actually use the funds. That may be:

• A confirmed on-chain transaction to the recipient’s address.
• A credited balance inside a custodial account.
• A bank deposit after a redemption and transfer.

Confirmation is often misunderstood. A transaction can be broadcast (sent to the network) but not confirmed. It can be confirmed but later reorganized (a reorganization is when the network replaces recent history due to consensus rules). Most widely used networks treat deep reorganizations as unlikely, but routing designs should still decide what enough confirmations means for the value and risk level involved.

Layer 7: Records and reconciliation

For individuals, records may simply be receipts. For businesses, reconciliation (matching transactions to invoices, payroll entries, or accounting ledger entries, where a ledger is an organized record of transactions) can become the hardest part of routing. A route that saves a few cents in fees but breaks reconciliation can be a net loss.

This is one reason many policy discussions about cross-border payments emphasize transparency and operational reliability as core outcomes, not just speed.^[1]

Common routes for moving USD1 stablecoins

Below are patterns you will see repeatedly. Think of them as building blocks. Real-world routes are often combinations of these patterns.

Route A: Direct transfer on the same network

This is the simplest route:

1. Sender holds USD1 stablecoins on Network X.
2. Recipient provides an address on Network X.
3. Sender transfers USD1 stablecoins to that address.
4. Recipient waits for confirmations and then uses the funds.

What can go wrong is usually operational: copying the wrong address, selecting the wrong network, or paying too low a network fee so the transaction is slow.

Route B: Transfer inside one custodian, then withdraw

Many people hold USD1 stablecoins inside an exchange or wallet app. In that case, part of the route may happen off-chain:

1. Sender transfers USD1 stablecoins to the recipient inside the same platform (off-chain book entry).
2. Recipient withdraws to their own wallet or to another service on a chosen network.

This can be cheaper and faster than on-chain transfer, but it introduces counterparty dependence on the platform. Public reports frequently highlight that stablecoin arrangements must address governance, risk management, and operational resilience to protect users and the system.^[2][3]

Route C: Cross-network delivery using a bridge

If the sender and recipient use different networks:

1. Sender holds USD1 stablecoins on Network X.
2. Sender uses a bridge to move value to Network Y (the recipient’s network).
3. Sender delivers USD1 stablecoins on Network Y to the recipient’s address.

Bridge design varies. Some bridges rely on smart contracts (smart contracts are self-executing programs on a blockchain). Others rely on custodial or semi-custodial arrangements. Routing analysis should treat bridges as a distinct risk category because their failure modes can be severe.

One additional concept that appears in routing discussions is a wrapped token (wrapped token means a token representation that stands in for an asset held or locked elsewhere). Wrapped representations can be useful, but they also add dependence on the wrapper mechanism and its governance.

Route D: Convert to U.S. dollars and use bank rails

Sometimes the simplest route is not on a blockchain:

1. Sender sells USD1 stablecoins for U.S. dollars through a regulated intermediary.
2. Sender sends U.S. dollars to the recipient by bank transfer.
3. Recipient buys USD1 stablecoins after receiving the funds, if they still want that form.

This route can be slower due to banking hours and correspondent banking (the system where banks rely on partner banks to move funds internationally). But it can offer clearer consumer protections and familiar dispute handling, depending on jurisdiction.

Route E: Merchant payment through a processor

For a merchant, routing can include acceptance layers:

1. Customer sends USD1 stablecoins using a supported wallet or checkout method.
2. A processor verifies receipt, manages confirmations, and may convert into the merchant’s preferred settlement form.
3. Merchant receives funds as USD1 stablecoins or as U.S. dollars.

Processors may implement smart routing (automated selection among supported networks and liquidity providers) to minimize failures and manage fees. For merchants, the key question is not just what did it cost but also did it settle reliably, with records that match orders.

How to judge route quality: cost, speed, and reliability

Routing for USD1 stablecoins often looks like an optimization task. In practice, it is an optimization task with constraints, trade-offs, and risk limits.

Cost: not just fees

Routing costs commonly include:

• Network fees paid to process transactions.
• Service fees charged by exchanges, brokers, processors, or bridges.
• Spread (the gap between a mid-market price and the price you actually get).
• Hidden operational costs such as manual support time when a transfer is delayed.

A route with a low network fee can still be expensive if the conversion step is illiquid. Conversely, a higher network fee can be worth paying if it avoids a fragile bridge or reduces the chance of support tickets.

Speed: confirmation time versus usable time

Speed is not one number. It helps to separate:

• Broadcast time: how long it takes to submit the transaction.
• Confirmation time: how long until the network includes it in a block.
• Finality time: how long until it is extremely unlikely to be reversed.
• Usable time: when the recipient can spend, withdraw, or redeem.

In some routes, the recipient may see the transfer quickly but cannot use it until a compliance review finishes. In others, the on-chain transaction is final but the custodian credits it after internal checks.

Reports on stablecoins and cross-border payments repeatedly emphasize that improving speed should not come at the cost of weakening risk management.^[1]

Reliability: failure modes matter

Reliability is the probability that the transfer will complete successfully without manual intervention. Reliability depends on:

• Network congestion (when many transactions compete for limited capacity).
• Bridge uptime and liquidity.
• The recipient’s ability to accept the specific network token representation.
• Human factors, including confusing user interfaces.

A reliable route is one where what can go wrong is limited and well understood. In policy work, that translates into expectations about governance, clear redemption mechanisms, and strong operational resilience for stablecoin arrangements.^[2][3]

Finality and reversals

Some people approach USD1 stablecoins expecting card-like reversals. Most on-chain transfers are not like card payments. Once a transfer is final on-chain, it is typically irreversible unless the recipient voluntarily returns funds.

That does not mean users have no protections. Protections can exist at other layers: a custodian might freeze suspicious funds, an intermediary might provide dispute programs, or a business might use escrow (escrow is a mechanism where funds are held until conditions are met). But those protections are not inherent to a token transfer.

This is an important routing truth: if reversals are required, you must route through a system that provides them.

Risk and compliance considerations

Routing choices shift risk from one place to another. The goal is not no risk, but risk that is understood, priced, and controlled.

Asset and redemption risk

USD1 stablecoins aim to maintain a stable value relative to the U.S. dollar. That depends on design choices like reserve assets, redemption processes, and governance. Public-sector analysis often treats stablecoin arrangements as needing credible mechanisms to maintain confidence that tokens can be redeemed at par (at par means one token for one dollar).^[6]

Routing cannot fix a poorly designed stablecoin arrangement, but routing can limit exposure. For example, a business might minimize the time it holds USD1 stablecoins by routing quickly into U.S. dollars, reducing the impact of a loss of confidence event.

Counterparty risk and concentration

Counterparty risk shows up whenever you rely on an intermediary. Examples include:

• Holding USD1 stablecoins in a custodial wallet.
• Using a centralized bridge or broker.
• Using an exchange for conversion.

Concentration risk (when too much activity depends on a small number of providers) can also appear. If most routes depend on one bridge or one settlement network, a disruption can affect many users at once.

Many regulatory discussions emphasize that stablecoin arrangements should meet high standards before operating at scale, including governance and risk management requirements.^[2][3]

Smart contract risk

Smart contract risk includes:

• Bugs in contract code.
• Vulnerabilities in upgrade mechanisms.
• Misconfigured access controls.
• Oracle risk (oracle means a system that provides external data to a blockchain contract, such as prices).

If routing relies on a smart contract bridge or automated market maker (an automated market maker is a trading system that uses pools of funds and formulas instead of traditional order books), the route inherits these risks.

Financial crime controls

If you route through regulated intermediaries, they may screen transactions for sanctions and suspicious activity. Sanctions screening (sanctions screening means checking people, entities, and some destinations against restricted lists) can reduce certain risks but may also introduce delays or holds that peer-to-peer routes do not have.

FATF guidance is widely used as a global reference for how AML and counter-terrorist-financing expectations apply to virtual assets and related businesses.^[4] FATF has also published material aimed at improving Travel Rule supervision, which is relevant because routing may involve passing identifying information between service providers for some transfers.^[5]

Consumer and business protections

Routing affects protections like:

• Error resolution and support.
• Dispute handling.
• Disclosure of fees and timing.
• Safeguarding of customer funds.

For example, a direct on-chain transfer is transparent but offers little built-in dispute handling. A routed payment through a processor may offer better support but adds fees and introduces a counterparty.

In the United States, the 2021 interagency report on stablecoins highlights concerns about user protection, payment system risk, and the need for clear rules when stablecoins are used for payments.^[7]

Routing patterns by audience and use case

Routing looks different depending on who you are and what you are trying to accomplish.

Individuals: sending money to another person

Individuals typically optimize for simplicity and low error risk. Common preferences include:

• Using the same wallet and same network as the recipient to avoid bridge steps.
• Using a reputable custodian when the recipient is not comfortable managing keys.
• Keeping transfers small when testing a new route.

Individuals also face the wrong network problem: sending USD1 stablecoins on Network X to a recipient who only monitors Network Y. Routing design should include clear network labeling and recipient confirmation.

Small businesses: getting paid and paying suppliers

Businesses often care more about:

• Predictable settlement and clear records.
• Fee transparency.
• The ability to produce invoices and receipts that match transfers.
• Treasury policy (rules for how long the business holds USD1 stablecoins versus converting to U.S. dollars).

A practical business route might accept USD1 stablecoins on a single network that customers can access, then periodically convert to U.S. dollars through a regulated intermediary.

Cross-border transfers and remittances

Cross-border routes can be attractive because USD1 stablecoins can move continuously, without banking hour cutoffs. But cross-border routing also introduces more compliance and user-protection complexity.

The BIS Committee on Payments and Market Infrastructures has published a detailed discussion of opportunities and challenges when stablecoin arrangements are used in cross-border payments, emphasizing that benefits should not be achieved by weakening risk management.^[1] The broader G20 Roadmap work similarly frames cross-border payments goals around cost, speed, access, and transparency.^[8]

In practice, routing for cross-border use often includes:

• Local on-ramps and off-ramps (on-ramp means converting local money into USD1 stablecoins; off-ramp means converting USD1 stablecoins back into local money).
• Compliance checks in both sending and receiving regions.
• Liquidity management for local currency conversions.

Routing also interacts with local payment systems. For example, bank transfers in the United States, Europe, and other regions can have different cutoff times, settlement expectations, and disclosure norms. A route that looks efficient on paper can become slow if it depends on a banking step that does not run continuously.

Developers and integrators

Developers building with USD1 stablecoins tend to focus on:

• Network support and technical reliability.
• Confirmation policies (how many confirmations are treated as final).
• Fallback routes when a network is congested.
• Monitoring and alerting for stuck transfers.

A technical but practical concept here is idempotency (idempotency means a request can be repeated safely without causing double payment). Routing systems should be designed so retries do not accidentally send twice.

Institutions and large treasuries

Institutions often treat routing as a risk-managed process. They may require:

• Multiple approved routes with clear limits.
• Separation of duties (one person initiates, another approves).
• Auditable records.
• Legal review of service providers and stablecoin arrangements.

They may also require segmentation by region due to regulatory differences, licensing, and local payment infrastructure.

Privacy and transparency trade-offs

Routing for USD1 stablecoins sits between two forces:

• On-chain transparency can improve auditability, reduce disputes about did it arrive, and simplify some forms of compliance monitoring.
• On-chain transparency can also reduce privacy because transfers can be linked through addresses, timing, and transaction patterns.

Privacy is not only about secrecy. It is also about minimizing unnecessary exposure of business relationships, customer lists, payroll timing, and purchasing behavior.

Routing choices that affect privacy include:

• Whether you reuse addresses (reusing an address can make linking easier).
• Whether you route through a custodian (a custodian may see more of your activity).
• Whether you use one network for all transfers (single-network patterns can create clearer footprints).
• Whether you separate operational flows (for example, using distinct wallets for payroll and supplier payments).

A balanced view recognizes that privacy goals must coexist with integrity controls. Many public bodies emphasize integrity (integrity means resistance to fraud and illicit finance) as a core requirement for money-like instruments.^[2][4]

Security and operational controls

Security is inseparable from routing because each extra hop adds an extra place something can go wrong.

Address safety and human error

On-chain routing can fail due to simple mistakes. Common failures include:

• Sending to the wrong address.
• Sending on the wrong network.
• Copying a deposit address that is no longer valid.
• Forgetting memo or reference fields when a service requires them.

Many of these failures are preventable through better user interface design, but routing plans should assume humans make mistakes. When mistakes are costly, routes should include safeguards like confirmation prompts and small test transfers.

Key management and account controls

If you control your own keys, key management (how you generate, store, and protect private keys) is the core security issue. If a custodian holds keys, then account security and custodian security are the core issues.

Basic controls include:

• MFA (multi-factor authentication, meaning you need more than a password).
• Hardware security keys.
• Withdrawal allowlists (approved destination addresses).
• Multi-signature wallets (multi-signature means more than one key is required to move funds).

NIST’s blockchain overview provides background on how blockchain systems work and why key control is central to security.^[9]

Service provider due diligence

If routing relies on third parties, questions to ask include:

• What networks and token representations are supported?
• How are reserves and redemption handled for the USD1 stablecoins involved?
• What happens during outages?
• What customer support exists for failed transfers?
• What compliance expectations apply?

IOSCO policy work on crypto and digital asset markets emphasizes themes like disclosure, custody safeguards, and operational resilience, all of which relate to routed stablecoin payments and transfers.^[10]

Tracking, records, and reconciliation

Good routing is observable. That means you can answer questions like:

• Has the transaction been broadcast?
• Has it been confirmed?
• How many confirmations does it have?
• Which address received it?
• What was the total cost including fees?
• What reference connects it to an invoice or payment request?

In on-chain routes, the transaction hash (a transaction hash is a unique identifier for a transaction) is the main receipt. In custodian routes, you may also need internal transaction identifiers and timestamped statements.

For businesses, reconciliation often becomes the limiting factor. If your accounting system cannot reliably map transfers to business events, the route becomes expensive, even if the fee line item is low.

Cross-border payment work by international bodies repeatedly treats transparency as a key outcome, in part because transparency reduces errors and reduces the operational cost of investigating delays.^[8]

Troubleshooting routing failures

Even well-designed routes fail sometimes. A troubleshooting mindset starts by identifying where the route is stuck.

Problem 1: The on-chain transfer is pending

Possible reasons:

• The network is congested.
• The fee offered is too low.
• The transaction conflicts with another pending transaction from the same address.

What matters for routing is having a policy for pending transfers, such as waiting thresholds and fallback routes for time-sensitive payments.

Problem 2: The bridge step is delayed

Possible reasons:

• Bridge liquidity is low.
• The bridge is paused due to risk controls.
• The destination network is unstable or congested.

Bridge delays highlight why routing systems often maintain multiple approved routes, rather than relying on a single bridge.

Problem 3: The recipient says the funds never arrived

Possible reasons:

• Funds were sent on the wrong network.
• The recipient is using a wallet that does not show that token representation.
• The custodian has not credited the deposit yet due to internal checks.

In many cases, the issue is not the network lost the funds but the route did not match the recipient’s acceptance conditions.

Problem 4: A compliance hold stops delivery

Possible reasons:

• The transfer triggered an automated risk rule.
• Required identity information is missing for the route.
• A sanctions screening match requires review.

This is one of the clearest examples of routing trade-offs: a route with stronger compliance controls may be safer and more broadly usable, but it can introduce delays that a peer-to-peer route would not have.

FAQ

Are USD1 stablecoins the same as a bank account?

No. USD1 stablecoins are digital tokens designed to track the U.S. dollar and be redeemable at a 1:1 rate, but the protections, disclosures, and legal structure can differ from bank deposits. Some routes may involve bank deposits after redemption, but that is a different layer of the system.^[7]

Can I reverse a transfer if I used the wrong address?

Usually not, if the route was a direct on-chain transfer and it became final. Some custodial routes may offer support processes, but that depends on the provider and the situation. If reversibility is a hard requirement, design the route around a system that supports disputes or escrow.

Why do two people see different fees for the same payment amount?

Because routing costs depend on the chosen network, network congestion, conversion steps, spreads, and service fees. Two people paying the same amount in USD1 stablecoins can take entirely different routes with different all-in costs.

Why is cross-border routing complicated?

Because cross-border routes often involve multiple currencies, multiple regulated intermediaries, local banking constraints, and different compliance expectations. International work on cross-border payments emphasizes that improving outcomes requires coordination across many building blocks, not just faster technology.^[8]

What is the single most common routing mistake?

Sending USD1 stablecoins on the wrong network for the recipient. It is the stablecoin version of using the right account number in the wrong country format. Routing designs that make the network choice explicit reduce this failure.

Sources

1. BIS Committee on Payments and Market Infrastructures, "Considerations for the use of stablecoin arrangements in cross-border payments" (2022)
2. Financial Stability Board, "Regulation, Supervision and Oversight of 'Global Stablecoin' Arrangements" (2020)
3. Financial Stability Board, "High-level Recommendations for the Regulation, Supervision and Oversight of 'Global Stablecoin' Arrangements" (2023)
4. Financial Action Task Force, "Updated Guidance: A Risk-Based Approach to Virtual Assets and Virtual Asset Service Providers" (2021)
5. Financial Action Task Force, "Best Practices on Travel Rule Supervision" (2025)
6. European Central Bank, "Stablecoins on the rise: still small in the euro area, but ... " (2025)
7. U.S. Department of the Treasury, "Report on Stablecoins" (2021)
8. Financial Stability Board, "Cross-border Payments" (work program overview)
9. National Institute of Standards and Technology, "Blockchain Technology Overview" (NISTIR 8202, 2018)
10. International Organization of Securities Commissions, "Policy Recommendations for Crypto and Digital Asset Markets" (2023)