> 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.12-release-notes/whats-new-in-release-55.02.07.md).

# What’s New In Release: 55.02.07

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

### Dispensers

The Price Sign Controller (PSC) was going offline during a price initialization. Multiple retries of price changes were being done automatically which eventually allowed prices to be updated. This was corrected and now the PSC will not go offline during a price initialization.

### Dispenser Card Readers <a href="#bookmark40" id="bookmark40"></a>

On Verifone Commander version 55.02.04, occasionally when a user entered a correct Driver ID at the DCR prompt quickly, the intended numeric value changed to a alphanumeric causing a decline with error “Invalid PIN Entered” message. If the customer tried the same card again, unknowingly a little slower, the transaction completed as expected. This was corrected and now the alphanumeric characters will only be sent if the Alphanumeric check box is enabled in DCR Keys Configuration.

### Mobile Payment <a href="#bookmark41" id="bookmark41"></a>

Mobile authorizations were failing at the dispenser. This was corrected and now they complete as expected.

### POS System <a href="#bookmark42" id="bookmark42"></a>

Occasionally, some workstations failed to renew POS Pairing prior to auto upgrade, resulting in a failure and need to manually reload the device. This was corrected and now the auto upgrade will detect this situation and prompt the operator to correct the condition before retrying the auto upgrade.

<h2 id="bookmark43" align="center">FEP Specific Changes </h2>

### Rapid Connect FEP <a href="#bookmark44" id="bookmark44"></a>

#### Resolutions <a href="#bookmark45" id="bookmark45"></a>

1. Terminal batch numbers were not incrementing due to a date format issue. This was corrected.
2. Site Asset Data was not sent at the end of the day. This was corrected


---

# 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.12-release-notes/whats-new-in-release-55.02.07.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.