> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-central/commander-central-user-guide/site-configuration/store-operations/tipping.md).
# Tipping
Tipping is located under C-Site Management > Site Management > (Select Site) > Store Operations. The Verifone Commander now provides flexible tipping options for sites that sell prepared items. The tipping prompt will be displayed on the PIN pad. Preset amounts or percentages for customer selection will be configured in Verifone C-Site Management. The “Prompt for Tip” will be enabled in the department and will apply to all PLUs within that department. Customers will have the option to enter a custom amount. The prompt is customizable.
Navigate to Store Operations > Tipping to view the configuration.
{% hint style="info" %}
Tipping requires Verifone Commander 56.01 release version.
See the Tipping Feature Reference on how to configure the Tipping feature on Verifone C-Site Management.
The Tipping Feature can only be configured on Verifone C-Site Management. It is not available in Verifone Configuration Client.
{% 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://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-central/commander-central-user-guide/site-configuration/store-operations/tipping.md?ask=&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.
