> 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/cug-57.00/cug-57.00-es/referencia-de-usuario-de-commander-57.00/ventas-de-fidelizacion-eps.md).

# Ventas de fidelización (EPS)

## Resumen

Los programas de fidelización vienen en todas las formas y tamaños. Pueden ofrecer descuentos inmediatos o ahorros futuros mediante incentivos como cupones o puntos para futuras compras.

Las ventas de lealtad EPS permiten el procesamiento y canje de transacciones de lealtad, tanto dentro del POS como fuera en los lectores de tarjetas del dispensador (DCR). Estas transacciones de lealtad se procesan a través del sistema de pago electrónico (EPS).

La funcionalidad del Front End Processor (FEP) de fidelización de EPS incluye el uso de la especificación de host POS-Loyalty de PCATS, el descuento por precio por unidad, el descuento a nivel de transacción y el descuento a nivel de artículo.

{% hint style="info" %}
*Consulte la documentación de referencia de la función Loyalty Sales para obtener información sobre esta función.* 
{% 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/cug-57.00/cug-57.00-es/referencia-de-usuario-de-commander-57.00/ventas-de-fidelizacion-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.