> 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/full-service-attendant/using-full-service-attendant/cash-price-level.md).

# Cash Price Level

1. The customer pulls up to the pump for cash fueling, and the attendant swipes an assigned FSA card for authorization at the DCR.
2. The DCR prompts for the cash level pricing amount.
3. The attendant enters the cash for fueling.\
   **Note:** *If the attendant skips this prompt, a requested amount of zero dollars will be sent to the FEP.*
4. The FSA card data and requested transaction amount is transferred to VIPER, where it is captured by the Full Service Attendant FEP.
5. The request is received by the FEP and processed locally, depending on the limit mentioned for that FSA card.\
   **Note:** *Full Service Attendant has its own card related configuration FullServiceAttendant\_CardTable which holds the card Ranges.*
6. The FEP sends the pre-authorized amount back to the DCR. The pump is equipped with the approval of that amount only.
7. The attendant pumps the fuel for the approved amount, and receives payment from the customer in cash.
8. After concluding the fueling stage, a completion request is sent by the DCR to VIPER where the transaction totals are updated.

{% hint style="info" %}
Alternately, the customer can directly swipe the payment card without involving the attendant. In this case, depending on the Price Tier returned from the EPS, the pump can either be authorized for the Credit or Cash Price Level.
{% endhint %}


---

# 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/full-service-attendant/using-full-service-attendant/cash-price-level.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.
