# What’s New In Version: 56.01.00

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

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

**Brand Updates**

The Verifone Configuration Client was updated with the new Verifone brand updates.

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

**Keypad**

The Self Checkout (Customer Mode) keypad will now match the PIN pad keypad layout.

**Print Inactivity Ticket**

The “Print Inactivity Ticket” parameter was added to a new section called “Inactivity Parameters” under Verifone Configuration Client > Self Checkout Global Configuration. This new parameter enabled by default will print a receipt if the customer abandons the transaction before the payment.

**Print Pay At Counter Ticket**

The “Print Pay At Counter Ticket” parameter was added to enable or disable the suspend print function for Pay at Counter on the Verifone Self Checkout functionality. It is located at Sales Parameters > Self Checkout > Global Configuration. After Pay at Counter is selected, a momentary message notifies the customer that their transaction was suspended.

**Void Line**

On Verifone Self Checkout Monitoring, the cashier can perform a Void Line to correct a transaction when a customer accidentally scans an item more than once or decides they do not want an item. The cashier can perform this action on Verifone Self Checkout without having to leave their POS workstation.

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

**Forecourt Log Messages**

The following changes were made to the Forecourt Log Messages:

* Clarifications were added to the information in fuel price log messages
* Corrections to the EMV Transaction Time log message for both Gilbarco and Wayne contactless transactions
* Corrections to the method names for a few Gilbarco driver log messages

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

**Long Text Prompting**

Support for long text prompting for outdoor optional loyalty reward messages has been implemented.

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

**Cancel Key**

A cancel key was added to the loyalty prompt flow for the cashier to abort the PIN pad prompting if the customer leaves without responding.

### Mobile Payment <a href="#bookmark115" id="bookmark115"></a>

**Single Credit MOP**

Single Credit MOP implementation was enhanced to include support for additional QR code types (beyond 204 or 205) for Mobile payment.

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

**Verifone Commander Software Management Suite (SMS)**

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 56.01.00 software release.

**Age Verification**

When a site disables the age verification service, the Verifone Commander will not attempt to contact the service. It will retain the store and forward transactions until service is enabled or deleted. When service is enabled, it will check for connectivity and then send the store and forward transactions, as well as get a list of trusted issuers.

**Auto Upgrade Backup and Restore**

The POP Configuration has been added to the Auto Upgrade Backup and Restore functionality.

**Cash Recyclers**

Cashiers and managers now have access to Crane’s cash recyclers management system in order to perform one or more of the following functions:

* Understand how to clear a jam
* See current cash/coin inventory
* Perform settlement/audit
* Dispense or fill cash/coin inventory
* Review errors or other information

This access will be available through a browser on the POS and/or Self-Checkout to avoid needing to connect another device.

**Plug-and-Play Functionality**

Plug-and-Play functionality has been added for USB-connected devices such as the Zebra Scanner and Verifone Self Checkout Light Pole. With this feature, supported devices will work without requiring a reboot when disconnected and reconnected, ensuring no disruption to business operations.

**POS Pairing**

Improvements were made to the POS Pairing Logging.

**System Optimization**

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

**Tunnel IP**

The Tunnel IP will now be included in the Verifone Commander site asset data sent to the Verifone C-Site Management.

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

**Tipping**

The Verifone Commander now provides flexible tipping options for sites that sell prepared items. The tipping prompt will be displayed on the PIN pad. There will be configurable preset amounts or percentages for customer selection. The “Prompt for Tip” will be enabled in the department and will apply to all PLUs within that department. Customers will have the option to enter a custom amount. The prompt is customizable.

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

**Car Wash Code**

In previous releases, the Verifone Commander generated a car wash code for a Vista device even though the device generated the code without the Verifone Commander. When the Vista device is able to generate its own code, the Verifone Commander will not generate an additional code, as long the device sends the code to Verifone Commander.

**PLU Not Found**

PLU Not Found functionality is now supported on Vista devices. For example, if a customer scans an item that was not added to the price book, the Vista self-checkout device in cashier mode will be able to perform a “PLU Not Found” sale.

**Select All**

The “Select All” functionality for departments has been added in Vista Devices > Groups. When clicking “Select All” for the Enable Departments settings in Vista Devices > Group, it selects both the check box for sticky label and departments.

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

### Verifone C-Site Management <a href="#bookmark120" id="bookmark120"></a>

