> 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/fleet-cards-general-fuel-configuration-and-usage/configuring-commercial-fleet-cards/configuring-fleet_check-mop.md).

# Configuring Fleet\_Check MOP

Fleet Checks can be exchanged for cash or be used as MOP in a transaction. Go to **Configuration Client > Store Operations > Payment > MOP** tab to configure **Fleet\_Check** MOP.

The driver fills the check and includes the amount they want. Fleet Checks do not have any product restrictions like commercial fleet cards. Fleet Check is like a regular check, but, has to get authorization for the total amount written on the check.

Voids or Refunds of Fleet Checks are not allowed. Assign Fleet\_Check MOP to a POS soft key.

{% stepper %}
{% step %}
Use **33 FLEET\_CHECK** MOP code

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FU5RmHoQ0Uns0oTwOcaE7%2Fimage.png?alt=media&amp;token=b4826f57-00b6-466d-910a-940f2936488c" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Enable “Allow Without Sale”, “Allow Change” and “Allow Refund”

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FLMp5TvkyTduDAIy01i6m%2Fimage.png?alt=media&amp;token=9c0984cd-645b-457b-834d-1e2c49f4c120" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Go to **Configuration Client > Store Operations > Touch Screen > Panel Configuration** to assign Fleet\_Check MOP to a POS soft key.
{% 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://commanderhelp.verifone.com/feature-references/features-and-products-references/fleet-cards-general-fuel-configuration-and-usage/configuring-commercial-fleet-cards/configuring-fleet_check-mop.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.
