> 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/faqs.md).

# FAQ's

### 💸 When do I get paid?

After your event ends, Indinite processes payouts through Stripe. You’ll usually see money in your account in a few business days.

### 💳 How do refunds work?

Refunds (if you allow them) go straight back to the buyer’s original payment method via Stripe.

### 🤷 What if my DJ cancels?

Life happens. Just edit your event details, update the lineup, and re-publish. Attendees will see the new info instantly.

### 📱 Do I need a separate app for check-in?

Nope! Just use the organiser dashboard on your phone. Open the Check-in page, allow camera access, and start scanning tickets.

### 🛑 Can I cancel an event after publishing?

Yes, but think carefully — attendees will get notified, and refunds will apply if tickets were sold


---

# 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/faqs.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.