# What’s New In Version: 56.02.00

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

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

**Branded Oil Policies**

After successfully logging into Configuration Client or the Import/Export tool, a disclaimer message “C-Site Branded Oil Policies may control forms. If there is a violation, C-Site will revert the data.” displays to the user. For Spanish-based locales, an equivalent translation of the above message will display to the user.

{% hint style="info" %}
Only certain field(s) will be controlled in a form corresponding to a policy.
{% endhint %}

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

**Background Screen Customization**

The background screen on the home and lookup pages on the Verifone Self Checkout can now be customized by uploading an image for each screen orientation. The image will automatically load when rotated between landscape and portrait. A tool tip was added to the background image texts that will display the screen ratios for portrait and landscape. It also displays a note that the banner will overlay these images. Background images are not required for configuration. The default parameters will load white background and white background with gif) when not used.

**Bypass ID Check**

Bypass ID Check is now supported in Verifone Self Checkout Monitoring. Bypass ID allows cashiers to easily bypass age verification when prompted.

**Light Pole Enhancement**

The Verifone Self Checkout light pole now flashes a slow yellow color when the “Are you still there?” inactivity prompt is displayed. Also, the Verifone Self Checkout Monitoring button changes to yellow to display inactivity updates.

**Reprompting for Age Verification**

When an item is added to the cart with a higher age verification requirement, the POS, Verifone Self Checkout, and the Verifone Self Checkout monitoring function will reprompt for age verification.

**Transaction Timer Message**

A transaction timer message to cancel the transaction has been added to Verifone Self Checkout if a customer walks away from the sale.

**POS Online Help**

POS online help instructions were updated for Verifone Self Checkout Monitoring.

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

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

**WEX and Comdata Direct Connection**

A Verifone direct connection to WEX and Comdata has been implemented. It allows the Verifone Commander to process Commercial Fleet transactions directly to WEX and Comdata. It will enable customers who do not use an acquirer, but supports commercial fleet transactions, to accept WEX and Comdata commercial fleet cards. It will be configured in Verifone C-Site Management only.

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

**Loyalty Prompt Change**

The loyalty prompt “Use Loyalty Options” was changed to “Present Loyalty ID/Card” when displaying soft keys for Alternate ID and barcode.

**QR Code Prompt**

A loyalty program enrollment QR Code prompt is now supported on the Verifone M400 PIN pad.

### Mobile Payments <a href="#mobile_payments" id="mobile_payments"></a>

**Fuel Grade Restrictions**

Mobile Payments now supports Fuel Grade Restrictions on Verifone Commander.

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

**DNS Configuration**

The DNS Configuration in Network Configuration is now sent from the Verifone Commander to the PIN pads.

**Import and Export Utility**

Site Management Suite (SMS) Import and Export Utility was updated to version 3.00.10 with this release.

**Memory Usage**

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

**Verifone RP-700 Printer**

The Verifone RP-700 Printer is now supported. It prints receipts from the front or top, QR codes, bar codes, and logos. It is Verifone white-labeled and secured. It has USB plug-and-play support.

{% hint style="info" %}
The customer display should be disconnected when any USB peripherals are connected.
\
White-label firmware is required for the Verifone RP-700 printer. See the Important Information section, for white-labeling details.
{% endhint %}

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

**Bar Code Scans**

The Vista framework was enhanced to allow barcode scans for mobile payments as part of the payments flow. Currently, Vista only supports the PIN pad QR code scan from the mobile application.

**Menu IDs**

Menu IDs will now be sent from the Verifone Commander to the Vista Partner Food Service.

**Reporting**

Vista device information is now available on the Verifone Commander to confirm partners are properly reporting their devices. It will also be available on Verifone C-Site Management Site Assets.

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

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

1. Verifone Self Checkout locked up when the inactivity timer reached its limit during charity or tipping. This was corrected and now the user will be able to access the Verifone Self Checkout after the register time out.
2. If a customer answered ‘No’ to the loyalty prompt on the Verifone Self Checkout, it displayed a dynamic loyalty prompt after hybrid payment. This was corrected and now the Verifone Self Checkout will skip the dynamic loyalty prompt after a hybrid loyalty card is used.

