> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/customer-documentation/petro-and-c-store/commander-highlights-user-guides-release-notes-and-certifications/commander-56.03/commander-56.03.03-release-notes/whats-new-in-version-56.03.03.md).
# What's New In Version: 56.03.03
Release Summary
Verifone Commander Release 56.03.03 covers a maintenance update spanning EPS/payment system resolutions, loyalty prompt and receipt issues, POS auto-upgrade reliability, and an age-verification safeguard, plus an EVPAY software distribution enhancement. A notable cluster addresses FEP-specific issues across Chevron (auto-upgrade file preservation and day-close sign-on delays), Phillips 66 (TLS settings reset after upgrade), Rapid Connect/Sunoco (loyalty discount handling and a POS lockup resolution), and Shell (duplicate-charge risk on Vista/Mashgin). Several resolutions resolve customer-facing payment failures — including incorrect Visa Fleet declines, Comdata partnership card misidentification, and a double-charge scenario — while others improve day-to-day reliability for loyalty balance inquiries and currency/locale configuration syncing.
Enhancements and New Features
### EPS System
#### **EVPAY**
EVPAY 2.04.05 R01 and 2.08.01 R01 upgrade packages were added to the Commander distribution, enabling sites to upgrade their EVPAY software through the standard update process. (139480, 138825, 139066)
Resolutions
### EPS System
1. When a Numeric Currency Code (or other locale settings) was updated for a site in Commander Central, the change didn't fully carry over to the Commander at that site. This could leave payment-related settings, such as EMV transaction currency fields, out of sync with what was configured in Commander Central. This issue has been resolved — currency and locale updates made in Commander Central now correctly apply to the Commander. (139403, 138186)
2. Some cards sharing an overlapping number range with Comdata's OTR Fleet BIN were being mistakenly processed as Comdata Fleet cards. This has been corrected so that non-Comdata cards in that range are properly excluded from Comdata Fleet processing and are no longer misidentified at the pump. (140860)
3. Visa Fleet Card postpay fuel transactions could be incorrectly declined with an “amount data is more than expected” error whenever the fuel quantity was 100 or more gallons/liters. Transactions of any quantity now process correctly. (139023)
4. After completing a loyalty balance inquiry, the PIN pad could remain stuck showing “WAITING FOR CASHIER” until the next transaction was started, even though the balance receipt had printed correctly. The PIN pad now displays “Welcome to the Store” after the inquiry completes instead of getting stuck on that message. (140633)
### Loyalty
1. When a loyalty discount reduced a self-checkout transaction to a $0.00 balance, the checkout button remained disabled, leaving the customer unable to complete the transaction or leave the terminal. The checkout button now stays enabled whenever items remain in the basket, even if the loyalty discount brings the balance due to zero, and the transaction completes without requiring a payment card. Customers are shown an on-screen message confirming that no payment was needed for the transaction. (137756)
2. The PIN pad displayed a generic “Loyalty Card Invalid” message instead of the specific message sent by the loyalty host. Customers will now see the accurate, host-provided message when a loyalty card cannot be validated. (139441)
3. Loyalty balance inquiries would leave the PIN pad stuck on “waiting for cashier” with no balance displayed or printed, even though the loyalty host had successfully returned the balance information. Balance inquiry receipts now print and display correctly. (140143)
4. If a customer entered or swiped an invalid loyalty card, the system displayed "Loyalty Card Invalid" and moved straight to payment instead of allowing another try. This has been corrected — customers are now properly prompted to retry, up to the intended three attempts, before the system proceeds with payment. (140634)
### POS System
1. During an Auto Upgrade, some sites experienced the upgrade being immediately aborted with an error indicating a required internal service could not be found, without any way to recover other than reloading the Verifone Commander. This was corrected now it completes successfully. (138669)
2. After an Auto Upgrade, some Commander sites failed to stay onboarded to Commander Central, showing a “Site not onboarded” error even though the site's asset data still reflected the prior release. This was corrected and it now allows the site to remain correctly onboarded after an upgrade. (137889)
### Sales
When a cashier scanned an item other than a valid ID during an age verification check, the prompt would disappear and the restricted item would be removed from the sale without any clear indication, risking a restricted item being sold unverified if the cashier was scanning quickly. The age verification screen now stays on the prompt after an invalid scan or swipe, simply displaying an error message so the cashier can retry. The scanner and PIN pad are also automatically re-armed so a retry can be completed without further intervention. (138546)
FEP Specific Changes
### Chevron FEP
**Resolutions**
1. There was an issue where certain files required for Auto Upgrade could occasionally fail to be preserved during the upgrade process, which could cause the upgrade to report a failure even after installation had completed. The system now detects and recovers these files automatically, improving upgrade reliability. (138990)
2. There was an issue that could cause an extended delay — several minutes — during day close, with the point of sale displaying "Offline Sign On In Progress. Try again later" and unable to process transactions. This occurred only if the offline authorization port setting had been changed without restarting the system. Day close now consistently uses the current port setting for offline sign-on, removing the need for a restart in this scenario. (139064)
3. In certain conditions, day close could result in an extended delay — up to several minutes — with transactions blocked at the point of sale even though the host had already responded successfully. Day close now reliably completes its sign-on process without this delay. (139456)
### Phillips 66 FEP
**Resolution**
After an Auto Upgrade, sites found that the TLS/SSL setting for their loyalty network connection had been disabled, requiring it to be manually re-enabled. The TLS settings are now carried forward from the site's prior configuration during the upgrade merge, so they remain intact after upgrading. (137399)
### Rapid Connect FEP
#### **Enhancement**
**Multiple Loyalty Discounts**
For Sunoco locations, the Multiple Loyalty Discounts in Same Transaction setting is now enabled by default on fresh installs and automatically re-enabled after an upgrade. Both indoor PIN pads and outdoor dispenser card readers now allow more than one loyalty program to be applied within the same transaction. The setting is enforced going forward so it cannot be inadvertently disabled. (139014)
**Resolutions**
1. When a cashier attempted to void a ticket that included an EBT payment, the Verifone Commander sent a reversal message to the EBT host that the host does not support and declines, since EBT SNAP transactions cannot be reversed once completed. The POS now prevents a ticket from being voided once an EBT or EBT cash-benefit payment has been applied to the transaction. If a correction is needed, the cashier completes the sale and processes a separate manual refund transaction instead. (134145)
2. When a loyalty discount on an in-house account prepay exceeded the configured per-gallon dollar limit, the POS would lock up displaying change due, and the associated fueling position became stuck, requiring a register reboot to recover. This happened because the system was dismissing a shared on-screen prompt the moment it paused, hiding the cashier acknowledgment overlay that the transaction was waiting on. The system no longer dismisses that shared prompt when it pauses, so the acknowledgment remains visible and the transaction can be completed normally. (139075)
### Shell FEP
**Resolution**
On sites using VISTA/Mashgin, a card could be successfully charged while the point of sale incorrectly reported the payment as failed — leading customers to be charged twice if they retried. Payment results are now handled correctly so this can no longer occur. (138102/138336)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://commanderhelp.verifone.com/customer-documentation/petro-and-c-store/commander-highlights-user-guides-release-notes-and-certifications/commander-56.03/commander-56.03.03-release-notes/whats-new-in-version-56.03.03.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.