# What’s New In Release: 54.02.00

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

### Verifone C18 Self Checkout and POS <a href="#verifone_c18_self_checkout_and_pos" id="verifone_c18_self_checkout_and_pos"></a>

Cashiers and managers can now access the Glory cash recycler's management system through a browser on the POS and/or the Verifone C18 Self Checkout.

### Verifone Cloud <a href="#verifone_cloud" id="verifone_cloud"></a>

1. Verifone Commander Onboarding can now be performed by giving only C-Site Management credentials at the Verifone Commander Configuration Client.
2. POS Security and Fuel Tax Exemptions can now be configured from the C-Site Management. Also, the Verifone Commander data can be synchronized to the C-Site Management.

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

The EZ-Receipt and APM menus and configurations have been removed from Verifone Configuration Client.

### Verifone Configuration Client and FoodService <a href="#verifone_configuration_client_and_foodse" id="verifone_configuration_client_and_foodse"></a>

Enhancements have been made between the Verifone Configuration Client and the KDS (Kitchen Display System) by implementing a “Refresh Configuration” functionality. This enhancement aims to ensure that the KDS stays up to date with the latest configuration settings provided by the Verifone Configuration Client.

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

Food Order Status notification is now sent to Cloud KDS.

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

1. In the Scanner Configuration, the default scanner option was changed to “2D Scanner” and the Ruby Ready scanner entry was renamed to Ruby Ready Scanner (Legacy). Sites that auto upgrade will retain the scanner they configured in the previous version.
2. Enhancements have been made to POS Pairing.

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

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

The Refresh Configuration feature at Verifone Configuration Client > Tools has been enhanced to include departments assigned to the PLUs sent using VISTA.

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

1. When a card does not have loyalty discounts and the customer answered ‘No’ at the loyalty registration message, the DCR was prompting for loyalty after fueling and getting stuck. This was corrected and the transaction will complete as expected.
2. Quick swipe handling was not executing in cases where EMV card was inserted and removed before ATR (Answer to Reset) was received. This was improved so that the card reader and keypad will be disabled when the EMV card is inserted and removed before ATR (Answer to Reset) is received. Also, the DCR will display a prompt to inform the customer that the card should be left in reader on next attempt.
3. On Gilbarco DCRs, when a card had both Credit and US Common Debit AID, T42 (IIN) and T5F55 (Issuer country code) tags were not returned from the device although these tags were present in card image. This was corrected and now will be returned from the device.
4. Initially when the EMV Configuration was sent to the Wayne DCRs, the system did not allow for partial AID match on Contactless Discover cards. This was corrected and now it allows for extended AID Discover Cards to be processed correctly.
5. When the “DCR Approve All Sales” option was enabled in the DCR configuration, the customer was only able to dispense one product and then the transaction completed. This was corrected and now the cashier can approve all sales with one key press, the customer can dispense multiple products, and then the sale finalizes.
6. When loyalty was enabled, user entered loyalty number at prompt, DCR displayed points balance, the DCR prompted for “Pay here Y/N” prompt, and if the user selected the ‘NO’ option, a network error was displayed. This was corrected.
7. Bennett DCR was locking up on second transaction after swiping attendant card. The DCR displayed the “Please Remove Card” message until the DCR was initialized or rebooted. This was corrected.
8. Occasionally, outdoor transactions were not journaled to the POS system until later in the day or next day. This caused an issue with reporting and with receipt reprint. This was corrected.
9. There was a difference in a amounts between the Network Card Report, Network Product Report, and EPS Network Report due to the DCR completing the sale as a zero dollar amount. This was corrected.
10. When a Gilbarco CRIND Contactless transaction was initiated with a MasterCard, the CDA (Tag 95) failed due to incorrect CAPKs.This was corrected and now during EMV Initialization, the CAPK section processing of the Gilbarco file correctly creates the two-character index number value by ensuring a leading zero character is provided if required.
11. Gilbarco M7 Contactless Reader in DCR was not enabled after DCR Initialization. This was corrected.

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

1. After a PIN prompt was canceled, the transaction continued instead of going into a declined state. This was corrected and now the transaction will cancel.
2. When Contactless EMV was enabled at the DCR, it was allowing contactless mag-stripe data (MSD) transactions. This was corrected.
3. There was a potential memory issue with Car Wash Paypoint, Vista Terminal or APT terminal configurations. This was corrected.
4. Contactless cards were prompting for cashback when disabled or not implemented. This was corrected and now will only prompt if cashback is enabled.
5. There was an issue with STAN files growing to large sizes leading to a potential memory issue. This was corrected.
6. The cashier was unable to activate CHS proprietary cards on the PIN pad. This was corrected.
7. When auto upgrading from Base 53.41.XX, the EMV Configuration tab was blank. This was corrected.

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

After every login attempt from APT devices, Refresh Configuration request was initiated from the APT device to VISTA and VISTA was trying to get the screen configuration. This caused a “Record Not Found” in the logs. It had no impact on the login and transactions performed on the APT device. This was corrected.

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

