> 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/customer-documentation/petro-and-c-store/commander-highlights-user-guides-release-notes-and-certifications/commander-54.02/commander-54.02.05-release-notes/whats-new-in-release-54.02.04.md).

# What's New In Release: 54.02.04

<h2 align="center">Enhancements</h2>

### &#xD;EPS System

#### &#xD;FID Table and Auto Upgrade

The values in the FID (Field Identifier) table will now be retained after an auto upgrade. These values are the location, location address, location city, location state, and location ZIP code.

### &#xD;Loyalty

#### &#xD;Enablement

The “Loyalty Enabled” option in POS Configuration is now read-only. It will accurately display the status indicating whether a loyalty FEP is active based on an automated data exchange with the EPS. Users are restricted from making changes to this field through Verifone Configuration Client or Back Office.

<h2 align="center">Resolutions</h2>

### &#xD;Dispenser Card Readers

VISA Contactless cards were failing at the DCR when using a loyalty card. This was corrected.

### &#xD;Loyalty

When a customer used a loyalty card to purchase fuel at a site with multiple loyalty programs configured, they received a discount message and the discount on purchase. However in some cases, the transaction was never sent to the loyalty host resulting in a shortage on loyalty sales. This was corrected and now the system will ensure that the transaction completion will be sent to the valid loyalty host in all cases.


---

# 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/customer-documentation/petro-and-c-store/commander-highlights-user-guides-release-notes-and-certifications/commander-54.02/commander-54.02.05-release-notes/whats-new-in-release-54.02.04.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.
