> 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/support-nordics/victa/how-tos/how-to-check-the-last-transaction-information.md).

# How to Check the Last Transaction Information

See the details of the most recent transaction on your Victa.

{% hint style="info" %}
**Use this when** you need to check the result of the most recent transaction — for example, if a payment was interrupted.
{% endhint %}

{% stepper %}
{% step %}

### Open Diagnostics

1. Open the app list: swipe **up** on the home screen. If your Victa opens straight into **Connect Express**, swipe **down** from the top of the screen and tap the **settings icon** in the bottom-right corner to get to the Android menu.
2. Tap **Diagnostics**.
   {% endstep %}

{% step %}

### Open Last Transaction Info

Tap **Last Transaction Info**. If you're asked for your **PIN code**, enter it — see [How to Set Up a PIN Code](/support-nordics/victa/how-tos/how-to-set-up-a-pin-code.md).
{% endstep %}

{% step %}

### Check the details

Scroll down to see the full transaction details, including whether it was approved. Tap **Print** if you need a copy.
{% endstep %}
{% endstepper %}

<details>

<summary>Keywords</summary>

Also called: last transaction, last transaction info, transaction status. Search terms: last transaction, transaction details, approved, declined, diagnostics, print.

</details>


---

# 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/support-nordics/victa/how-tos/how-to-check-the-last-transaction-information.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.