What Destination Token Fees Pay For

A destination token fee is a cross-chain transfer charge deducted from, or charged in, the token you receive on the destination chain. First, you choose an amount and destination token; a router gets quotes for routes between the chains. The selected bridge or relayer then moves value across, and a destination transaction delivers the token to your wallet. The fee can cover transfer costs, liquidity, destination execution or an app’s own charge. Protocols use different fee models, so the label alone does not tell you what you will receive. For more on how a route can deliver the token an app needs, see this guide to the bungee bridge.

What does a destination token fee pay for?

It pays for one or more parts of completing the transfer, depending on the route. A relayer may advance tokens on the destination chain and later settle with liquidity providers. The fee can compensate those parties for destination gas, liquidity use and the time or risk involved. The Across documentation describes its transfer cost as a combination of liquidity-provider and relayer fees, with relayer fees covering gas, capital and risk. Those charges are reflected in the difference between the deposit and the amount received.

A separate app fee may also be taken from the output token. Across, for example, documents an optional integrator fee charged in the output token and paid to a designated recipient on the destination chain. Chainlink’s CCIP documentation shows another distinction: some charges are paid on top in a selected fee token, while configured token-pool fees can be deducted from the transferred amount. These are examples of different models, not universal rules.

How is it different from destination gas?

Destination gas pays validators or block producers to include a transaction on the destination chain. A destination token fee is a charge measured in the token delivered, if the route takes it from that output. The two costs can be related: a relayer’s fee may account for gas it expects to pay. But the wallet may not have to pay destination gas separately if the relayer executes the delivery and includes that cost in the quote.

Think of the route quote as a receipt estimate: it should show what goes in, what comes out and which charges are included. The quoted destination amount is not necessarily the amount you would get by converting the source token at a market price; swaps, price impact and fees can all affect it.

How can you compare destination token fees?

Compare routes using the same source amount, destination chain and destination token. Read the estimated receive amount alongside the fee breakdown; a smaller listed fee does not guarantee a better deal if the route offers less output. Check these details before signing:

• Destination chain and token address, not just the token ticker.
• Estimated output and any minimum received amount.
• Whether fees are deducted from the output or charged separately, and in which token.
• Whether the quote includes destination execution or leaves you needing native gas to use the funds afterward.

Fees and quotes can change with gas prices, liquidity and route conditions. Bungee’s fee documentation says it does not add a markup when transactions are routed through other protocols, while its Auto flow includes on-chain execution costs in quoted fees. That is specific to Bungee’s stated model; other routes can differ. The practical rule is to judge the amount that reaches the correct destination token and wallet, then check whether you will need native gas for your next transaction.