# What's New In Release: 54.02.03

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

### Verifone C18 Self Checkout <a href="#bookmark210" id="bookmark210"></a>

During a Verifone Self Checkout fuel prepay and the default price level was set to Credit and then the customer paid with cash MOP, an incorrect price level was given. This was corrected.

### Verifone Configuration Client

When apostrophes, slashes, or double quotes were used in a category name, the information was missing from the category configuration. This was corrected and double quotes and slashes cannot be used in the name, but apostrophes are allowed.

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

Improvements were added to the POS Pairing feature to assist with Helpdesk troubleshooting efforts.

### Reports <a href="#bookmark24" id="bookmark24"></a>

Taxes were not displaying in the Tax Reports when the tax name size was more than 10 characters and included a special character. This was corrected and the tax name will be truncated in the report if it has more than 10 characters.

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

### Phillips 66 FEP

#### Resolution <a href="#bookmark27" id="bookmark27"></a>

The preauthorization was not matching the WEX card number provided in the completion message. This resulted in a transaction posting to a terminated card. Also, Fallback transactions were not displaying an odometer for the preauthorization and the Driver and Vehicle number was not matching between preauthorization and completion messages. These were corrected.

### &#x20;VAPS FEP

#### Resolution <a href="#bookmark29" id="bookmark29"></a>

The preauthorization was not matching the WEX card number provided in the completion message. This resulted in a transaction posting to a terminated card. Also, Fallback transactions were not displaying an odometer for the preauthorization and the Driver and Vehicle number was not matching between preauthorization and completion messages. These were corrected.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-and-integrated-pos/commander-release-notes/verifone-commander-release-54.02.03/whats-new-in-release-54.02.03.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.