> For the complete documentation index, see [llms.txt](https://docs.zenfinder.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zenfinder.ai/getting-started/stripe-connect-and-revenue-share.md).

# Stripe Connect & Revenue Share

During partner onboarding we will create and link a **Stripe Connect** account for your organisation. This Stripe account is where your share of transactions will be paid.

* Zenfinder will route revenue-share payouts to the connected Stripe account.
* Partners may be required to complete Stripe-required identity, tax, and business information for payouts to begin.
* Settlement timing (payout frequency and delays) follows Stripe’s policies and your Stripe Connect configuration; please contact <partnerships@zenfinder.ai> or your onboarding lead for exact timing and any hold/payout rules.

Any transactions that are attributed to calls initiated via your platform will be tracked by Zenfinder and included in your revenue share.


---

# 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.zenfinder.ai/getting-started/stripe-connect-and-revenue-share.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.