> 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.14.md).

# What's New in Release: 55.02.14

<h2 align="center">New Features and Enhancements</h2>

### Verifone Commander Central

#### CWM Component Label Rename

Commander Weights & Measures (CWM) was shown simply as “CWM” in Help > About, which did not match the labeling that Weights & Measures requirements call for. The component is now labeled “Metrological Software Version” in Help > About on the POS and Commander Configuration Client. (143346)

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

### POS System

1. After a sale ended on a POS with device monitoring enabled, the POS could stop responding to taps for about a minute if the Commander’s monitoring connection was unavailable. The POS now handles this in the background, so it keeps responding to taps. (143636)
2. After a card was approved at a kiosk, Commander could hit an error while finishing the sale and report a failure to the kiosk, which then resent the sale and charged the customer’s card a second time. Commander now completes the sale correctly in this situation, so the kiosk no longer resends it. If an unfinished earlier transaction cannot be cleared when a new session starts, Commander now reports that error instead of silently continuing. (142241)
3. When the Commander’s monitoring connection was unavailable, Self Checkout (SCO) could take minutes to start, load its menu keys slowly and ignore taps. SCO no longer waits on that connection at startup. It retries in the background every 10 seconds and sends its latest status once it reconnects, so it starts quickly and responds normally even while the connection is down. (141967)

### Sales

Refunds to a Credit or Debit method of payment could fail with the error “E1151 TICKET TOTALS ZERO - Press CASH” when “Allow zero entry” was disabled for those payment methods, leaving Cash as the only option for the refund. Credit and Debit refunds now process normally. (143339)

<h3 align="center">FEP Specific Changes</h3>

### Rapid Connect FEP

#### Resolution

Some EBT cards could be misidentified, for example a Food Stamp card treated as a Cash Benefit card, which could cause the transaction to fail. The Buypass card table now lists the individual EBT card ranges instead of one broad range. The POS also now asks for the EBT type (Food Stamp or Cash Benefit) when a card falls in an EBT range or can’t be clearly identified. (143177)


---

# 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.14.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.
