> For the complete documentation index, see [llms.txt](https://docs.indinite.co.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.indinite.co.uk/money-and-payouts/how-you-get-paid.md).

# How You Get Paid

With Indinite, all your ticket sales flow securely through **Stripe Connect**. To unlock payouts, you’ll first need to complete a quick **KYC (Know Your Customer) verification**. Don’t worry—it’s safe, simple, and only takes a few minutes.

#### 🪄 Steps to Get Paid:

1. **Connect Stripe** – Link your organiser account to Stripe.
2. **Complete KYC** – Add your details (business or personal). Stripe may ask for ID and bank info.
3. **Sell Tickets** – Watch your sales roll in as orders come through.
4. **Get Payouts** – Stripe automatically transfers your share to your bank account.

👉 Until KYC is done, funds will stay pending. So make this your **first pit stop** after signing up as an organiser!


---

# 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.indinite.co.uk/money-and-payouts/how-you-get-paid.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.