> 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/commander-user-reference-guides-1/commander-user-references/commander-user-reference-56.01/loyalty-sales-eps.md).

# Loyalty Sales (EPS)

## Overview

Loyalty programs come in all shapes and sizes. They can offer on-the-spot discounts or future savings through incentives as coupons or points toward future purchases.

EPS loyalty sales allow the processing and redemption of loyalty transactions, both inside at the POS and outside at the dispenser card readers (DCR). These loyalty transactions are processed through the electronic payment system (EPS).

The EPS Loyalty Front End Processor (FEP) functionality include using the PCATS POS-Loyalty Host Specification, Price-per-unit Discounting, Transactions-level Discounting, and Item Level Discounting.

{% hint style="info" %}
*Refer to the Loyalty Sales feature reference documentation for information on this feature.* 
{% 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/commander-user-reference-guides-1/commander-user-references/commander-user-reference-56.01/loyalty-sales-eps.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.