> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/feature-references/features-and-products-references/receipt-reprint/using-receipt-reprint/receipt-preview-functionality.md).

# Receipt Preview Functionality

The transaction list will be sorted in reverse chronological order, with the most recent entry highlighted. A graphic representation of the receipt will appear for the preview.

Each entry includes the date and time, register, transaction type, amount, fuel information and transaction detail.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/uzZVDRYBx1GbenmB0enm/images/rendered_004.png)

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2F1ig8U8vBB3SB7nG0E8pj%2Fimage.png?alt=media&amp;token=31ccef10-7062-4979-9aa7-26e7fad8e2d5" alt=""><figcaption></figcaption></figure>

If the receipt is longer than what can be displayed on the screen, there are page up/page down options for the user to select to scroll through the receipt preview.

{% hint style="info" %}
The page up/page down options only apply to the graphic preview that is on the screen.
{% endhint %}

The user may touch another entry found in the transaction list to view it.

The selected entry may be printed by touching the Reprint button or by pressing **\[ENTER]**.


---

# 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.verifone.com/feature-references/features-and-products-references/receipt-reprint/using-receipt-reprint/receipt-preview-functionality.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.
