> 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/mobile-payments/configuring-mobile-payments/configure-mobile-method-of-payment-mop.md).

# Configure Mobile Method of Payment (MOP)

{% hint style="info" %}
New installations have a default Method of Payment and Code configured in the system to accept mobile payments.

If however, the system is upgraded, then the MOP and MOP Code must be configured.

If the site imported the mobile configuration using the Import and Export utility, either on a new install or upgrade, the Mobile MOP and Code will need to be configured manually.
{% endhint %}

{% stepper %}
{% step %}
From the Configuration Client, go to: Store Operations > Payment.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/iQdaPVHb5NfLnvUFsyqv/images/rendered_009.png)

The Payment Management window displays.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/7udthJ5qndcI2lVg7dwB/images/rendered_010.png)
{% endstep %}

{% step %}
From the Payment Management window, select the \[MOP] tab.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/BYMOEalWv6O3HvbE7JPO/images/rendered_011.png)
{% endstep %}

{% step %}
Scroll down the `<Select MOP>` pane to an unconfigured position and configure the Mobile MOP parameters.

<img src="https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/ou7VW8KV7DDrVo53FToI/images/rendered_012.png" alt="" width="375">

| Variable             | Value                                                       |
| -------------------- | ----------------------------------------------------------- |
| Name                 | Enter: MOBILE                                               |
| MOP Code             | Select: 28 - MOBILE                                         |
| Minimum Amount       | Indicates the minimum amount accepted <$0.00-9999.99>.      |
| Maximum Amount       | Indicates the maximum amount accepted <$0.00-9999.99>.      |
| Limit                | Alerts the cashier to the Mobile MOP limit <$0.00-9999.99>. |
| #Additional Receipts | Indicates how many additional receipts are required <0-3>.  |
| Tender Code          | Generic.                                                    |
| Tender Sub Code      | Generic.                                                    |
| {% endstep %}        |                                                             |

{% step %}
Select to enable additional Options parameters.

<img src="https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/QJa2yRW4MVY0xr0JGeAo/images/rendered_013.png" alt="" width="375">

| Variable                   | Value                                                                                                                                               |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| Force Safe Drop            | Enables a safe drop message (if the Limit value is not 0.00).                                                                                       |
| Tender Amount Required     | Requires the clerk to enter an actual (counted) drawer amount before selecting this MOP.                                                            |
| Allow Zero Entry           | Indicates a zero entry is allowed when entering a drawer amount.                                                                                    |
| Allow Refund               | Permits a Refund transaction to be tendered.                                                                                                        |
| Allow Safe Drop            | Allows a safe drop.                                                                                                                                 |
| Force Ticket Print         | Forces a receipt to be printed for transactions that includes this MOP.                                                                             |
| Open Drawer On Sale        | Forces the cash drawer to open when a transaction includes this payment type.                                                                       |
| Cashier Report Prompt      | Prompts a cashier to enter the actual (counted) drawer amount when printing cashier report.                                                         |
| Allow Without Sale         | Permits acceptance without purchase. For example, cashing in a winning lottery ticket or permitting a check to be cashed without a purchase.        |
| Allow Change               | Allows the cashier to make change when "amount > amount due" is selected. For example, if a check can be written for more than the purchase amount. |
| Allow Money Order Purchase | Permits a money order sale.                                                                                                                         |
| {% endstep %}              |                                                                                                                                                     |

{% step %}
Select \[Save] to accept, or \[Cancel] to exit without saving changes.

The setup of the Mobile Method of Payment is complete.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/TR9StLYSfH2hRrOfM4uP/images/rendered_014.png)

{% hint style="info" %}
Log out and back in to all POS terminals after any setting modifications to allow these changes to take effect.
{% endhint %}
{% 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/mobile-payments/configuring-mobile-payments/configure-mobile-method-of-payment-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.