1. Messages from the Loyalty Host were not being displayed to the cashier, but instead, displayed a “PCATS07 ISO Format Error” message. This was corrected and now the loyalty messages are displayed.
2. With Loyalty and Prompt for Loyalty after payment enabled, the “Reward Customer Yes/No” prompt was not displayed on the PIN pad. This was corrected.
3. Sale items in the loyalty finalization from the POS were not adding up to the total amount of the transaction and therefore, the EPS was not finalizing loyalty. Retrying the loyalty completion was not correcting it, but the system kept trying to complete it. This caused a large number of STAN files on the EPS. This was corrected.

<br>

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

1. Digital Video Recorder (DVR) went offline when Receipt Printer Unavailable message displayed on the POS. This was corrected.
2. Special characters in the Site ID, Location ID, and Period Name were causing the system to send blank data to the back office. This was corrected.
3. When the cashier added a PLU with serial number and then canceled the serial number prompt, the PIN pad was still activated with the blue arrow lights. This was corrected and now the PIN pad blue arrow lights will be turned off when the cashier cancels the serial number prompt.
4. When the “ASM license expired” or “SCO license expired” overlay message displayed, the “Sales Functions Initializing” message also displayed. This was corrected and the Sales Functions Initializing message will not display.
5. After an auto upgrade, the full scanner configuration was not retained. This was corrected.
6. The Verifone Commander was rejecting the import of an image file with “The maximum number of images allowed is 300” error message. This was corrected and the limit was increased to 500 images.
7. After an auto upgrade, the Swipe License/Membership option under PIN Pad Configuration was not sending a prompt to the PIN pad. This was corrected.
8. The auto upgrade failed due to an issue in the auto renewal of Verifone Commander and POS trust (SSH-CA cert) after one year of expiry. This was corrected.
9. POS terminals were unexpectedly becoming unpaired with the Commander. This was corrected.

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

The Pump Test was not displaying the subtracted amount from the fuel reports. This was corrected.

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

1. When the user entered and invalid account number for EBT Voucher Processing, the flow stopped without any message. This was corrected and now the EPS will display “Invalid Account Number” when EBT number is not correctly entered.
2. For Charity transactions, when the Cash MOP was selected, the PIN pad displayed the option to the exact amount or “No Thanks.” When the Credit MOP was selected, the “No Thanks” prompt was not displayed and the customer had to select Cancel. This caused confusion. This was corrected and now the prompt displays for Credit.
3. On split tender transaction, the EPS was getting pay line items from the POS and loyalty was taking full transaction amount as pay line item for Cash. This was corrected and when cash is last pay line item, the actual pay line item amount is calculated by subtracting other pay line items stored in EPS STAN files.
4. Fuel Reward (FRN) and second loyalty was not printing inside, but instead printed as price tier. This was corrected.
5. Multiple Fuel discounts were not printed for more than one fuel product discount when used in one transaction. This was corrected. When applying an auto-generated POP code using any qualifier to an indoor prepay fuel transaction, the POS displayed the “POP CODE REJECTED” message. This was corrected.
6. On Verifone C18 POS register with a POP Discount transaction and loyalty offline, the PIN pad was stuck on “Waiting for cashier” and the C18 did not respond after pressing CASH MOP key to complete A PLU with department fuel type was able to be voided using void line. This was corrected and now when this type of void transaction is attempted, the POS will display not allowed.

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

### Chase FEP <a href="#bookmark62" id="bookmark62"></a>

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

EMV Contactless cards are now supported at Gilbarco and Wayne DCRs for the Chase distribution.

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

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

Online and offline transactions are now sent at the same time so that the site can process debit transactions while offline transactions are in queue. Also, online transaction channel handling has been improved.

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

Card label was printed twice in the receipt for outdoor card transactions. This was corrected and will print only one time.

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

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

JCB and China Unionpay (CUP) contactless cards are now supported inside and outside.

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

The EPS time will now synchronize with the HPS host. The time sync request will be triggered at 3:00 A.M. local time everyday and after a PDL request.

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

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

Fuel sales using Visa Fleet cards were preauthorized, but occasionally not settling with the host. This was occurring with POS prepays as well as preauthorizations at DCRs. The host was not getting the completion from the EPS when this occurred. This was corrected.

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

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

The EPS time will now synchronize with the HPS host. The time sync request will be triggered at 3:00 A.M. local time everyday and after a PDL request.

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

The POS was locking up after a card was declined. This was corrected.

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

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

For ExxonMobil sites, the following support has been added for Comdata:

* Comdata only and Comdata co-branded commercial fleet cards
* Comdata Comcheks (requires an MOP to be configured)
* Comdata Express Codes (requires an MOP to be configured)
* An option to send Diesel fuel prices to Comdata through Fiserv so a site's prices can be displayed in Comdata's mobile app. Also, cards can be approved for fueling if the price is within the price posted in the app.

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

1. EMV Fallback transactions contained no receipt or card information. This was corrected.
2. All DCR sales were getting response code 904 with “No EMV Data received from host” error message in the log. This was caused by not supporting multiple currencies. This was corrected by adding multiple currencies to the configuration file.

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

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

The EPS time will now synchronize with the HPS host. The time sync request will be triggered at 3:00 A.M. local time everyday and after a PDL request.

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

When using a gift card in a postpay fuel sale, it was failing with the response code 50 from the host. This was 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.02/whats-new-in-release-54.02.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.