> 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/shell-card-pricing/using-shell-card-pricing/prepay-transactions.md).

# Prepay Transactions

**Amount Prepay**

If the transaction is tendered by cash, the customer dispenses fuel at the cash fuel price level at the pump. If the transaction is paid by credit, the customer dispenses fuel at the fuel price level configured for the card type (e.g. debit cards can either be configured at cash or credit price level).

**Volume Prepay**

For volume prepays, the cashier must select a fuel grade and a fuel price level when they ring up the fuel prepay.

When the Ignore MOP Conflict parameter is enabled (or checked) in Forecourt > Fuel > Site Parameters, sales can be tendered using any MOP regardless of the fuel price level of the MOP.

When this parameter is not enabled (or not checked) and if the transaction is tendered by cash, the MOP entered must be at cash price level.

If the transaction is paid by credit, the price level configured for the card type should also be credit.

If there is a price level conflict, then an error message appears indicating "MOP Conflict".

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2Fz5fcy77eiewWTlDTiKxH%2Fimage.png?alt=media&amp;token=e5e30efc-050f-4411-b393-69246f024037" alt=""><figcaption></figcaption></figure>


---

# 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/shell-card-pricing/using-shell-card-pricing/prepay-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.
