> 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/v660p/how-tos/how-to-run-the-saf-diagnostic.md).

# How to Run the SAF Diagnostic

Check and upload stored offline transactions on your V660P with the SAF Diagnostic.

{% hint style="info" %}
**Use this when** you want to check for stored offline transactions and send them — for example, if a guide asks you to run the SAF Diagnostic.
{% endhint %}

{% stepper %}
{% step %}

### Open Diagnostics

1. Open the app list: swipe **up** on the home screen. If your V660P 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 SAF Diagnostics

Tap **SAF Diagnostics**. It shows **Pending**, **Declined**, and **Reversals** — the stored offline transactions on the terminal.
{% endstep %}

{% step %}

### Upload the transactions

If there are stored transactions, tap **Upload Offline Transactions**.
{% endstep %}
{% endstepper %}

<details>

<summary>Keywords</summary>

Also called: SAF diagnostic, store and forward, offline transactions, pending reversals. Search terms: SAF, store and forward, offline, pending, reversals, upload, diagnostics.

</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/v660p/how-tos/how-to-run-the-saf-diagnostic.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.