> For the complete documentation index, see [llms.txt](https://docs.payrexx.com/platform/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/platform/english/analytics/transactions.md).

# Transactions

This article covers transaction statistics. Learn where to find reports on the number of transactions, transaction volume, and other valuable insights in Payrexx.

To access the statistics, navigate to **Transactions** in the platform administration of your Payrexx account.

At the top of the window, select the year you want to analyze, specify the year you want to compare it with, and click the button "Show".

In the following example, the year 2024 is compared with the year 2023:

<div align="left"><figure><img src="https://13947520-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McKWr2N1ZENCggMlAH5%2Fuploads%2Fqbal7HpXI6lJ9JAq3qP5%2Fimage.png?alt=media&amp;token=27d2b61a-2f14-49a1-aceb-474c73aa3f41" alt=""><figcaption><p>Selection of the year to be displayed and the comparison period</p></figcaption></figure></div>

## Key Metrics for Transactions

In the main section of the window, the following time-related key metrics are displayed:

* Number of transactions by currency
* Transaction volume by currency
* Number of transactions by merchant country
* Transaction volume by merchant country
* Transaction fees


---

# 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/platform/english/analytics/transactions.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.
