> For the complete documentation index, see [llms.txt](https://mtrsolution.gitbook.io/eventic/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mtrsolution.gitbook.io/eventic/payouts/the-payout-request-process.md).

# The payout request process

In this section, we are going to highlight the payout process, from its request, to its approval

## Definition

A payout is requested by an organizer in order to receive his revenue for a specific event date.

## Conditions

A payout can only be requested if:

* At least one payout method is already set by the organizer
* The event date has a ticket that is not free
* The organizer revenue from this event date is greater than zero
* There is no other pending payout request

## How is a payout requested in Eventic?

![](/files/-MJMUD5GIyODciXLtJbw)

1. Organizers go the My events section in their dashboard
2. Select the three points next to the event, and choose Request payout
3. Choose the specific event date 
4. Review the payout request details, choose a payment method from the ones you have set up and confirm
5. The administrator can approve the payout request or deny it
6. A payment form depending on the payment method chosen by the organizer will open, the administrator will fill in the fields to pay the organizer
7. Email notification are sent once the payout request is processed

{% hint style="info" %}
Once the payout request submitted, the event date will be locked and the sales will be suspended for the specific event date. Organizers can wait until the start date of the event date before requesting the payout. Organizers can cancel the payout request any time before it is processed.
{% endhint %}

{% hint style="info" %}
The administrator can enable or disable the available payout method the Payment settings
{% endhint %}


---

# 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://mtrsolution.gitbook.io/eventic/payouts/the-payout-request-process.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.