1. There were several issues involving special characters displaying incorrectly across many different configurations including the Loyalty and Mobile Configurations. These were corrected.
2. When a user deleted a department from the Fee Tab list box, instead of clearing the selection or displaying a blank entry, it defaulted to selecting the zero index element, which was not the desired behavior. This was corrected and now the list box displays a blank entry when an item is deleted.
3. For Brand transitions, Loyalty Configurations were not received in the Cloud from the Verifone Commander after onboarding for the first time. This was corrected and now the Loyalty Configurations are received.
4. The C-Site Management Menu Configuration was updated with a new PLU structure. This will also support the older PLU structure to be backwards compatible.
5. A large amount of sites had their Mobile Configuration erased simultaneously without a C-Site Management push. An exception occurred because two threads were picking up the same configuration message simultaneously. Both threads attempted to write to the same file leading to conflicts. This was corrected and now only one thread will write to the file at a time avoiding conflicts.
6. Error 503 was displayed in the logs when uploading images from the Verifone Commander to the Verifone C-Site Management. This was corrected.
7. If an onboarded Verifone Commander with configurations was on Verifone C-Site Management and then it was deleted and assigned a new Service ID, the configurations were not sent to Verifone C-Site Management after onboarding again. This was corrected and now the configurations will be sent.

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

After performing an Auto Upgrade, duplicate items were displayed in the panel configurations within Verifone Configuration Client. This was corrected.

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

1. On Verifone Self Checkout Monitoring, the payment failure symbol was displayed on the monitoring button at the same time the Charity prompt was displayed on the PIN pad. This was corrected and the payment failure will not be displayed.
2. On Device Monitoring, the MQTT button color was incorrect when canceling the order menu which had the ID Check as a sub-item. This was corrected and now the MQTT button will display as green when canceling the order.
3. After an Auto Upgrade and if the Verifone C18 was in POS Portrait Mode and then the cashier tried to switch the mode from POS to Self Checkout, the “Sorry, no application is currently supported.” message displayed. This was corrected and now the Verifone C18 can be switched from POS to Self Checkout mode after an Auto Upgrade.
4. On Verifone Self Checkout, the POS was locking up on a prepay transaction on the commercial fuel dispenser after enabling the “Allow Multiple Products” option in the Fuel Configuration. The cashier was unable to void the transaction. The POS had to be rebooted before exiting the ticket. Since the multi-select is not supported on Verifone Self Checkout User Interface, the transaction flow will now skip the multi-grade prompt on Verifone Self Checkout for prepays.
5. Verifone Self Checkout became unresponsive after inactivity time on the Activation/Recharge screen. This was corrected and the Activation/Recharge screen will now be dismissed, and the Verifone Self Checkout will return to the welcome screen.
6. The Screen Configuration on Verifone Self Checkout was not retained after an Auto Upgrade. This was corrected and now all Verifone Self Checkout configurations will be restored after a backup and restore with the Verifone Petro Suite Installer (PSI).
7. On Verifone Self Checkout, the receipt was printed even though the customer selected ‘No’ to print receipt. This was corrected.
8. On Verifone Self Checkout, the inactivity timer was displayed one minute after selecting Checkout and MOP. This was corrected and the inactivity timer displays after five minutes.
9. Receipt was not printing if “Done” was not selected during Suspend and Pay at Counter. This was corrected and the now the receipt prints.

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

The fuel driver was not displaying the discounted the cash and credit prices for Bennett direct interface for single price windows. This was corrected to display the cash or credit prices.

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

1. Transaction was not completely terminated for a payment failure after loyalty scenario. It was occurring when a payment card was inserted while payment prompt after loyalty was displayed. The customer was prompted to remove card that gave the impression the payment had completed normally. If customer lifted the handle and cashier authorized a postpay, customer would likely to fuel and not follow prompt to pay inside since the card was already presented to the DCR. This was corrected and the transaction will terminate if a payment failure occurs after loyalty.
2. When a second cashier approved the same dispenser from a different POS terminal within roughly five seconds of the first approval, the first approval armed the pump and the second caused an error that removed the receipt number. This caused a sale from the second approval to come due inside. This was corrected and now the receipt number is retained if an error occurs during the approval of a calling pump. This will prevent the sale from coming due inside in cases where pump is armed and an error occurs.
3. The Verifone Commander was sending blank prompts to Wayne DCRs for loyalty transactions, it displayed “WPF,999” on Anthems and blank displays for more than five seconds on Ovations. This was corrected and now the loyalty transaction completes as normal.
4. WEX cards include alphanumeric prompts even when the expected response is numeric only. The system was rejecting alphanumeric prompts when the DCR keypad was not configured as alphanumeric. This was preventing certain WEX cards from being approved. This was corrected and now the format error generated for alphanumeric prompts sent to DCR with a numeric keypad will be bypassed.
5. 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.
6. Legacy JCB cards were supported for contactless payment on Wayne DCRS. This was corrected and they are no longer supported.
7. 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.
8. 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.”

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

