Can I reduce bridge costs by splitting one transfer into smaller transfers?

Splitting can increase costs because each transfer can incur its own fixed withholding charge and source-network transaction fee. Smaller transfers may also face different limits or quotes. Compare the combined fees and destination amounts for the proposed pieces with one valid quote for the full amount. A lower fee on an individual piece doesn't establish that the complete transfer costs less.

Will reversing a route keep the same Orbiterfinance bridge fee?

The reverse direction needs its own quote because the source and destination payment roles change. Destination gas, maker liquidity, and route pricing can differ between directions. The gas that your wallet pays also belongs to the new starting network. A successful outbound quote doesn't establish the return route's current availability, transfer limits, or fees.

Does a zero contract feeAmount make an Orbiterfinance bridge free?

Setting feeAmount to zero in the Aggregator's executeBridge call removes that call's explicit commission, not every transfer cost. That zero-fee configuration also requires a zero feeRecipient address. Source-network gas remains a separate consideration, and the selected route can still have other bridge charges.

When can a token approval add a separate network fee?

A token approval incurs its own network fee if it executes as a separate on-chain transaction. Whether you need a new approval depends on the selected token, spender, existing allowance, and execution method. An approval grants permission to move tokens, so its transaction doesn't itself establish the destination bridge payment. Count separately payable approval gas in the transfer budget.

How should an integration replace an outdated bridge fee simulation?

Use the REST API to obtain a quote when replacing the outdated JavaScript SDK's fee simulation. The legacy SDK's send-and-receive examples don't establish a price for a newly requested route. The API quote provides component charges and destination amounts together. Those fields let an integration display costs for the requested transfer without applying an old example rate.

Orbiterfinance bridge fees by route and cost component

Updated Sunday 11 October 2026

Orbiterfinance bridge fees depend on the token, transfer amount, starting network, and destination network. Maker-based transfers combine a fixed withholding charge with a percentage trading fee. Source-network gas adds a separate cost, and a route that exchanges tokens can include a swap fee. Your selected quote reports the component fees and expected destination amount.

A bridge quote and a wallet's gas estimate describe different costs. Keeping their units and payment roles clear prevents double counting, especially when a transfer includes a swap or runs through another application.

Source payment and destination liquidity have different costs

In the maker-based bridge model, the sender funds a source-network transaction while the maker uses destination liquidity to pay the receiving wallet.

The source balance

For a transaction that you fund directly, your source balance must cover its transfer amount and network charge. Depending on the asset and network, the transferred token and gas token can differ. The source wallet then needs both balances. The withholding deduction covers a different part of the transfer, so it doesn't supply the source wallet's gas.

The destination payment

The maker's liquidity supplies the destination payout after the sender initiates the source-network transfer. That destination payment has its own network cost, which explains the withholding charge in this model. These relationships describe the maker-based path; contract-based routes may use different execution steps. The selected quote must still identify the destination token and recipient.

Fixed charges and percentage fees behave differently

A withholding charge contributes a set token amount for the selected route, while the trading component follows that route's applicable percentage and amount basis.

The withholding charge

In the maker-based bridge model, the withholding fee covers gas for the destination transfer. Its amount can differ between destinations and can change when pricing changes. Fixed describes the fee's form within the quote, not a permanent price for every transfer. Read the token unit alongside the figure; its dollar equivalent is a conversion of that charge.

The trading percentage

The trading fee scales with the amount basis that the route uses. Read the quoted charge in token units alongside the applicable rate. The route's calculation may produce a charge that differs from a simple percentage of the amount you entered. When the fixed charge stays unchanged, a larger valid transfer spreads it across more tokens.

Published example rates aren't a tariff for every token or direction. Your selected route supplies the applicable charges.

Does the quoted total fee include source-network gas?

The documented totalFee subtotal doesn't include a separate source-network gas estimate. The tradeFee entry reports the transaction handling charge. The documentation defines the subtotal as withholding, swap, and transaction fees. The totalFee field description specifies feeSymbol as the unit, while the published response example sums the USD fee fields. Confirm the unit before using totalFee in a calculation. A wallet can show an additional network charge when you sign the transaction. Count a separately payable charge alongside the quoted subtotal, while avoiding another destination-gas entry when the withholding fee already covers it.

The quote provides a swap fee field and separate output details for routes that exchange assets. A zero swap fee leaves the other cost components to account for. The exchange rate can still affect the value received. Slippage tolerance sets acceptable price movement; it doesn't remove the withholding charge, trading fee, or source gas.

Keep different currencies separate until you convert them using one consistent valuation. Adding a gas-token quantity directly to a transfer-token quantity produces a meaningless total.

An application can also configure a commission when requesting a quote. Its configuration names a fee recipient and a percentage. Identify whether the quoted output or transaction amount already accounts for that commission. Subtracting the same charge again overstates the cost. This application-specific component matters when comparing quotes through different interfaces.