### Dispenser Card Readers <a href="#bookmark84" id="bookmark84"></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. When the customer finished answering loyalty prompts and then raised the fuel handle at the payment screen, the DCR was calling inside even though Handle Up Calling and Preset Postpay were disabled. This was corrected and now the DCR will not call inside.
3. 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.
4. 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 time improvements for only event messages received from Wayne.

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

1. The “Invalid Product” message was displayed twice when attempting to purchase lottery with a fleet card. This was corrected and now it only displays once.
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. 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.
4. Null Pointer Exception was observed in the T-Log as part of a successful card transaction. This was corrected and now Null Pointer Exception are no longer observed.
5. Cashback option was not prompted when the transaction included PLUs with Tax and the customer was using Discover card for payment. This was corrected and now the cashback prompt displays.
6. Intermittently, a network transaction was not journaled in the T-Log or Network Journal. This was corrected and now it is journaled.
7. Transactions were getting declined when using the loyalty QR code on the PIN pad. An error message “Credit Timeout” displayed on the POS. This was corrected and now the transaction is approved.
8. The AID was missing from only the outdoor EMV contactless transaction receipts. This was corrected and now it is printed.
9. 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.

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

1. When a gift card was swiped during a balance inquiry, the PIN pad displayed the “Rewards Customer Yes/No?” prompt. This was corrected and now the “Reward customer Yes/No” prompt will not display for the Balance Inquiry.
2. When an invalid loyalty ID was scanned using a bar code, the system continued to loop infinitely.This was corrected and now after scanning an invalid loyalty ID barcode for three times, the system will skip that particular loyalty program and continue with payment or with next available loyalty program.
3. On the MX 900 Series PIN pad, the loyalty program name was not displayed on the “Use Loyalty ID/Card” screen when Alternate ID was disabled. This was corrected and now the program name is displayed.
4. On Verifone Commander distributions with no primary FEP, EPS loyalty transactions were failing. This was corrected and now loyalty transactions will complete successfully without failure.
5. 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.

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

1. For POP PPG discount, the discount amount was set as the applied discount. This caused incorrect fuel totals in the Product Systems Product Code Movement Report, because the POP PPG discount amount was added to the totals of the fuel products. This was corrected and now the PPG applied discounts are prevented from getting added to the fuel totals in Payment Systems Product Code Movement Report. It also ensures that the POP post fueling discounts continue to get added to the fuel product totals in the Payment Systems Product Code Movement Report as expected.
2. 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.

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

1. There was an inconsistency in the calculation of the per product total sales for cash and credit transactions for the product codes in the NAXML Movement Report. This was corrected and now th totals are calculated correctly.
2. There were inconsistencies in the NAXML Payment Systems Product Code Report for transactions with line item discounts and different number of special product codes(tax, split tender, etc.). This was corrected.
3. The Full Station Data NAXML report displayed equal values for the Station Net Grand Total and Station Grand Total even though transactions in that period had loyalty line item discounts and loyalty ticket level discounts. This was corrected and now Station Grand Total and Station Net Grand Total will differ by the total discount amount.
4. On the Payment Systems Product Code Report, when a manual discount was applied on all items in the menu order item, the product total for the first item part of the order item displayed a gross total and then for the rest, it displayed a net total (a total subtracted by discount amount). Also, the discount product code displayed only the amount equal to the discount applied on the first item of the order item. This was corrected and now the totals will be calculated consistently for all the item lines within the composite item line.

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

1. When the minimum PPU was set as one dollar at the POS and the street price was less than the discounted price, the discount was displayed on the receipt, but the discount was not fully applied due to a rounding issue. This was corrected and now the full discount is applied.
2. When a tip was applied to a transaction and there was a network payment failure, the tip was not removed. This was corrected and now the tip is removed.
3. When charity was selected and added to a Fleet Card transaction, the message “Invalid Products” was displayed on the POS screen. The cashier had to void the transaction and begin a new transaction. If charity was added to a Fleet Card transaction and the cashier selected the line item and chose the “VOID LINE” option, the system did not perform the intended operation and the line item was not marked as voided. This was corrected and now the charity item line can be voided by the cashier and sent to the network host for approval.
4. “Age restricted” menu key items were not allowing the quantity to be greater than ‘1’ during the first scan. This was corrected and now the correct quantity is now allowed.
5. 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 id="bookmark90" align="center">FEP Specific Changes</h2>

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