1. The EPS was not handling the terminal batch close as expected. This was corrected and improvements have been made to the terminal batch close process.
2. Fuelman cards were not prompting for Driver ID or Odometer. This was corrected.
3. After performing an EMV transaction, the EMV transaction data was not displayed in the EMV Transaction Report. This was corrected.
4. 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 processes the transaction. This was corrected and if the card is inserted, it proceeds to the please swipe card prompt and the processes the transaction.

### FoodService <a href="#foodservice" id="foodservice"></a>

Future mobile food order report was printing raw HTML instead of the correct report. This was corrected.

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

1. After the initial loyalty prompting, a loyalty failure and then the customer continued to payment with a failed hybrid card, the terminal repeated the loyalty prompting again. This was corrected and the transaction will continue as expected without repeating the loyalty prompting.
2. When a multiple loyalty transaction was performed and if the first loyalty program host responded with a “Rewards Not Available” message, then the POS would display the same message for the second loyalty program. This was corrected and the message will only display if it is in the second host response.
3. The ampersand symbol (&) was not displayed between loyalty program names on the indoor PIN pads. This was corrected and now it displays.
4. The Loyalty element was being created with the FEP name as the program name for hybrid cards and it was causing an “E33 Error” during a loyalty transaction. This was corrected and now the Card Type Label will be used to create the loyalty element for hybrid cards.
5. When send reward prompt to the cashier was enabled in a loyalty transaction, the “Use Loyalty Options” screen displayed the program name as “true” on the PIN pad instead of the configured program name. This was corrected and the configured program name will display on the PIN pad.
6. When the “Display PINpad Prompts To Cashier” parameter was enabled, the “&” symbol displayed on the POS as “& amp” within the loyalty program name. It was correctly displayed on the PIN pad. This was corrected and now it displays as “&” on the POS.

### Mobile Payment <a href="#mobile_payment" id="mobile_payment"></a>

1. The receipt printed for a mobile ASA transaction did not contain “Merchant Copy” and “Acct/ Card #” label. This was corrected and now the labels will print.
2. The EPS was blocking mobile receipt text from printing on all receipts that were not completions. This was corrected and now the EPS no longer blocks receipt texts, but the POS does not send receipt text on prepay receipts.

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

1. 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.
2. The USB Scanner ID and Model Configuration were not retained after an Auto Upgrade. This was corrected and now they will be retained.
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.
4. When a user chose not to restore backup data after a PSI installation, the confirmation prompt displayed the message “! The backup data will be deleted. Are you sure?”. This was corrected and now the exclamation mark before the sentence is displayed as an icon inside of a yellow circle.
5. 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.
6. When performing an Auto Upgrade from Release 55.xx.xx to 56.xx.xx, booting to Diagnostic Kernel (DK) failed after a successful Auto Upgrade on the Verifone Commander side. The POS DK worked fine. This resulted in the Verifone Commander was unable to downgrade to lower bases. This was corrected and now booting into the DK is successful.

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

1. The “All DCRs” section of the Department By Register, Category By Register and Tax By Register reports contained the totals from only one department in spite of having purchased products from two separate departments. This was corrected and now the “All DCRs” section displays two departments.
2. 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 Report Navigator End Of Day Report.

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

When a site sold an age-restricted item on a prepay fuel sale and there was an underrun, the POS prompted to check the ID again when giving the change back for the underrun transaction. This was corrected and the ID will not be prompted again.

### 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="bookmark133" align="center">FEP Specific Changes</h2>

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

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

**EMS Batch Report**

Additional sales transaction information such as Product Code, Price Per Gallon, Odometer, Driver ID, etc., were added to the EMS Batch Report for Reconciliation on Verifone Commander.

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

