> 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-uk/v200c/how-tos/how-to-submit-offline-transactions.md).

# How to Submit Offline Transactions

Submit stored offline (SAF) transactions from a V200C terminal — steps differ by software version.

{% hint style="info" %}
**Use this when** a V200C terminal has stored offline transactions that need to be sent for authorisation.
{% endhint %}

This guide submits offline (Store and Forward) transactions. The steps depend on your terminal's software version — pick the matching tab below.

{% tabs %}
{% tab title="Version 2.10.0.10 and above" %}
{% hint style="info" %}
You'll need the Supervisor password to complete this process. The default is `12345`. If it has been changed and you don't know it, refer to page 43 of the [Webcom Manual](https://verifone.gitbook.io/uk-help-centre/webcom-manual/).
{% endhint %}

{% stepper %}
{% step %}

### Open the Menu

On the Sale screen after logging in, tap the blue banner at the top of the screen.
{% endstep %}

{% step %}

### Open the Supervisor Menu

Select `Supervisor` and enter your Supervisor password.
{% endstep %}

{% step %}

### Go to SAF Diagnostics

Select `SAF Diagnostics`.
{% endstep %}

{% step %}

### Send Offline Transactions

Select `Send Offline Transactions`. If there are no offline transactions, the terminal tells you. If there are, they're submitted automatically.
{% endstep %}
{% endstepper %}
{% endtab %}

{% tab title="Below version 2.10.0.10" %}
On older software, SAF Diagnostics isn't available, so offline transactions are submitted at login instead.

{% stepper %}
{% step %}

### Check the network connection

Make sure the terminal is connected to the network. If needed, [restart the network interface](https://docs.verifone.com/support-uk/v200c/how-tos/how-to-restart-the-network-interface.md) first.
{% endstep %}

{% step %}

### Log in

Log in to the terminal. This triggers any stored offline transactions to be submitted.
{% endstep %}

{% step %}

### Update for manual submission

To get access to SAF Diagnostics for manual submission, update the terminal to version 2.10.0.10 or above. Refer to page 33 of the [Webcom Manual](https://verifone.gitbook.io/uk-help-centre/webcom-manual/) to schedule a software update.
{% endstep %}
{% endstepper %}
{% endtab %}
{% endtabs %}

<details>

<summary>Keywords</summary>

Also called: submit offline transactions, SAF, store and forward, send offline, SAF diagnostics, stored offline report. Search terms: offline, SAF, store and forward, stored transactions, send offline, saf diagnostics, version.

</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-uk/v200c/how-tos/how-to-submit-offline-transactions.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.
