> For the complete documentation index, see [llms.txt](https://docs.payrexx.com/merchant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payrexx.com/merchant/english/account/payments.md).

# Payments

In this chapter, you will learn everything about the transaction overview and the different types of payments in Payrexx: One-time payments, subscriptions, pre-authorizations, and tokenizations.

Click on the desired card to learn what this area of your Payrexx account includes and how you can best utilize it:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><a href="/merchant/english/account/payments/transaction-overview.md">Transaction Overview</a></td><td>Overview of all transactions in Payrexx</td><td></td><td></td></tr><tr><td><a href="/merchant/english/account/payments/transaction-details.md">Transactions</a></td><td>Transaction history listing all transactions</td><td></td><td></td></tr><tr><td><a href="/merchant/english/account/payments/subscriptions.md">Subscriptions</a></td><td>List of all subscriptions (recurring payments)</td><td></td><td></td></tr><tr><td><a href="/merchant/english/account/payments/pre-authorizations.md">Pre-authorizations</a></td><td>All charged and uncharged reservations</td><td></td><td></td></tr><tr><td><a href="/merchant/english/account/payments/tokenizations.md">Tokenizations</a></td><td>List of all payments ready for charge</td><td></td><td></td></tr><tr><td><a href="/merchant/english/payment/disputes.md">Disputes</a></td><td>Overview of current and past disputes</td><td></td><td><a href="/merchant/english/payment/disputes.md">Disputes</a></td></tr><tr><td><a href="/merchant/english/account/payments/export.md">Transaction Exports</a></td><td>Exporting transactions to Excel or CSV files</td><td></td><td></td></tr></tbody></table>

## Related Topics

For additional resources on the "Payment" topic, please refer to the following articles:

### Functionalities

If you are looking for general information about the various payment functionalities, the following link will help you:

{% content-ref url="/pages/-McP6jn8wzdkQZ6usQqE" %}
[Functionalities](/merchant/english/payment/functionalities.md)
{% endcontent-ref %}

### Payment Status

An overview of all payment statuses can be found at the following link:

{% content-ref url="/pages/2Wwrfd29tECxcla4NCT7" %}
[Payment Status](/merchant/english/payment/payment-status.md)
{% endcontent-ref %}

### Test Payments

For more information about "Test Payments", please click on the following link:

{% content-ref url="/pages/-MdNTXs1Cj\_H0MnJqHLN" %}
[Testing](/merchant/english/payment/testing.md)
{% endcontent-ref %}


---

# 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.payrexx.com/merchant/english/account/payments.md?ask=<question>&goal=<user_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.