> 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/feature-references/features-and-products-references/eps-loyalty/using-eps-loyalty/eps-loyalty-attributes.md).

# EPS loyalty attributes

* Sites can enable both POP Discount and loyalty, but a customer can receive only one discount per transaction.
* After the loyalty card is swiped, VOID LINE and ERROR CORR cannot be used. Use VOID TICKET instead.
* If the network denies the request, a denial message displays. The transaction continues as usual.
* The POS updates loyalty report totals after each transaction.
* From Release 57.02, the customer's loyalty ID (for example, a phone number) is stored masked in the T-Log unless the site turns on storing it in clear. A newly installed system stores it masked.
* A loyalty ID that is also a payment card (a hybrid card), or that is in the format and length of a payment card number, is always stored masked, whatever the setting.


---

# 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/feature-references/features-and-products-references/eps-loyalty/using-eps-loyalty/eps-loyalty-attributes.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.
