> For the complete documentation index, see [llms.txt](https://support.trybit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.trybit.com/general-information/fees.md).
# Fees
Trybit's fee amounts, individual terms, and payment configuration options.
Trybit uses a transparent fee model: three types of charges affecting the final amount, and full flexibility in who pays them — the client or the merchant.
### Trybit service fee
Charged on all incoming payments — the standard rate is 1.9%.
{% hint style="info" %}
Individual terms are available for projects with growing turnover — the fee can be reduced, down to as low as 0.4%. Exact terms for high turnover are clarified in the support chat.
{% endhint %}
### Transfer fee
A separate fee charged when paying invoices via transfer to a wallet address on the Tron and Ethereum networks — it's needed to aggregate incoming payments to the merchant's main address:
* Tron — fixed, 1.4 USD;
* Ethereum — dynamic, depending on current network load.
No transfer fee is charged for other supported currencies and networks. The transfer fee is also not charged when paying via a Web3 wallet or WalletConnect — regardless of the network (more on payment methods on the [Payment Page](/payments/payment-page.md) page).
### Network fee
The blockchain's own fee for confirming a transaction. It is not included in the invoice amount, since the service doesn't know in advance which wallet or exchange the payment will be sent from — the payer covers it independently when sending.
If the client didn't account for the network fee and a smaller amount than stated on the invoice arrived, the invoice receives the "Partially Paid" status — more details in the [Invoice Statuses](/payments/invoice-statuses.md) section.
When withdrawing funds, the merchant pays the network fee at the time of withdrawal — the withdrawal service itself is free (0%).
### Can the fee be passed on to the payer
Yes. In the [project settings](/getting-started/project-settings.md), you can choose who pays the service fee and the transfer fee — the client or the merchant:
* **client pays** — the fee is added on top of the invoice amount;
* **merchant pays** — the fee is deducted from the amount credited to the balance.
This same setting affects the minimum invoice amount — more details in the [Currencies, Networks and Limits](/general-information/currencies-networks.md) section.
### Connection and maintenance fees
Connecting to Trybit and using the personal dashboard are free. There is no monthly maintenance fee: the service earns only on the fee from incoming payments.
{% hint style="success" icon="lightbulb" %}
Not sure where to start? Use the knowledge base search (🔍the search icon in the page header) — it's often faster than browsing manually, especially given the volume of material.
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://support.trybit.com/general-information/fees.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
