# What’s New In Release: 55.02.05

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

### Dispensers <a href="#bookmark59" id="bookmark59"></a>

#### Host-based Grade Restrictions

Improvements have been made to enforcing a host-based grade restriction at the dispenser. If the EPS or the host does not authorize all the grades, but more than one grade is on the dispenser, the DCR will display the grade selection prompt. Under any circumstances, customer will not be able to dispense an ineligible grade.

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

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

1. On Wayne Anthem DCRs, the prompt “WPF:999: displayed immediately before “Transaction canceled” due to a card being declined. This was corrected and now the DCR displays “Authorizing”, “Transaction canceled”, and then “Declined.”
2. After an auto upgrade, the DCR was only displaying “Press Payment Key” and no other buttons or graphics. This was corrected and now the DCR displays the correct configuration after an auto upgrade.
3. There were intermittent issues with cards clamping on Wayne DCRs for an extended period of time and then they were declined. If the cards were re-inserted, the sale went through successfully. This was due to an occasional event message received from Wayne during chip card processing that was not processed before the next event message was received. This was corrected by adding a small 10 millisecond time delay for only event messages received from Wayne.
4. Since the required Gilbarco Veeder-Root (GVR) M7 firmware has not been released to production for the support of the GVR Offline Plain Text PIN, the DCRs were rebooting when a chip card was used. This was corrected by backing out the changes for the support of the GVR Sunset Offline Plain Text PIN.

&#x20;

### EPS System <a href="#bookmark62" id="bookmark62"></a>

1. Credit cards were processed after a decline at the DCR. The DCR displayed Decline, quickly displayed “Enter Data” prompt followed by a car wash prompt and then the customer was able to fuel. This was corrected and now the card will be prevented from being processed after a decline.
2. A generic declined message displayed on the PIN pad and DCR in a Verifone Commander EF environment when there was no matching card data found during the initial payment processing. This was corrected and now the track data from the unsuccessful transaction is sent back to the POS/OPT system. This allows the system to initiate a secondary (AUX) payment processing method, potentially leading to a successful transaction without displaying the initial decline message to the user.
3. POS was sending an EMV initialization to the PIN pad via the EPS when the cashier switched between CSR and return options and then initiated a transaction. It also caused the PIN pad to “Processing please wait” stage. This was corrected and now the EMV initialization is not sent.
4. Intermittently, a network transaction was not journaled in the T-Log or Network Journal. This was corrected and now it is journaled.

### Loyalty <a href="#bookmark63" id="bookmark63"></a>

After applying the loyalty discount and a NAXML discount added, the item line price was going into the negative due to the loyalty discount. As a result, the tax was calculated on a negative price causing the overall transaction amount to become negative. This was corrected to ensure that the line item price never falls below zero.

### Mobile <a href="#bookmark64" id="bookmark64"></a>

When there was a POP Discount for fuel in a mobile transaction using a proprietary card, only a portion of the discount was applied locally. This was corrected.

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

On Releases 55.02 and higher, PLUs or departments could not be imported from a backup with Auto Upgrade if a PLU or department number had zero(s). The workaround was to open the XML and delete the invalid “zero” entry and then save it. This was corrected. However, restoration of this data will not be allowed, and the process will continue with the remaining PLUs and departments.

### Sales <a href="#bookmark66" id="bookmark66"></a>

Occasionally, the cashier mistakenly entered a value for the charity amount via the virtual keyboard causing an issue with the charitable donation. This was corrected and now the cashier can only cancel the charity prompt using the keyboard or the on-screen CANCEL button, ensuring the donation is only entered on the PIN pad.

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

### Chase FEP

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

The Chase card table included manual entries for PCI-compliant card types. This was corrected and those entries have been removed.

### Chevron FEP <a href="#bookmark70" id="bookmark70"></a>

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

When “No” was selected at the loyalty rewards prompt inside on the POS or PIN pad, the entire transaction was canceled. When the loyalty ID was entered and whether it was valid or not, the transaction was declined. Also, on the PIN pad, if cancel was selected on the pad or screen, the transaction was declined. This was corrected by adding a validation for this scenario.

### Phillips 66 FEP <a href="#bookmark72" id="bookmark72"></a>

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

1. The Phillips 66 Configuration was not being retained after an Auto Upgrade if the site was on Verifone Commander 55.02.00, 55.02.01, 55.02.02, 55.02.03 and 56.00.00 versions. This was corrected by updating the Backup Data script to add the configurations present.
2. POS was displaying “EPS is busy” message when processing a network transaction. This was corrected and now the network transaction continues as expected.

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

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

Sites using Datawire for Fiserv connectivity were displaying the echo test admin message. This was corrected and the echo admin message no longer displays for Datawire configured sites.


---

# 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-55.02.08/whats-new-in-release-55.02.05.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.