> 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/eps-loyalty/using-eps-loyalty/loyalty-sales-functions/cashier-option-to-cancel-out-of-loyalty-prompt.md).

# Cashier Option to Cancel Out of Loyalty Prompt

From Verifone Commander Release 56.01, added **YES**and **NO**keys to the Loyalty Auth prompt. Pressing the NO prompt will abort the PIN pad prompt.

This feature is focused on addressing the issue of cashier control over the PIN pad when a site is in customer-facing mode. This solves scenarios where customers walk in, inform the cashier of their pump number, drop money on the counter, and leave. These customers are unaware of any necessary actions on the PIN pad. Cashiers need to reach over to cancel loyalty prompts or even walk around to the PIN pad. This inconvenience causes a significant challenge and lacks intuitiveness.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/JzJGROTCNjRLPB2hXWer/Unknown%20image)


---

# 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/eps-loyalty/using-eps-loyalty/loyalty-sales-functions/cashier-option-to-cancel-out-of-loyalty-prompt.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.
