> 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-55.02/commander-55.02.14-release-notes/whats-new-in-release-55.02.13.md).

# What's New in Release: 55.02.13

<h2 align="center">Release Summary</h2>

This release corrects the Help > About component information in the Commander Configuration Client and no longer installs empty modules. It also fixes loyalty price-per-gallon discounts on Mobile fuel prepays, and blank menu keys with no linked PLU no longer appear on the POS. A recent FEP Specific change to EBT void handling has been reverted, so voids of mixed EBT and non-eligible items behave as they did before.

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

### Commander Configuration Client

The Profile FCC shown in the Commander Configuration Client under Help > About was incorrect or missing for several distributions. These problems stemmed from incorrect component definitions and dependencies in the distribution configuration files. The definitions have been corrected so the proper component information is displayed and unnecessary empty modules are no longer installed. (138442)

### Loyalty

When an inside fuel prepay was tendered to a Mobile payment method, the site-level loyalty price-per-gallon discount was not applied and the pump price was not rolled back. The POS also displayed an unexpected "Payment not needed" message during this flow. This was corrected so that loyalty discounts apply correctly to mobile fuel prepay transactions. (141658)

### Sales

After upgrading, some menu keys that were not linked to a PLU in the imported back office data appeared on the POS as blank, non-functional buttons. This was caused by an earlier change that removed a check which previously hid such keys. The check has been restored for unassigned keys, so blank buttons no longer appear while items with valid prices and images continue to display correctly. (140833)

<h2 align="center">FEP Specific Change</h2>

### Rapid Connect FEP

#### Resolution

A recent change to EBT void handling has been reverted. Fiserv was declining the reversal (TOR) sent when an EBT item and a non-eligible item were voided together. EBT voids now behave as they did before that change. (142310)


---

# 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-55.02/commander-55.02.14-release-notes/whats-new-in-release-55.02.13.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.
