Skip to main content
Bridging is the same flow as a swap, you just set toChain to a different chain. Settlement is asynchronous, so the status step polls. Pick a chain below; the tabs stay in sync across Setup, Steps, End-to-end, and API usage.

Setup

Bridge USDC from Arbitrum to Base.

Steps

1

Quote

Quote across bridge providers. Setting toChain to a different chain than fromChain is what makes this a bridge.
To bias toward speed or a specific bridge, use filter: 'fastest' or provider allow/deny lists, see advanced quote fields.
2

Approve

Approval is on the source chain only: the bridge handles disbursement on the destination side. AutoPermit keeps it gasless where the token allows.
Other approval flows (Permit2, EIP-2612, gasless permits) are in Check allowance and Approval mechanisms.
3

Build & send

trade() builds the bridge transaction, then signs and sends it in one call. refundee and recipient matter more here than on a same-chain swap.
trade() builds and sends in one call. Call buildTradeTxn first only to preview the transaction or reuse it via txnData. Use a refundee you control on the source chain, and set recipient to the address that should receive funds on the destination. Full request shape: Execute trade.
4

Status

Cross-chain settlement is asynchronous: poll getTradeTxnStatus until it reaches a terminal state.
Terminal states are COMPLETED, FAILED, PARTIAL, and REFUNDED. See Track trade status for a ready-made polling helper.

End-to-end

API usage

The same flow over REST. Non-EVM chains build a chain-specific transaction you sign locally, then submit via Broadcast.
Sign and broadcast the transaction from the build response with your own signer. Full reference: Quote, Build Tx, Status.

Bridge quirks

  • refundee matters. If the destination leg fails, funds return to refundee on the source chain. Use a wallet you control.
  • recipient can differ from sender. Useful when paying on someone else’s behalf, they receive on the destination chain.
  • Settlement time varies. Across is seconds; CCTP is ~13 minutes; others vary by route. Read best.duration from the quote.
  • Approval is source-chain only. No extra approval on the destination side; the bridge contract handles disbursement.

When to use Fuse instead

If your goal is “bridge, then do something on the destination” (add liquidity, mint, stake), use a Fuse bundle, one signature for the whole journey.
Last modified on September 21, 2026