> For the complete documentation index, see [llms.txt](https://support.kea.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.kea.ai/kea-pay-fees.md).

# Kea Pay Fees

Just like your point-of-sale, we collect merchant fees on each transaction. kea AI believes in transparency and passes the effective rate we get from our service provider, Stripe. The merchant service fee is set to 2.9% + $0.30 per transaction. With this rate you get the most secure and trusted payment collection with minimal to no disruptions and industry leading digital payment methods like Apple & Google Pay.

Each transaction & payouts reflects this deducted merchant fee when transferred to your respective bank account. To process transactions through your merchant of record, set the payment setting to Pay-on-arrival. This allows you to process payment through your native point-of-sale and the merchant fees you have set.

Want to offset merchant fees? Learn more about applying a Service Fee to kea Pay orders [**here**](/add-service-fee-to-kea-ai-orders.md).

**Have any further questions on payments and processing? Feel free to contact our support team here via SMS or Call:  📲** [**(650) 709-2993**](sms:+16507092993)


---

# 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://support.kea.ai/kea-pay-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.