The lifi bridge uses four route shapes: bridge only, swap then bridge, bridge then destination swap, and swap-bridge-swap. For a new transfer, the LI.FI bridge finds routes across supported bridges and decentralized exchanges; lifi bridge can help you compare how those steps fit together. Each step can succeed or stop on its own, so the last completed step determines which token arrives.
How to read a lifi bridge route
A route shows the planned order of swaps and the cross-chain bridge step. Read it from the source token toward the requested destination token. The token delivered by the bridge may be an intermediate asset that a later swap was meant to convert.
Bridge only
A bridge-only route moves an asset to another chain without a separate swap. It suits a transfer such as USDC to USDC when the chosen bridge can deliver the requested destination asset directly. The token contracts can have different addresses on the two chains, so compare the destination token’s address as well as its symbol.
With no destination swap to complete, the bridge delivery is the final token outcome. That makes this the simplest shape to read when a transfer has finished.
Swap then bridge
A swap-then-bridge route converts your source token into a bridgeable token before sending it across chains. It suits someone whose starting token cannot take the selected bridge route directly. Say you start with one asset, swap it for USDC on the source chain, then bridge that USDC to the destination.
The source swap determines what enters the bridge. If it stops before the bridge starts, there is no destination delivery to interpret. If it completes, inspect the bridge’s output token to identify what should arrive.
Bridge then destination swap
A bridge-then-destination-swap route delivers an intermediate token and then converts it into the token you requested. It suits a destination asset that the bridge itself does not deliver. The crucial distinction is between the bridged token and the requested token: they are two outcomes of two steps.
Suppose the bridge delivers USDC.e, and the planned destination swap would turn it into native USDC. If that swap fails, cannot find enough liquidity, or exceeds its allowed slippage, you can receive USDC.e instead. The cross-chain leg succeeded; the final conversion did not. LI.FI records a delivered token other than the requested one as DONE with substatus PARTIAL.
That is why an unexpected destination token is usually an intermediate asset, not missing funds. In LI.FI Scan, compare the requested output with the receiving token and the steps that actually ran. Confirm the chain and token address before deciding what to do with the asset. A matching symbol alone may conceal a bridged variant.
Swap-bridge-swap
A swap-bridge-swap route converts the starting token into a bridgeable asset, crosses chains, then swaps that asset into the requested output. It suits a transfer where neither the starting token nor the desired destination token fits a direct bridge route.
This shape has two conversion points. The first swap determines the bridge input; the second determines the final token. If the destination swap stops after delivery, the receiving token can be the bridged asset and the substatus can be PARTIAL. Read the steps in order to see which conversion completed.
How bridge mechanisms affect the outcome
The bridge mechanism explains how the middle leg settles within any of the four shapes. Intent-based routes, such as Across, Relay, and Mayan, arrange for an actor to fulfill a destination outcome; Across relayers front their own funds on the destination chain. Pool-based routes, such as Stargate, use liquidity available across chains. Circle CCTP uses burn-and-mint: USDC is burned on the source chain and native USDC is minted on the destination. The mechanism helps explain the bridge delivery, while the route’s last swap determines whether that delivery becomes your requested token.
What is a lifi bridge refund?
A LI.FI bridge refund means the requested destination delivery did not complete and funds were returned, typically on the source chain. The substatus REFUNDED identifies that outcome. A source swap may already have converted your original token, so a refund can arrive as a different token. Read the refund token, chain, and amount in the transfer record before looking only for your original asset.
Can you pick a specific bridge in lifi?
A LI.FI route can identify the bridge it uses, and integrations can filter route options by bridge. Whether you can choose one directly depends on the interface and on routes available for your tokens and chains. Compare the complete route, including both swaps, rather than treating a bridge name as the whole transfer: the final swap may decide what you receive.
To explain an unexpected token, follow the route to its last completed step. A successful bridge can leave its intermediate token on the destination when the final swap stops, producing PARTIAL; a REFUNDED transfer sends funds back instead. The route’s step order tells you where to look and why that token arrived.