> For the complete documentation index, see [llms.txt](https://docs.offblocks.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.offblocks.xyz/developer-guides/api-integration/fees.md). # Fees In order to ensure smooth operation of our services and transaction flow across blockchain and payment networks, we need to collect and pay fees. These include but are not limited to gas fees on blockchains, off-ramping fees and banking partner fees. Some of these fees are included in our monthly operations fees, however some of them are collected on a per-transaction basis and are subject to fluctuation due to various factors. You may choose to relay those fees entirely onto the customer, or sponsor certain fees. You may also choose to add your own monetisation stream by collecting transaction fees from your customers. Every transaction contains a set of collected fees which are included as part of total settled amount. A fee object can be either of three types: * `partner` - a fee collected based on your monetisation settings * `service` - a fee paid to our service partners in order to facilitate the transaction. This may include any off-ramping or banking fees * `network` - a gas fee collected by the blockchain to process all related transactions --- # 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://docs.offblocks.xyz/developer-guides/api-integration/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.