> 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/v400m-integrated/how-tos/how-to-check-stored-transaction-data.md).

# How to Check Stored Transaction Data

Check whether your V400M has any stored transactions waiting to be sent.

{% hint style="info" %}
**Use this when** you want to see whether your terminal has any stored transactions — for example, when troubleshooting, or before your terminal is replaced.
{% endhint %}

## Check stored transactions

{% stepper %}
{% step %}

### Open the menu

Press **4** and **6** at the same time, then enter password **1234** and press the **green button**.
{% endstep %}

{% step %}

### Go to Transaction information

Select **Transaction information**.
{% endstep %}

{% step %}

### View stored transactions

Select **Stored Transaction Data**. This shows any transactions stored on the terminal that haven't been sent yet.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**Found stored transactions?** Run a reconciliation to send them — see [How to Run a Reconciliation](/support-nordics/v400m-integrated/how-tos/how-to-run-a-reconciliation.md). If they won't send, see [Offline Transactions](/support-nordics/v400m-integrated/errors/offline-transactions.md).
{% endhint %}

<details>

<summary>Keywords</summary>

Also called: stored transactions, stored transaction data, offline transactions, pending transactions, transaction information. Search terms: stored transactions, transaction information, offline, pending, replace terminal.

</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/v400m-integrated/how-tos/how-to-check-stored-transaction-data.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.