Calculate a bridge-only fee subtotal

When the component fees share one token unit, adding them gives a usable subtotal before you account for any separate source-network charge.

A hypothetical bridge-only quote

This hypothetical bridge-only quote shows a withholding fee of 0.42 token units and a transaction fee of 0.072 token units. Its swap fee is zero, and the wallet quotes a separate source-network gas charge. All component amounts refer to the same fee token.

Adding 0.42 + 0.072 + 0 gives a quoted subtotal of 0.492 token units. The source gas charge remains outside that subtotal. If gas uses another token, convert both costs to a common currency before adding their values.

The subtotal measures quoted charges. The quote's output details give the destination amount. A nonzero swap fee would change the subtotal; a different exchange rate could change destination value even if the component fees stayed unchanged.

Compare quotes on the same transfer terms

Quotes become comparable when the starting network, input token, amount, destination network, recipient, and output token describe the same transfer. Match those terms before comparing charges. Changing only the destination can alter the withholding cost and available liquidity. Changing the output token introduces an exchange decision as well. Compare the fees together with the destination quantity, keeping the output token's identity and units clear. A lower fee figure can accompany a different asset or a smaller payout.

For routes that combine bridging with a swap, keep the slippage setting consistent during comparison. Matching that setting makes the quoted output boundaries comparable. The fee components describe explicit charges; price impact describes an effect on the exchange price. Don't label every difference between input and output as a bridge fee, especially when the token changes. Read any displayed dollar values using the same price basis.

Recheck pricing when transfer conditions change

A quote applies to its requested destination, token amount, and execution path; changing those inputs calls for another quote.

Transfer limits and liquidity

Available liquidity and transfer limits determine whether the requested amount fits a maker-based route. A price extrapolated from a smaller transfer can't establish availability for a larger amount. Increasing the amount can lower the fixed fee's proportional burden without making the larger transfer available. Check the applicable range alongside the price, and keep the input asset's identity tied to its network.

Source gas and transaction structure

Source gas depends on the network's pricing rules and the work that the transaction performs. Contract interactions can require different execution work from a simple transfer. For an Ethereum Virtual Machine (EVM) transaction, the gas limit caps how many gas units it can consume; it isn't a token-denominated bridge fee. A quote's transaction data and a wallet's gas estimate therefore serve different purposes. Use the estimate for the actual transaction that you'll sign, especially if the route changes its required operations.

Reconcile the quote with the settled transfer

The final cost reconciliation needs the actual source-network charge and the confirmed destination payment, alongside the quote that described the requested transfer. A successful source transaction can precede the maker's destination payment. The receiving wallet's confirmed payout supplies the amount to compare with the quote. Compare the destination token, recipient, and amount with the intended payout. While the payout is pending, the missing destination balance isn't a settled fee amount.

A later transaction from the receiving wallet creates its own network cost. Include it in a broader movement budget only when that further action belongs to your task. Recalculate the comparison if the route, fee configuration, or output asset changes before execution.

Illustration: Reconcile the quote with the settled transfer (Orbiterfinance bridge fees)

Open full-size image

Orbiterfinance bridge fees: common questions

Can I reduce bridge costs by splitting one transfer into smaller transfers?: Splitting can increase costs because each transfer can incur its own fixed withholding charge and source-network transaction fee. Smaller transfers may also face different limits or quotes. Compare the combined fees and destination amounts for the proposed pieces with one valid quote for the full amount. A lower fee on an individual piece doesn't establish that the complete transfer costs less.
Will reversing a route keep the same Orbiterfinance bridge fee?: The reverse direction needs its own quote because the source and destination payment roles change. Destination gas, maker liquidity, and route pricing can differ between directions. The gas that your wallet pays also belongs to the new starting network. A successful outbound quote doesn't establish the return route's current availability, transfer limits, or fees.
Does a zero contract feeAmount make an Orbiterfinance bridge free?: Setting feeAmount to zero in the Aggregator's executeBridge call removes that call's explicit commission, not every transfer cost. That zero-fee configuration also requires a zero feeRecipient address. Source-network gas remains a separate consideration, and the selected route can still have other bridge charges.
When can a token approval add a separate network fee?: A token approval incurs its own network fee if it executes as a separate on-chain transaction. Whether you need a new approval depends on the selected token, spender, existing allowance, and execution method. An approval grants permission to move tokens, so its transaction doesn't itself establish the destination bridge payment. Count separately payable approval gas in the transfer budget.
How should an integration replace an outdated bridge fee simulation?: Use the REST API to obtain a quote when replacing the outdated JavaScript SDK's fee simulation. The legacy SDK's send-and-receive examples don't establish a price for a newly requested route. The API quote provides component charges and destination amounts together. Those fields let an integration display costs for the requested transfer without applying an old example rate.