> For the complete documentation index, see [llms.txt](https://help.enterprise.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.enterprise.ledger.com/help-center-v2/reference/transaction-fees.md). # Transaction fees How Ledger Enterprise calculates and displays transaction fees, why the figure you approve is a maximum, and what each network charges. Every fee on Ledger Enterprise is a **transaction fee**, paid to the network's miners or validators. Ledger charges nothing on top. ## The figure you approve is a maximum Signing does not happen when you create a transaction. Time passes while the Request collects its approvals, and network prices move in that window. So the platform authorizes a **ceiling** rather than a prediction.

Stage	What happens
At creation	The fee is estimated, and a buffer is added for most Networks. The total is the maximum fee
While approving	Nothing is recalculated. Approvers see the same figures the Creator saw
At broadcast	The network takes its actual price. The unused buffer stays in the Account

The signing payload sent to the Hardware Security Module (HSM) carries two ceilings. One is the **maximum fee**. The other is the **maximum total**, which is the amount plus the maximum fee. > **Important:** The HSM will not sign beyond those ceilings. A transaction that would cost more fails, rather than costing more than was approved. Nothing about a Request can be changed once it exists. A fee that turns out to be too low means creating the transaction again with a faster strategy. ## What the interface shows Every network that charges a fee shows the same figure: **Max Fee**, a ceiling. Canton charges the sender nothing. **Detailed fee** opens the breakdown behind it:

Label	What it is
Max Fee	The ceiling. The HSM will not sign above it
Buffer (%)	The margin added to the estimate to reach the ceiling
Estimated base fee	What the network is expected to charge
Network's own extra fee	See below by network

The buffer is what makes the ceiling larger than the estimate. Each network sets its own, listed below. ## By network

Network	How the fee is built	Buffer	Choice of speed	What you can customize
Bitcoin	Estimated base fee plus buffer	400%	Yes	`sat/byte`
Canton	No fee to the sender	None	No	The optional reason field
Ethereum and EVM	Gas limit multiplied by the sum of base fee, priority fee and buffer	200%	Yes	Gas limit, and the buffer percentage
Hedera	Estimated base fee plus buffer	100%	No	Nothing
Ripple	Estimated base fee plus buffer	100%	Yes	The maximum fee, and the destination tag
Stellar	Estimated base fee plus buffer	100%	Yes	The memo
Sui	Estimated base fee plus buffer	100%	No	Nothing
Tezos	Estimated base fee, plus buffer, plus an allocation fee where it applies	50%	Yes	Nothing
Tron	Worst-case TRX cost, assuming no bandwidth and no energy, plus buffer	100%	No	Nothing

Notes on individual networks: * **Bitcoin.** The fee depends on transaction size, so it depends on how many unspent outputs are spent. See [**Bitcoin**](/help-center-v2/reference/networks/bitcoin.md). * **Canton.** Holding fees apply to a coin contract, and only to archive one whose fees exceed its balance. See [**Canton**](/help-center-v2/reference/networks/canton.md). * **Ethereum.** The base fee and the priority fee are shown in Gwei, so small values stay readable. The priority fee is always paid in full; only the effective base fee is charged. * **Tezos.** Sending to an unallocated destination adds a one-time allocation fee. See [**Tezos**](/help-center-v2/reference/networks/tezos.md). * **Tron.** Bandwidth and energy cover the cost first. TRX is spent only when they run out. See [**Tron**](/help-center-v2/reference/networks/tron.md). ## Sponsored fees **Ledger Enterprise does not support sponsored fees on any network.** One Account cannot pay another Account's transaction fee here, even where the network itself allows it. ## Where fees appear

Where	What is shown
The send form	The fee, with its countervalue, refreshed every 15 seconds
The details view	The buffer, the estimated base fee, and the network's own extra fee where they apply
The Request	The same fields as the details view when available
The Ledger device	The fee, and the network's own extra fields
Operation history	The actual transaction fee paid

Fees are not shown in the operations list, only on an individual operation. ## Related * [**Sending assets**](/help-center-v2/guides/transactions/sending-assets.md) * [**Networks**](/help-center-v2/reference/networks.md) * [**Statuses and errors**](/help-center-v2/reference/statuses-and-errors.md) * [**Limits**](/help-center-v2/reference/limits.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.enterprise.ledger.com/help-center-v2/reference/transaction-fees.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.