> 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/coupon-scanning/using-coupon-scanning/transaction-flow/valid-coupon-processing.md).

# Valid Coupon Processing

The cashier must decide if a coupon may be applied to a transaction before scanning it. Once scanned, the system applies valid coupons (non-expired) at the transaction level.

{% hint style="info" %}
The system accepts valid and non-expired coupons only. The system does not check against items in the transaction and also does not impose any item-based restrictions while accepting coupons.
{% endhint %}

{% stepper %}
{% step %}
Enter \<items> into the transaction.
{% endstep %}

{% step %}
Scan the coupon.

* On scanning the first coupon, the prompt displays "SCANNED COUPON - ADDITIONAL ITEMS CANNOT BE ADDED AFTER COUPONS ARE SCANNED. CONTINUE? \[Y/N]."
  * Select \[YES] to go to method-of-payment (MOP) mode to process the coupon.
  * Select \[NO] to go back to subtotal level. The prompt "COUPON NOT PROCESSED" displays and ignores already scanned items.

{% hint style="info" %}
Once a coupon scan has started in a transaction, the user cannot add more items to that transaction. If the user still wants to add a coupon to the same transaction, then the user can scan the coupon or enter the coupon as an MOP.
{% endhint %}

* The system accepts the coupon amount from the coupon, and the coupon amount is applied as a transaction-level amount.
  {% endstep %}

{% step %}
Continue to accept more coupons or tender the transaction.
{% 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/coupon-scanning/using-coupon-scanning/transaction-flow/valid-coupon-processing.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.