#### Resolution <a href="#bookmark92" id="bookmark92"></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="#bookmark93" id="bookmark93"></a>

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

1. When a car wash was added to a loyalty transaction, there was an additional carriage return. This was corrected.
2. The “PIN USED” text in the receipt table had incorrect validation. As a result, the text was printed on all receipts where debit cards were used, regardless of whether a PIN was actually entered. The validation was corrected.
3. 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 and now the cashback prompt is displayed.

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

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

1. Terminal Transaction Qualifiers (TTQ) values for VISA and Union Pay were incorrect in the Application Identifier (AID) table. These were corrected.
2. Voyager EMV and MSR reversals were not being sent to the host. This was corrected and now Voyager reversals are sent.

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

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

The “PIN USED” text in the receipt table had incorrect validation. As a result, the text was printed on all receipts where debit cards were used, regardless of whether a PIN was actually entered. The validation was corrected.

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

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

1. Terminal Transaction Qualifiers (TTQ) values for VISA and Union Pay were incorrect in the Application Identifier (AID) table. These were corrected.
2. Voyager EMV and MSR reversals were not being sent to the host. This was corrected and now Voyager reversals are sent.
3. “Account Type” and “Network Name” fields were blank on the Visa and Mastercard Fallback receipts. This was corrected and now the “Account Type” and “Network Name” fields are populated.
4. The last two digits in the Verifone Commander Software release version were getting cut off in the Phillips 66 Salesforce Reporting. This was corrected and they are no longer cut off.
5. 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 and now the configuration is retained.
6. Credit and Debit refunds were failing due to high STAN numbers created by the EPS. This was corrected.

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

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

**Fiserv PTPE Cloud BIN Service (CBS)**

The Verifone Commander now supports the Fiserv Cloud BIN Service (CBS). The Cloud BIN Service is also known BIN Exclusion. It does not encrypt certain BIN ranges that are not required to be processed by Fiserv. They have introduced a new cloud BIN management service in their commerce hub that can manage BIN exclusions without updating any configuration files. The Cloud BIN Service objective is to implement a P2PE (Point-to-Point Encryption) methodology where the BIN exclusion is centralized in the cloud, reducing the need for implementation on individual devices at each site. This approach enhances efficiency and ensures consistent, scalable management of BIN exclusions across the entire network.

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

1. Visa Fleet prompt entries, such as Vehicle Number and Driver ID, were not printing on the preauthorization merchant receipt. This was corrected and now are printing on the merchant receipt.
2. When an electronic void transaction was initiated for an approved manual fuel transaction, Comdata cards with BIN range 560017 were getting declined locally. The decline was due to a parameter reversal allowed in Buypass Parameters set to false. This value came from the PDL.This was corrected by adding a null check.
3. EBT was not added to the dual-use indicator, so the EBT prompt was not displayed on the PIN pad. The transaction was declined as “CARD NOT ALLOWED.” This was corrected. EBT was added to the dual-use indicator. The PIN pad will now prompt for Credit, Debit and EBT. The customer will select EBT and then the transaction will process as EBT.

### Test FEP <a href="#test_fep" id="test_fep"></a>

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

**Contactless Payment**

Contactless payment for inside and outside transactions was enabled in the Verifone Test FEP distribution.

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

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

1. Terminal Transaction Qualifiers (TTQ) values for VISA and Union Pay were incorrect in the Application Identifier (AID) table. These were corrected.
2. When refunding a Visa Fleet transaction, the POS was displaying “Invalid Reference Number” even though the correct reference number was entered at the prompt. 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-56.03.00/whats-new-in-version-56.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.