> 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/smart-suggestion/using-smart-suggestion/suggestions-on-the-pin-pad.md).

# Suggestions on the PIN Pad

With the PIN-pad-screen suggestion type configured, the offer is presented to the customer on the payment terminal instead of (or alongside) the cashier screen:

| Scenario on the POS                                                  | Verified Behaviour                                           |
| -------------------------------------------------------------------- | ------------------------------------------------------------ |
| Customer-facing suggestion, sale paid with cash                      | Suggestion renders on the PIN pad; cash tender completes     |
| Suggestion accepted, paid with debit and cash-back                   | Debit and cash-back flow is unaffected by the upsell         |
| Void Line after a PIN pad upsell, paid with debit and cash-back      | Corrections work after PIN pad acceptance                    |
| Different trigger PLUs for the PIN pad offer                         | Rule matching identical to the POS panel                     |
| Customer cancels on the PIN pad / cashier cancels on the POS         | Either side can cancel; transaction continues to tender      |
| Customer declines; verify the prompt dismisses                       | Decline dismisses the PIN pad offer cleanly                  |
| Prepay, postpay, and rest-in-gas fuel sales with PIN pad suggestions | All three fuel flows verified with the customer-facing offer |
| Swipe-ahead disabled and enabled during PIN pad suggestions          | Card swipe-ahead behaviour respected in both configurations  |


---

# 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/smart-suggestion/using-smart-suggestion/suggestions-on-the-pin-pad.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.
