> 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-sweden/v400m/sa-har-gor-du/sa-har-kontrollerar-du-sparade-transaktionsdata.md).

# Så här kontrollerar du sparade transaktionsdata

Så kontrollerar du om det finns lagrade transaktioner som väntar på att skickas från din V400M-terminal.

{% hint style="info" %}
Använd den här guiden när du vill se om terminalen har lagrade transaktioner, till exempel vid felsökning eller innan terminalen byts ut.
{% endhint %}

## Kontrollera lagrade transaktioner steg för steg

{% stepper %}
{% step %}

### Öppna menyn

Tryck på knapparna **4 och 6 samtidigt**, ange lösenordet **1234** och tryck sedan på den gröna knappen.
{% endstep %}

{% step %}

### Gå till Transaktionsinformation

Välj **Transaktionsinformation**.
{% endstep %}

{% step %}

### Visa lagrade transaktioner

Välj **Lagrad transaktionsdata**. Här visas alla transaktioner som är lagrade i terminalen och som ännu inte har skickats.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**Hittade du lagrade transaktioner?** Gör en avstämning för att skicka dem. Följ guiden [Så gör du en avstämning](/support-sweden/v400m/sa-har-gor-du/sa-gor-du-en-avstamning.md). Om transaktionerna inte skickas följer du guiden [Offline-transaktioner](/support-sweden/v400m/fel/offline-transaktioner.md).
{% endhint %}

<details>

<summary>Nyckelord</summary>

Även kallat: lagrade transaktioner, sparade transaktionsdata, offline-transaktioner, väntande transaktioner. Söktermer: lagrade transaktioner, Transaktionsinformation, Lagrad transaktionsdata, offline, väntande, byta terminal, V400M.

</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-sweden/v400m/sa-har-gor-du/sa-har-kontrollerar-du-sparade-transaktionsdata.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.
