> For the complete documentation index, see [llms.txt](https://docs.revelator.com/pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revelator.com/pro/getting-started/account-settings/payee-settings.md).

# Payee Settings

**Description**

Payee Settings are used to configure the financial information necessary for processing payments and reporting.

**Steps**

1. Access **Account > Payee Settings**.
2. Set the **Type** to either **Company** or **Individual**.
3. Enter the **Payee Name** and select the **Tax Domicile Country**.
4. Add the **Tax ID** and **VAT Number** if applicable.
5. Choose the **Default Payment Method**.
6. Set the **Statements** email for payment notifications.
7. Click **Save**.

### Payee Details

**Description**

The Payee Details page displays the payment information saved by the payor, including the payee ID and payout currency.

**Steps**

1. Go to **Account > Payee Details**.
2. Review the following information:
   * **Payee Name**
   * **Payee ID**
   * **Payout Currency**
   * **Payment Threshold**
   * **Payee Vendor ID**


---

# 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.revelator.com/pro/getting-started/account-settings/payee-settings.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.