> 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/self-checkout/configuring-self-checkout/hide-show-pay-at-counter.md).

# Hide/Show Pay at Counter

For Verifone Commander maintenance release 55.02.06, release 56.02.xx, and release 56.03.00, a new system property has been added to hide/show the Pay at Counter option at the SCO.

System Parameter **payAtCounter.action** has the options Suspend and Hide. By default, the action is **payAtCounter.action=Suspend**, which will show the Pay at Counter option.

If **payAtCounter.action=Hide**, then the UI will not display the option to Pay at Counter.

The Hide option has been added because some retailers that have Self-Checkout do not want to offer their customers to pay at the counter.

When pay at counter option is enabled, the customer can choose this option, get a suspend ticket, and leave the store with the items without paying. The cashier may not realize this has occurred.

This system property configuration allows sites to disable the Pay at Counter functionality for the following scenarios:

* Help -> Pay at Counter
* After items are in the cart and a new item that is not allowed to be sold is attempted to be added
* PLU not found
* Department not allowed at SCO
* Fractional Quantity items
* Open PLU Items

{% hint style="info" %}
Get in touch with Verifone Support to update payAtCounter.action=Hide.
{% 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/self-checkout/configuring-self-checkout/hide-show-pay-at-counter.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.
