Does a failed Ethereum bridge transaction still incur a network fee?

An Ethereum transaction that executes and fails still consumes gas. Include the network fee that was actually charged when accounting for that attempt. A transaction rejected before execution is a different state, so an error message alone doesn’t establish a gas charge or a completed bridge transfer.

Why can API transfer limits differ when fee inclusion is switched?

The API’s value_include_gas_fee setting determines whether its minimum and maximum transfer values include the gas fee within the input amount. Compare limits using the same setting. This flag describes how those limits treat fees; it doesn’t supply a universal gas price or guarantee the final wallet charge.

Can manually changing bridge settings lower the quoted fee?

Manual adjustments to available bridge settings can potentially lower fees or change transfer speed. The applicable result depends on the selected supported transfer and the settings offered for it. A possible reduction doesn’t establish a fixed discount, so compare the resulting quote on the same amount and fee basis.

Is the referral commission credited to the wallet paying the bridge fee?

The referral commission is credited to the inviter’s commission account after the referred wallet completes a cross-chain transaction. Its basis is a share of that transaction’s fee. The commission credit belongs to the inviter and doesn’t, by itself, establish a discount or refund for the fee-paying wallet.

Are earned bridge points a monetary deduction from transfer costs?

Reward points are a separate quantity and shouldn’t be subtracted directly from a monetary fee total. Bridging activity can earn points, but a points credit alone doesn’t establish a cash refund or a change in the delivered token amount. Reconcile monetary charges in their own token or currency units.

Where can an unexplained difference in a bridge payout be reported?

An unexplained transfer discrepancy can be raised through Owltofinance’s Discord ticket support. The support process includes server verification before opening a ticket. Include the source transfer hash, selected asset, chain direction and relevant quote details so the issue can be tied to that request.

Owltofinance

Owltofinance bridge fees scale with the transfer amount at an unchanged rate and accompany prepaid destination transaction costs

Last updated · Tuesday, 13 October 2026

Owltofinance bridge fees are percentage-based charges that must be reconciled alongside prepaid destination costs and source-chain gas. The bridge quote describes a transfer request; the destination record establishes the amount delivered. Total cost also includes the network fees that the sending wallet actually pays. A token transfer may require an approval transaction before submission. Keep that approval’s gas separate from the bridge’s percentage charge, and compare the completed source and destination records using consistent token units.

The percentage charge and the prepaid destination cost

Quoted bridge charges equal the percentage fee on the transfer amount plus the prepaid destination transaction cost. Written symbolically, C = A × r + D. Here, A is the transfer amount used for the fee calculation, r is the decimal rate and D is the prepaid destination charge. The quote supplies the applicable rate and destination charge for the selected transfer. C excludes the source wallet’s separately paid network gas. All added amounts must use the same monetary unit. If gas uses another token, retain separate totals until a stated conversion puts them into a common unit.

The percentage fee goes to the platform and market makers. The destination charge compensates the market maker in advance for the receiving-chain transfer.

Amounts, fee units and supported pairs

Token quantities, transaction values and wallet balances need their own labels before they can support a fee calculation. The amount entered for a transfer isn’t automatically the same as the wallet’s total debit. An expected receive amount describes the quoted output; the completed destination transfer establishes delivery. Source gas may use a different token from the asset being bridged. Adding those raw quantities would give a total with mixed units. A fiat total needs a stated conversion for each charged asset, using one valuation basis across the comparison.

A supported transfer pair combines an asset with its source and destination chains. The chosen amount must fall within that pair’s accepted range. An out-of-range value can cause the bridge request to fail. Network support alone doesn’t establish support for every token or transfer direction. Use the route that belongs to the actual request when comparing costs. A quote from another pair can have different fee terms, even when the displayed token name matches.

The API’s get_all_pair_infos response supplies pair-specific minimum and maximum values. These are transfer limits, so they don’t express the rate charged by the bridge.

Cost records through the transfer stages

The quote, source submission and destination payout describe different states of the same request. In the browser interface, route and fee calculation follow the selected asset and network options. The wallet then confirms and signs the transaction. Completion provides records from both chains, which can be compared with the stored quote.

Cost records through the transfer stages
Transfer stage	Cost record	Applicable transfer scope
Quote preparation	Percentage charge, prepaid destination cost and expected output	Selected asset and supported source-destination pair
Source submission	Wallet gas estimate, then the submitted transfer hash	Source chain; an approval comes first when required
Bridge processing	In-progress state; destination amount remains unconfirmed	Transfer identified by its source transaction hash
Destination completion	Completed destination transaction and delivered token amount	Receiving address and token on the selected destination chain
Cost reconciliation	Source fees, delivered amount and original quote	Amounts matched by token unit and transfer direction

