> 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/t650-two-piece/how-tos/how-to-check-the-last-transaction-information.md).
# How to Check the Last Transaction Information
Check and print the status of the most recent transaction on a T650 Two-Piece (T650C).
{% hint style="info" %}
**Use this when** you need to check or print the details of the most recent transaction — for example, to confirm whether a payment was approved.
{% endhint %}
You check the last transaction on the **T650C** — it includes payments your customer made on the P400.
## Check the last transaction
{% stepper %}
{% step %}
### Open the App Launcher
On the T650C, slide down on the payment screen from the top, then tap the **9-box grid** symbol at the top next to the Wi-Fi icon.
{% endstep %}
{% step %}
### Open Diagnostics
Select **Diagnostics**.
{% endstep %}
{% step %}
### Open Last Transaction Info
Select **Last Transaction Info**. You'll see the details of the most recent transaction, including whether it was approved or declined.
You can also print the last transaction if needed.
{% endstep %}
{% endstepper %}
Keywords
Also called: last transaction, last transaction info, last txn, reprint last transaction, transaction status, did it go through. Search terms: last transaction, last transaction info, transaction status, approved, declined, print last transaction.
---
# 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/t650-two-piece/how-tos/how-to-check-the-last-transaction-information.md?ask=&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.
