> For the complete documentation index, see [llms.txt](https://help.autobuy.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.autobuy.io/general-faq/autobuys-fees.md).

# AutoBuy's Fees

 AutoBuy.IO is an all in one payment processing and e-commerce solution. Whether you are selling digital goods, game items, or even software, AutoBuy gives you a platform to accept payments, send out orders, manage support tickets, and more. On top of any fees that the payment processor (PayPal or Stripe) may have, AutoBuy.IO also has a flat **3% fee** on transactions. This is withdrawn automatically and can be viewed on a seller's order details.

The table below breaks down any fees on AutoBuy.

| Processor      | Fees                |
| -------------- | ------------------- |
| PayPal         | 3% + gateway fees.  |
| Stripe         | 3% + gateway fees.  |
| Cryptocurrency | 3% + handling fees. |

*Please Note: While we move our systems to another cryptocurrency partner Bitcoin withdrawals will have a fee of 0.0004 BTC. We do not have an eta on when this will be complete.*


---

# 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.autobuy.io/general-faq/autobuys-fees.md?ask=<question>&goal=<endgoal>
```

`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.