# What’s New In Version: 56.03.00

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

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

**Pay at the Counter**

The Verifone Self-Checkout display option to Pay at the Counter can now be hidden for certain scenarios. This is for sites that do not want their customers to pay at the counter. It can be enable or disabled in System Properties.

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

**Stylesheet-Based Reports**

By optimizing certain aspects of memory usage, improvements were made to Verifone Commander Stylesheet-Based Reports.

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

**Penny Rounding Feature**

With the discontinuation of the U.S. penny, all cash transactions can be rounded to the nearest five cent increment. Our POS system, billing, and reporting systems will properly handle rounding, eliminate penny references, and remain compliant with the new standards. The following System Properties can be configured:

* cash.rounding.enabled=true or false
* cash.rounding.strategy=NEAREST, UP, or DOWN
* cash.rounding.adjustment=0.05, 0.10, or 1.00

If incorrect values are entered, the system will use the default values (false, NEAREST, and 0.05).

**Site Management Suite (SMS) Import and Export Utility**

The Site Management Suite (SMS) was updated to version 3.00.15 and the Import and Export Utility was updated to version 3.00.11 with this release.

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

### Verifone Configuration Client <a href="#bookmark33" id="bookmark33"></a>

1. The DNS values displayed in Verifone Configuration Client were determined by the sequence of elements in the incoming XML rather than their unique IDs. As a result, DNS3 was populating on DNS1. If there were no DNS entries configured on DNS1 and DNS2, the remaining values shifted upward and appeared in the wrong fields. This issue was limited to the information viewed in Verifone Configuration Client. The XML payload had the correct IDs. This was corrected by binding each DNS to their respective configuration IDs.
2. The Security Log Servers Configuration was displaying an internal error when trying to add or update a log server IP in Verifone Configuration Client. This was corrected.
3. There was a potential issue that could result in the system getting stuck causing the POS to lock up. This was corrected.

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

1. The “OK” button on the Verifone Self Checkout displayed with a red background. It was causing confuion. This was corrected and now it displays with a green background.
2. When an order was placed on the Verifone K350 or Online Ordering Portal, the Verifone KDS received a ticket with a specific order number. If the ticket was recalled or scanned from the customer bar code and then paid the ticket on the Verifone C18, the Order status was updated to “Paid.” However, a new duplicate ticket was also created with a Verifone C18 order number. This was corrected and now there are no duplicate tickets.

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

There was a possible intermittent issue with dispensers not allowing a preset due to pump stopped. This was corrected by making an internal update to improve handling.

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

1. 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.
2. 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.
3. When a car wash was selected after fueling, the DCR went to the idle screen, no receipt printed, the completion was not sent to the host, and the sale came due inside. This was corrected and now the transaction will complete as expected.

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

1. 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.
2. Comdata limits were handled incorrectly if more than one limit was sent. Quantity limit was compared without addressing the decimal points. This was corrected by setting the decimal points towards the left two positions for comparison.
3. Comdata product mapping table was missing entries for #1 Diesel and premium off-road diesel. This was corrected and the entries were added.
4. The user had to perform multiple day closes to apply the network tables. This was corrected and now only one day close has to be performed to apply the tables.

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

1. When the user selected loyalty outside and payment inside, loyalty was prompted again inside. The loyalty information was not retained for the postpay sale. This was corrected and now the loyalty ticket references are retained for settling the postpay fuel transaction.
2. The PIN pad was displaying “Account Not Found” when the customer manually entered their loyalty number and the prompt “PCATS7 ISO ERROR” was displayed on the POS. This was corrected.
3. When the Cancel button was pressed on the POS numeric keypad at the Use Loyalty Option screen, the transaction was declined and the “E17 REVERSE ERROR” message displayed on the POS. This was corrected and now the transaction completes successfully.

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

1. In Verifone Configuration Client > Managed Modules, when scanner and printer device types were changed from serial to USB and the POS was rebooted to engage the device, the printer module “Printer Type” changed to “VFIPrinter.submodule.” This was corrected and now it displays correctly.
2. The following charity donation expected prompt messages were not displayed on the POS screen:

* Charity In Progress
* Please acknowledge the charity prompt on the PIN pad or POS

  This was corrected and now the prompt messages will display after entering values from the keyboard.

3. Occasionally, the Auto Upgrade was not completing. The POS was stuck at the A8 stage during the upgrade. This was corrected and now the Auto Upgrade completes as expected.
4. The error message “Unknown Communication Issue \[1006]. Please wait. Trying to reconnect to server” displayed on the POS and then it rebooted. This was corrected.
5. Multiple logouts and logins were needed in order for POS configuration changes to be reflected on the C18 workstation. This was corrected.
6. When the Menu description was not available, the menu was displaying with a blank name. This was corrected.
7. 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.
8. Verifone serial printers (RP-300/310/320/330 and TM-88) without white labeling firmware were displaying “Receipt Printer Unavailable” or “Receipt Printer Unsupported” alarm messages. This was corrected and now the messages no longer display.

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

