> 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-55.02/commander-55.02.12-release-notes/whats-new-in-release-55.02.12.md).
# What's New in Release: 55.02.12
Release Summary
This release delivers the EVPAY 2.04.05/2.08.01 upgrade packages to Commander distribution and resolves a range of loyalty, payment, and system-stability issues across the platform. Key resolutions address stuck PIN pad and point-of-sale states during loyalty transactions and balance inquiries, incorrect Visa Fleet Card fuel-quantity declines, and Auto Upgrade failures affecting login, onboarding, and update completion. Brand-specific improvements include corrected loyalty messaging and TLS retention for Phillips 66, expanded multi-loyalty-discount support for Sunoco, and a resolution preventing EBT voids and duplicate charges at Shell/Vista sites. Additional corrections improve age-verification handling, transaction log accuracy, and self-checkout loyalty discount behavior.
Enhancement
### 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
### Loyalty
1. 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)
2. 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)
3. 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)
4. 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)
### EPS System
1. 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)
2. 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)
### POS System
1. Users were occasionally unable to log into Verifone Commander Configuration Client, receiving a timeout error, with the only recovery being a full Commander reboot. This was corrected and now the user can log in as expected. (138674)
2. 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)
3. 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)
### Reports
On sites configured to keep detailed transaction logs for Daily periods only (not Shift periods), the Shift period's transaction log could end up with a large number of duplicate transaction records after period close, due to an incorrect file path in a system configuration lookup. Transaction totals were not affected, but the duplicate records could throw off reporting and other systems that count individual transactions. The configuration lookup now points to the correct file, so Shift period logs no longer contain duplicate entries. (139756)
### Sales
1. 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)
2. When a customer paid for an age-restricted item along with a prepay fuel purchase, and the fuel sale came in under the prepaid amount, the system would incorrectly ask for ID again when handling the refund for the unused amount. The system no longer re-prompts for ID in this scenario, and adding a new age-restricted item to that refund transaction is blocked. (111172)
FEP Specific Changes
### 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)
#### Resolution
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)
### 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-55.02/commander-55.02.12-release-notes/whats-new-in-release-55.02.12.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.