> 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/feature-references/features-and-products-references/orpak-avi-rfid-fueling/appendix/handle-up-calling.md).

# Handle Up Calling

This section describes the system behavior when the POS is configured for a ***“call in”*** from the dispenser to the POS workstation. The dispenser call in begins when a dispenser handle is lifted. The POS workstation produces both an audible and visual alert indicating that a dispenser is calling in for authorization. The cashier can then authorize the dispenser by pressing a key on the workstation.

## Card Takeover Enabled

Precondition: The system is configured to allow payment information to be presented at the DCR after the dispenser has been approved for fueling by the cashier (Card Takeover Enabled).

***Scenario 1: Cashier authorizes fueling prior to customer placing nozzle in fuel tank.***

{% stepper %}
{% step %}
**Raise Handle**

The customer raises the handle on dispenser.
{% endstep %}

{% step %}
**Alert Cashier**

The POS alerts the cashier of the pump calling in for authorization.
{% endstep %}

{% step %}
**Approve Dispenser**

The cashier approves the dispenser for fueling.
{% endstep %}

{% step %}
**Place Nozzle**

The customer places the nozzle in the tank.
{% endstep %}

{% step %}
**Receive Payment Information**

The POS receives payment information from the MWGT.
{% endstep %}

{% step %}
**Fuel and Hang Up**

The customer dispenses the fuel and hangs up the nozzle.
{% endstep %}
{% endstepper %}

***Scenario 2: Cashier authorizes fueling after customer places nozzle in fuel tank.***

{% stepper %}
{% step %}
**Raise Handle**

The customer raises the handle on the dispenser.
{% endstep %}

{% step %}
**Alert Cashier**

The POS alerts the cashier of the fueling authorization request.
{% endstep %}

{% step %}
**Place Nozzle**

The customer places the nozzle in the tank.
{% endstep %}

{% step %}
**Receive Payment Information**

The POS receives payment information from the MWGT.
{% endstep %}

{% step %}
**Approve Fueling**

The POS approves the dispenser for fueling.
{% endstep %}

{% step %}
**Disable Cashier Approval**

The POS disables the cashier approval of the dispenser.
{% endstep %}

{% step %}
**Fuel and Hang Up**

The customer dispenses the fuel and hangs up the nozzle.
{% endstep %}
{% endstepper %}


---

# 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/feature-references/features-and-products-references/orpak-avi-rfid-fueling/appendix/handle-up-calling.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.
