# What is cross-chain routing?

Canonical: https://apa.app/resources/guides/what-is-cross-chain-routing
Category: Concepts

A plain-language explanation of cross-chain routing for merchants accepting crypto payments.

Cross-chain routing lets a customer pay with one supported asset or network while the merchant receives another. For a payment product, the goal is not to make merchants think about bridges and swaps. The goal is to make the route explicit, priced, and safe enough to show at checkout.

## A route exists when direct payment does not match

A direct payment matches the merchant payout asset and network. Routing appears when the customer pays a different asset, a different network, or both.

For example, a merchant may receive USDC on Solana while a customer wants to pay ETH on Base. The route needs to convert the payment into the merchant's payout asset and network.

- Different asset can require a swap.
- Different network can require a bridge.
- Different asset and network can require both steps.

## The checkout should explain the tradeoff

Routing is useful because it lets more customers pay. It also adds more moving parts than a direct wallet-to-wallet payment. A good checkout shows the route type, expected output, fee, expiry, and risk state before the customer pays.

In Apa, direct payments are free and routed payments use one flat routed fee. That keeps the pricing model simple for merchants and customers.

## Webhooks close the loop

A routed payment can move through pending, routing, settling, paid, failed, or refund-required states. Ecommerce stores should wait for a signed webhook before fulfilling the order.

That keeps the storefront clean while the merchant backend receives the reliable final payment state.

## FAQ

### Is cross-chain routing the same as a direct crypto payment?

No. Direct payments match the merchant payout asset and network. Routing is used when the payment needs an asset conversion, a network bridge, or both.

### Should merchants hide routing details?

No. The customer should see when a payment is routed, what they are expected to pay, what the merchant is expected to receive, and whether the route can expire or fail.