1. When multiple loyalty programs were configured and used during a transaction, the terminal prompted to “Insert or Swipe the Payment Card” instead of “Insert or Tap Payment card.” This was corrected.
2. When the customer entered an invalid loyalty ID, the POS allowed them to retry three times. This was corrected and now the POS will only allow two retry attempts.
3. The POS was displaying “Card has two fuel product” message and then declining the sale when using some cards. It was caused by the system checking for 900 series product codes and passing them as fuel. It incremented the fuel purchased count that went beyond the fuel limit allowed by Chevron. This was corrected and now the system will use NACS product codes to filter out 900 series product codes.
4. 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="#hps_fep" id="hps_fep"></a>

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

**Brand Selection**

ARCO/Tesoro was removed from the Brand selection in the HPS distribution when using the Verifone Petro Suite Installer and Verifone Configuration Client.

**Gilbarco Kernel Version**

A Verifone Commander property file did not contain the needed instruction to point to the required Gilbarco M7 3.12 kernel version. This was corrected and the file was edited to contain the required Gilbarco M7 3.12 kernel version needed.

#### Resolutions <a href="#bookmark139" id="bookmark139"></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. 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.
4. 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.

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

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

1. When selecting EBT PLU with credit MOP, the PIN pad bypassed payment options and processed the transaction as a debit, resulting in a declined transaction with a “Bad Test Card” error. This was corrected and the PIN pad will prompt for Debit, Credit, and EBT options and approve the transaction.
2. Fallback entries have been added for the EMV WEX, Fuelman, and Voyager cards. An additional card, Maverik Fleet has been added to the card table.

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

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

**Gilbarco Kernel Version**

A Verifone Commander property file did not contain the needed instruction to point to the required Gilbarco M7 3.12 kernel version. This was corrected and the file was edited to contain the required Gilbarco M7 3.12 kernel version needed.

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

1. Entry Mode was printed as “Swipe” on the receipt for Fallback transactions instead of “FSwipe.” This was corrected.
2. Two System Trace Audit Numbers (STAN) were printed on PIN Debit receipts. One STAN had the invoice number and the other had the reference number. This was corrected. The STAN that had the Invoice Number was removed, because it already had a separate field on the receipt. Also, the Account type and Network Number were moved one below the other instead of printing it on a single line.
3. WEX Dual AID prompting was not working as expected. This was corrected by adding the custom tables for the Phillips 66 Distribution.

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

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

**Comdata Commercial Fleet**

For merchants that process Comdata commercial fleet transactions, the POS and EPS have been modified to calculate the sale prices such that non-fuel items in the sale include the tax amount in the item price so that the host can process the transaction.

**Fuelman AID**

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

**Gilbarco Kernel Version**

A Verifone Commander property file did not contain the needed instruction to point to the required Gilbarco M7 3.12 kernel version. This was corrected and the file was edited to contain the required Gilbarco M7 3.12 kernel version needed.

**US Common Aid**

Currently, for Fiserv distributions, US Common AID has a non-zero CVM limit. Cardholders below the limit are not prompted for a PIN, resulting in the transactions being processed as credit without opportunity to process as debit. The CVM limits were updated to $0 as per requirement.

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

1. The Fiserv AID Rules Table for inside and outside was incorrect for Fuelman cards. This was corrected and now the Issuer Identification Number (IIN) must be set to ‘NO’.
2. When an offline transaction was performed with an EMV card, it was declining with a “E03 Sale Declined” message. This was corrected and now the transaction will be successful with a local authorization confirmation.
3. 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.
4. 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.
5. 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.
6. Datawire was sending an invalid Accept property due to Java. This was corrected.
7. After upgrading to release 55.02.01, the diesel product (code 20) became restricted. This was corrected by making a change to the product table.
8. The swipe ahead prompt was set to ‘three’ retries. This was corrected and now the swipe ahead retry is set to ‘one’.
9. 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.

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

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

**Gilbarco Kernel Version**

A Verifone Commander property file did not contain the needed instruction to point to the required Gilbarco M7 3.12 kernel version. This was corrected and the file was edited to contain the required Gilbarco M7 3.12 kernel version needed.

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

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

**Gilbarco Kernel Version**

A Verifone Commander property file did not contain the needed instruction to point to the required Gilbarco M7 3.12 kernel version. This was corrected and the file was edited to contain the required Gilbarco M7 3.12 kernel version needed.

**Marathon Brand**

Marathon was removed from the Brand selection in the VAPS distribution when using the Verifone Petro Suite Installer and Verifone Configuration Client.

#### Resolutions <a href="#bookmark152" id="bookmark152"></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.


---

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