> For the complete documentation index, see [llms.txt](https://docs.aquapay.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquapay.io/features/payments-and-payouts.md).

# Payments and Payouts

## Payments

The Payments page displays a table with all your payments. By default, it shows payments in descending creation order.

![](/files/lcXnqwN092uYcCE3RqE3)

You may choose to sort by a different parameter instead by hovering over any other table header and clicking on the arrow that appears. Clicking it will cycle through sort by ascending, descending, and none/clear sort.

![](/files/rnQPC2O44WX4aAlygafr)

You can also choose to narrow down the table data shown by a date range of your choosing via the Date Range picker above the table.

![](/files/bdVwzju1oz182KQbroOE)

Status is a filter you can utilize to customize your table view. You may select as few or as many statuses you would like to see on the table.

![](/files/8gye3Rdn4rMP3EJaVqFl)

The table updates as you select Status parameters to filter.

![](/files/BGKPgY9Flm7Ag0HwTIoX)

The Payouts page displays a table

![](/files/lCpoLn8vcF9UPrao2jgI)


---

# 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.aquapay.io/features/payments-and-payouts.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.