> For the complete documentation index, see [llms.txt](https://docs.exoclick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exoclick.com/publishers/payments/publisher-payments.md).
# Payments Tab
In the **Payments** tab, you can see how your payments are configured and the history of payments you have already received.
## The Payment Information section
In the **Payment Information** section at the top of the screen you can see:
* **The Account Status**: Whether your account is approved or not.
* **Minimum Payout**: This is the threshold amount above which the Publisher will get a payout.
* **Payment Frequency**: Whether automatic payments\* generate invoices **Weekly** or **Monthly**
* **Next Payment Date**: The next date that you are due to receive payment.
* **Next Payment Period**: The period that your next payment will cover.
* **Due on Next Period**: The amount that is due on your next payment.
* **Total Due**: The total that you are due to receive.
\*Automatic payments will generate invoices automatically on a **Weekly** or **Monthly** basis and as chosen by the Publisher.
## Payment History
In the **Payment History** section at the bottom of the screen, you can see the history of the payments you have received:
* **Period**: The period covered by the payment.
* **Amount**: The amount of the payment.
* **Referrals**: The amount of revenue you have received from **Referrals**.
* **VAT**: Any VAT you paid on the payment.
* **Total**: The Total amount of the payment including VAT.
* **Date**: The date the invoice was generated.
* **Due Date**: The date the invoice is expected to be paid by.
* **Payment Date**: The date of the invoice’s payment.
* **Status**: Whether the payment is **Paid** or **Pending**.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.exoclick.com/publishers/payments/publisher-payments.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.