> 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/pos/tutorials-newland-terminals/managing-transactions.md).

# Managing Transactions

In the following guide, you will learn how to print payment receipts and process refunds on your Newland card terminal.

## Contents

1. [Viewing payment reports](#viewing-payment-reports)
2. [Last receipt copy](#last-receipt-copy)

### Viewing payment reports

The transaction history of your POS terminal provides an overview of all processed payments. To access this overview, proceed as follows:

* Click the icon in the top right corner of the screen to open the main menu, and then select **Reports**.

#### TWINT payment report

Click the TWINT icon and configure the following settings in the next window:

<div align="left"><figure><img src="https://1455115231-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MYJhU4qriZCz_Wxs0T0-887967055%2Fuploads%2Fm04nop4joc4bHIj3Ccxw%2Fimage.png?alt=media&amp;token=5b3d90cc-875e-4d7a-af1f-9a231745a08a" alt="" width="360"><figcaption><p>Generating a payment report</p></figcaption></figure></div>

1. **Date range:** Define the date range for the payments you want to display in the report.
2. **Time:** Define the time of day for the payments you want to display in the report.
3. **Type:** Choose whether you want to display a summary or a detailed report.
4. **Filter:** Click on "Filter" to generate the report:

<div align="left"><figure><img src="https://1455115231-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MYJhU4qriZCz_Wxs0T0-887967055%2Fuploads%2Ftpfs27m5tcwL1Zuf4SAz%2Fimage.png?alt=media&amp;token=0c42ae63-6d89-4835-aceb-3e830ab90af9" alt="" width="360"><figcaption><p>Summary report of TWINT payments on the screen</p></figcaption></figure></div>

{% hint style="info" %}
The report can either be viewed on the screen or printed.
{% endhint %}

#### Card payment report

* Click the Card icon.
* Choose whether you want to view a summary or a detailed report.
* Click on "Filter" to narrow down the payments displayed in the report by:
  * Date, Time
  * Debit/Credit card
  * Transaction amount

### Last receipt copy

Click the icon in the top right corner of the screen to open the main menu, and then select **Print receipt copy**.

1. Choose whether you want to generate a customer receipt or a merchant receipt.
2. The receipt will be displayed directly on the screen.
3. You can either print or send the receipt:
   1. Select the printer icon to print the receipt directly.
   2. Select the share icon, enter the desired email address, and click "Send" to email the receipt.


---

# 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/pos/tutorials-newland-terminals/managing-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.