1. Tax was not applied on a PLU item from the second menu in an Order Menu transaction. This was corrected.
2. 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.
3. For blue law transactions, the system was only looking at the PLU record and not inheriting from the department record. This was corrected by ensuring PLUs inherit Department restrictions and prevents restricted items from being sold outside designated hours.

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

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

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

**Business Date and End-of-Day Sequence Number (EODSN) Support**

The Business Date (BD) and the End-of-Day Sequence Number (EODSN) are now included in certain messages sent to the Chevron host. The Terminal Batch Summary Report and the EPS Network Report now display the correct BD and EODSN, and both values update at the end of each day.

When the system starts for the first time after installation, it sends an Offline Sign-On message that includes start values of Business Date, Start Time of Business Date, Start of EODSN and End of EODSN. If the system does not receive a response to this message, it will try again every 10 seconds up to 15 times. During this time (about 5 minutes), transactions are paused. If all retries fail, the system will allow transactions to continue normally, but it will not send the message again unless triggered later by the Store and Forward process. The follow-up message will not include the extra starting information. If the system does receive a successful response from the host, it will update the Business Date and end-of-day values accordingly. If no response is ever received, those values will not be updated.

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

1. When performing and indoor or outdoor transaction with three loyalty programs configured, sequence of loyalty prompts was incorrect. The order of prompting was corrected.
2. When an item with Open PLU and ID Check was enabled and the customer was under age, the error message “Customer Cannot Purchase This Item” was not displaying unless a second item was added to the transaction. This was corrected and now the error message displays immediately on the first item.
3. Debit Host Total information captured under the heading “ELECTRONICALLY CLOSED DEBIT BATCH” of the Network Batch Detail Report was incorrect, because the POS was referring to the Credit Total (instead of Debit Total) value sent in the response message received from the Chevron Host when POS Debit Total value was '0' and vice versa. This was corrected.
4. After a customer received a loyalty discount, the points were not removed from the loyalty account. This was due to specific timeout values being ‘999’. The POS/FCC timed-out after four minutes on any card service request and drop the connection. When the prompt eventually timed out, the EPS detected that the connection no longer existed to POS/FCC and triggered its reversal logic. This was corrected by changing the timeout value if it is ‘999’.
5. Cashback prompt was not displayed for both Discover Credit and Debit cards while performing a Prepay only Fuel or Prepay Fuel with Merchandise transactions when the switch panel settings were configured to prompt cashback. This was corrected.
6. When performing a Gift Card balance inquiry using an MSR card, the receipt was generated successfully and reflects the correct gift card balance. However, the entry method (Swiped) was missing in the receipt. This was corrected and now the entry method (Swiped) is displayed along with the card details and balance.
7. Decline and pre-authorization transactions were populating the Unconfirmed Log. This was corrected and now they are not added to the Unconfirmed Log.

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

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

WEX and Mastercard Fleet transactions were failing with exception errors due to prompt lengths and product codes.

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

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

Bluefin is now supported. Bluefin is a payment and data security company that provides Point-to-Point Encryption (P2PE) solution to protect sensitive payment information. Its service provides secure transactions both in-store and online, reducing the risk and simplifying compliance with Payment Card Industry (PCI) standards.

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

1. POS was displaying “EPS is busy” message when processing a network transaction. This was corrected and now the network transaction continues as expected.
2. WEX and Mastercard Fleet transactions were failing with exception errors due to prompt lengths and product codes.
3. WEX EMV transactions were declined with a format error due to an extra space in the EMV data. This was corrected by removing the extra space.
4. The Network Configuration for Phillips 66 were not preserved after an auto upgrade from 56.00.00 to 56.02.01. This was corrected and now it is preserved.

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

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

1. 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.
2. When the parameter “Allow without sale” was enabled for Credit or Debit MOP and cashback or cash advance was selected, the host declined due to a missing Service Level. This was corrected and now the service level is included.
3. The POS was displaying an E16 ISO format error when a sale transaction was performed by selecting a PLU linked with tax for all WEX OTR cards. This was corrected and now the transaction processes through the primary host if any merchandise PLU or fuel product is linked with tax.
4. Site was processing on TID 002, but reporting totals on TID 001. This original MID and TID were not being reset to null after Close Daily. This was corrected and now the original MID and TID are reset to null after response received for the host totals.
5. Changes have been made to comply with the latest Datawire protocol.

### Shell FEP <a href="#bookmark52" id="bookmark52"></a>

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

When the POS-to-EPS cable was disconnected during fueling and then reconnected more than three minutes after fueling was completed, the EPS failed to send the Card Financial Advice CSR message. This was corrected and now it sends the Card Financial Advice CSR message.

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

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

1. &#x20;WEX and Mastercard Fleet transactions were failing with exception errors due to prompt lengths and product codes.
2. WEX EMV transactions were declined with a format error due to an extra space in the EMV data. This was corrected by removing the extra space.

### Verifone EPS FEP <a href="#bookmark56" id="bookmark56"></a>

#### Enhancements <a href="#bookmark57" id="bookmark57"></a>

**Visa and Mastercard Contactless EMV**

Visa and Mastercard contactless EMV cards are now supported for the FCB FEP at the Gilbarco M7 DCR.


---

# 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-56.03.00/whats-new-in-version-56.03.00.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.