> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/orpak-avi-rfid-fueling/using-orpak-avi-rfid-fueling/fueling-pause-and-resume.md).

# Fueling Pause and Resume

If the VIU data becomes unavailable while fuel is approved for dispensing, Verifone Commander prevents fuel from being dispensed (Fueling Pause). During a Fueling Pause, Verifone Commander displays the **“PUMP STOPPED”** message at the DCR. If the dispenser handle is lowered during a Fueling Pause, Verifone Commander will terminate the transaction.

If fuel dispensing has been prevented (Fueling Pause) for an AVI/RFID transaction, Verifone Commander will prevent the cashier from reapproving the dispenser. There is a limitation in the Tokheim dispenser firmware where a stop command is ignored when it is received within three seconds after a start command is received. Verifone Commander performs a three second delay before issuing a stop command for the Tokheim system to prevent the cashier from reapproving the dispenser. This three second delay will also be observed for all Fueling Pauses with Tokheim dispensers.


---

# 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://commanderhelp.verifone.com/feature-references/features-and-products-references/orpak-avi-rfid-fueling/using-orpak-avi-rfid-fueling/fueling-pause-and-resume.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.
