# What’s New In Release: 55.02.04

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

### POS System

#### System Optimization

By optimizing certain aspects of memory usage, improvements were made to the Verifone Commander performance.

#### <sub>Verifone Commander Software Management Suite (SMS)</sub>

The Verifone Commander Software Management Suite (SMS) 3.00.14 and Import/Export Utility version 3.00.09 will be included in the Verifone Commander 55.02.04 software release.

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

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

1. On Wayne DCRs, “WPF:999” displayed followed by a blank prompt just before the Loyalty Optional prompt. This was corrected and the “WPF;999” message is no longer displayed.
2. The Forecourt Controller (FCC) list of 9F33 terminal capability values did not include 6058C8 for disabling the offline plain text PIN CVM. This configuration is supported by Gilbarco Veeder-Root starting with M7 firmware version 04/05.13.13. This was corrected by adding 6058C8 to the FCC list of supported 9F33 terminal capability values for Gilbarco Veeder-Root DCRs. It allows the disabling of the offline plain text PIN CVM with M7 firmware versions of 04/05.13.13 or higher.

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

1. After performing an EMV transaction, the EMV transaction data was not displayed in the EMV Transaction Report. This was corrected.
2. When an EMV EBT ECL fallback card was swiped, the PIN pad displayed the “INSERT OR TAP CARD” prompt. If the card was inserted, it displayed “Unsupported Card Try again”, followed by “Remove Card”. It was repeated three times and then it proceeded to the correct prompts and processed the transaction. This was corrected and if the card is inserted, it proceeds to the please swipe card prompt and the processes the transaction.

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

DCR was displaying a “Scan Loyalty Code” option even though “Enable Scanner” was disabled in DCR Position Attributes. This was corrected.

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

The indoor and outdoor mobile transactions were displayed incorrectly in the Report Navigator End Of Day Report. Also, the food stamp transaction count and amount were displayed incorrectly in the same report. These were corrected.

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

1. After one year of either upgrading or installing the Verifone Commander software, the POS displayed the “SEC Alert Pairing Invalid: To avoid data loss, immediately go to the Maintenance Menu and select Perform POS Pairing” message. This was corrected and now the automatic pairing renewal process will be performed as expected.
2. After an Auto Upgrade completed, the Restore Stage 1 displayed errors and the site was unable to initialize fuel and perform fuel transactions. This was corrected and now the Auto Upgrade will complete successfully without errors and perform fuel transactions.
3. When using the DataLogic Gryphon GD4500 Series scanner for an ID Check, it was always returning the date of birth as January 2, 2001. This was corrected.

### VISTA <a href="#vista" id="vista"></a>

VISTA was not allowing loyalty rewards when using a partner self checkout. This was corrected and now loyalty rewards can be used.

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

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

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

During an Automatic End of Day, there was a multiple thread access that was causing the batch not to close. The End of Day Report closed as expected without the batch totals. This was corrected.

### HPS FEP <a href="#bookmark89" id="bookmark89"></a>

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

1. Entry Mode was printed as “Swipe” on the receipt for Fallback transactions instead of “FSwipe.” This was corrected.
2. When a contactless Visa Fleet card was used in a prepay or at the DCR and then canceled successfully with zero dollar receipt, the EPS sent incorrect values to the payment host. This was corrected and the correct values are sent.
3. A VISA Fleet Mag-Stripe transaction was getting declined with a format error (Response Code - 904) when a Driver ID or ID number prompt was entered. This issue was occurring on indoor and outdoor transactions. This was corrected.
4. In a Fallback transaction, the Customer Copy receipt was missing the label “Auth#” in the network body for the Authnet#. Also, in a Fallback transaction, there was an extra space between Auth# and Resp Code for an Indoor Sale in Merchant Copy. These were corrected.
5. When a JCB refund transaction was initiated and then the contactless card was tapped, it was declined locally with a credit failure message on the POS. This was corrected and now the transaction will complete.

### NBS FEP <a href="#bookmark91" id="bookmark91"></a>

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

In the previous 55.00 release, the system was allowing loyalty requests to be sent with the payment request together. This caused the customer not to see the Reward/Accept PPG Discount immediately after the loyalty card swipe. Previous to Release 55, the software sent the loyalty swipe up first and return the rewards prompt. It would then send payment prompt for pay inside or at the pump. This was corrected.

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

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

1. Entry Mode was printed as “Swipe” on the receipt for Fallback transactions instead of “FSwipe.” This was corrected.
2. WEX Dual AID prompting was not working as expected. This was corrected by adding the custom tables for the Phillips 66 Distribution.
3. When a JCB refund transaction was initiated and then the contactless card was tapped, it was declined locally with a credit failure message on the POS. This was corrected and now the transaction will complete.

### VAPS FEP <a href="#bookmark95" id="bookmark95"></a>

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

1. Entry Mode was printed as “Swipe” on the receipt for Fallback transactions instead of “FSwipe.” This was corrected.
2. The network body of the receipt printed twice for Visa Fleet 2.0 sales transactions. This was corrected and now it only prints one time.

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

### Enhancement <a href="#bookmark98" id="bookmark98"></a>

**Fuelman Cards**

Fuelman AID(s) will now be enabled or disabled based on the card status in the Card Table PDL.

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

1. The host was returning an unknown tag ‘VS’ in the host totals response and therefore causing an error. This was corrected by adding checks for newer tags included in the interface to prevent the unknown tag error that was causing the host totals to fail.
2. The swipe ahead prompt was set to ‘three’ retries. This was corrected and now the swipe ahead retry is set to ‘one’.
3. Cards were declined when a restricted item, such as charity, was offered at the DCR. The card was immediately declined due to outside charity or donations enabled at the site. The decline happened immediately after inserting the card and before any charity prompt was presented or fuel was dispensed. If charity outside was disabled at the location, the card works as expected. This was corrected and the card with restrictions will process as expected even if the restriction is enabled at the site.
4. Datawire was sending an invalid Accept property due to Java. This was corrected.
5. The Card Type Prompt Code was set to zero for some entries while performing DCT download. This was corrected and Card Type Prompt Code as per RVE106 was added.
6. Expired Discover cards were being approved when the PDL indicated expiration date should be checked for this card type. This was corrected and now they will be declined.


---

# 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.04/whats-new-in-release-55.02.04.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.