> For the complete documentation index, see [llms.txt](https://helpcenter.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.verifone.com/p400-how-tos/submit-offline-transactions.md).

# Submit Offline Transactions

<mark style="color:$danger;">**For Terminals on Version 2.10.0.10 and Above**</mark>

1. **Access the Sale Screen** \
   After logging in, go to the Sale screen.
2. **Open the Menu** \
   Tap the blue banner at the top of the screen.
3. **Go to Supervisor Menu** \
   Select Supervisor and enter the password (default is 12345, unless changed). If you have amended this please refer to <mark style="color:purple;">page 43</mark> on the [Webcom Manual](/webcom-manual/webcom-manual.md).
4. **Go to SAF Diagnostics** \
   Select SAF Diagnostics.
5. **Send Offline Transactions** \
   Select Send Offline Transactions.

If there are no offline transactions, the device will notify you. If there are offline transactions, they will be submitted automatically.

***

<mark style="color:$danger;">**For Terminals Below Version 2.10.0.10**</mark>

1. **Check Network Connection** \
   Ensure the terminal is connected to the network ([Restart the network interface](/p400-how-tos/restart-network-interface.md) if needed).
2. **Attempt Login** \
   Log in to the terminal. This will trigger any stored offline transactions to be submitted.
3. **Update Terminal** \
   To access SAF Diagnostics for manual submission, update your terminal to version 2.10.0.10 or above.  Please refer to <mark style="color:purple;">page 33</mark> on the [Webcom Manual](/webcom-manual/webcom-manual.md) to schedule a software update on the terminal.

#### [<mark style="color:$success;">Back to P400 - How To Guides</mark>](/p400-how-tos/p400-how-to-guides.md#p400-how-to-guides)


---

# 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://helpcenter.verifone.com/p400-how-tos/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.