A supported token transfer on an EVM (Ethereum Virtual Machine) chain may need an approval transaction before the bridge transfer. With sufficient allowance, the SDK leaves its approval transaction body empty, so the source-network cost can differ between allowance states even when the transfer amount and supported pair remain unchanged. Add an approval’s actual gas only when that transaction occurred. An approval permits the specified contract to spend tokens; it doesn’t establish destination delivery. The transfer transaction supplies the hash used to track the bridge’s progress.

Does a source transaction hash confirm destination delivery?

A source transaction hash identifies the sending-chain transfer, while destination delivery requires a completed receiving-chain record. The browser status can show Processing after wallet confirmation, leaving the cross-chain transfer in progress. Success indicates that the transfer has finalized. Receipt queries use the transfer’s source hash to track that process. While delivery remains unresolved, record the submitted source transaction and its confirmed charges separately from the expected destination amount.

View image file

Matching the completed payout to source charges

Match the destination payout to its receiving address, token and chain before interpreting a difference as a fee. Bridge receipts provide send and receive value fields plus destination transaction identifiers. Compare the receiving transaction’s amount with the quoted output using matching token units; a wallet’s overall balance can include unrelated activity.

Source records establish the fees that the sending wallet actually paid, including any approval tied to this transfer. If a send-to-receive difference already includes the quoted charges, adding those same components again would double-count them. Source gas paid separately still belongs in the wallet’s total cost. When charged assets differ, preserve each token amount and apply a consistent conversion only for a common monetary total. This accounting requires the quote’s actual treatment of fees, so don’t assume that every displayed amount includes the same components.

History records include the initiation timestamp, transferred amount and network path. They help distinguish this transfer from nearby wallet activity when several transfers involve the same asset.

Should the maker’s destination gas be added to the quoted charge?

The maker’s destination gas shouldn’t be added again when the quoted destination charge already covers that delivery. Destination TX Costs prepay the market maker for the destination-network transfer. If the destination explorer displays a network fee paid by the maker, that figure doesn’t establish an additional debit from the receiving wallet. Later transactions from the receiving wallet have their own network costs. A later contract deployment is a separate operation, so its gas belongs to a different task than the completed bridge’s fee total.

Transfer size and changing network charges

At an unchanged percentage rate, a larger transfer amount produces a larger percentage charge. If the quoted destination charge stays constant, it represents a smaller proportion of a larger transfer. This relationship doesn’t establish a cheaper route or an amount to send. Source gas and the destination charge can also change between requests. A comparison needs the same fee basis, with each changed input visible instead of attributing every difference to transfer size.

Destination gas conditions can prompt changes to the destination-related fee, and adjustments aren’t frequent. A lower network gas price doesn’t promise an immediate matching reduction in the displayed charge. Keep the accepted quote with its transfer record during reconciliation. Substituting a newer rate would mix the terms of separate requests. If the pair, amount, approval requirement or destination charge changes, the applicable cost calculation changes too.

Useful questions about Owltofinance bridge fees

Does a failed Ethereum bridge transaction still incur a network fee?: An Ethereum transaction that executes and fails still consumes gas. Include the network fee that was actually charged when accounting for that attempt. A transaction rejected before execution is a different state, so an error message alone doesn’t establish a gas charge or a completed bridge transfer.
Why can API transfer limits differ when fee inclusion is switched?: The API’s value_include_gas_fee setting determines whether its minimum and maximum transfer values include the gas fee within the input amount. Compare limits using the same setting. This flag describes how those limits treat fees; it doesn’t supply a universal gas price or guarantee the final wallet charge.
Can manually changing bridge settings lower the quoted fee?: Manual adjustments to available bridge settings can potentially lower fees or change transfer speed. The applicable result depends on the selected supported transfer and the settings offered for it. A possible reduction doesn’t establish a fixed discount, so compare the resulting quote on the same amount and fee basis.
Is the referral commission credited to the wallet paying the bridge fee?: The referral commission is credited to the inviter’s commission account after the referred wallet completes a cross-chain transaction. Its basis is a share of that transaction’s fee. The commission credit belongs to the inviter and doesn’t, by itself, establish a discount or refund for the fee-paying wallet.
Are earned bridge points a monetary deduction from transfer costs?: Reward points are a separate quantity and shouldn’t be subtracted directly from a monetary fee total. Bridging activity can earn points, but a points credit alone doesn’t establish a cash refund or a change in the delivered token amount. Reconcile monetary charges in their own token or currency units.
Where can an unexplained difference in a bridge payout be reported?: An unexplained transfer discrepancy can be raised through Owltofinance’s Discord ticket support. The support process includes server verification before opening a ticket. Include the source transfer hash, selected asset, chain direction and relevant quote details so the issue can be tied to that request.