> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-highlights-user-guides-and-release-notes/commander-55.02/commander-55.02.09-release-notes/whats-new-in-release-55.02.09.md). # What’s New In Release: 55.02.09

Resolutions

### Verifone Configuration Client 1. DNS Name configuration was missing on the Verifone Commander when performing an Auto Upgrade. This was corrected. (128030) 2. Frequent Configuration Manager error messages occurred when attempting to log in to the Verifone Configuration Client. Additionally, within the Verifone Commander Configuration Client, various command failures were observed—including errors when saving, initializing, refreshing, or accessing the Helpdesk Diagnostics tabs. These were corrected. (130870) ### Dispensers A watch pump lockup occurred because the Bennett driver processes queued commands for each fueling position and only issues poll commands when the queue is empty; under certain conditions, such as an increased watch pump rate, the queue remained continuously populated, preventing the poll needed to detect the EOT transition. This was resolved by sending a poll command alongside every Get Sale Data command to ensure EOT triggers are not missed. (129459) ### Dispenser Card Readers A CAPK06 error occurred when processing cards if an FCC EMV initialization happened while the position was not idle. Before this change, the EMV configuration update was not applied until the second transaction after the initialization, causing the in-progress and subsequent transaction to run without the update. This change now applies the EMV update before the next transaction, preventing FCC from executing any new transactions without the latest configuration. (128545) ### EPS System 1. 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. (119478) 2. For legacy Visa Fleet 1.0 transactions on FlexPay6 DCR, the system was detecting the fleet prompt within Track 2 Discretionary Data (Tag 57), but the prompt was not displayed at the dispenser. Visa Fleet 2.0 transactions were not affected. This was corrected and now the prompts are displayed. (126705) ### Loyalty 1. After upgrading to 55.02.07, pressing the Cancel softkey on the PIN pad during the Rewards redemption prompt caused the transaction to fully abort and return a Decline after the payment card was read and the Get Rewards response was received. This was corrected. (131552) 2. When Multiple Loyalty Discounts in the Same Transaction was disabled, selecting a Loyalty FEP in a transaction with a hybrid card caused all loyalty cards to be routed to that Loyalty FEP; this was corrected by validating Loyalty FEP eligibility per loyalty card before routing. (131663) ### POS System 1. ID cards lacking date-of-birth information, such as certain medical marijuana cards, were previously accepted using a default DOB of 01/02/01. The POS now correctly rejects these IDs as invalid. (127996) 2. When Cash Rounding Adjustment was enabled, cash prepay transactions that included a decimal amount may print incorrect $0 completion receipt calculations and it also impacted reporting. This was corrected. (129232) 3. The following cash rounding issues were corrected: * Rounding Adjustment was added incorrectly to receipts when a Non-Taxable Coupon was used and tax was credited * Rounding Adjustment was applied but not displayed on receipts when a Special Discount was used * Cash prepay transactions with decimal amounts printed incorrect $0 receipt calculations, impacting reports * Totals under $0.05 did not allow entry of $0.00 or values below $0.05 * Line items displayed incorrect rounding amounts due to a casting issue * Rounding issues occurred when Cashback was applied * Rounded amounts were displayed as Change instead of Rounding Adjustment * Rounding Adjustment did not appear on receipts during split transactions * Rounding Adjustment appeared on the ODSP screen but was missing from receipts * Rounding Adjustment tags appeared on the ENTER SALES EMPLOYEE / Exit screen * Rounding was not recalculated when charity was applied to a sale * $0.02 refund transactions were not cleared correctly * Rounding issues affected CSR reports * Rounding values were missing from refund sales in the cashier (POS) report (130797) 4. The DVR issue occurred because the system always logged the last payment line, and when rounding added an extra line at the same moment as the CASH payment, the ROUNDING line was logged twice while the CASH line was skipped. The resolution now keeps track of which payment lines have already been logged, so only new ones are written and both CASH and ROUNDING are recorded correctly. (131373) 5. The difference between the original transaction total and the rounded cash total was only calculated at the TOTAL key press and was not recalculated after partial credit payments, resulting in incorrect rounding behavior. This was resolved by recalculating this amount at Release 55.02.09 Verifone Petro Software Release Notes Proprietary + Confidential. © Verifone Inc. All rights reserved. 17 each payment line initialization to ensure the Rounding Adjustment is applied correctly. (129475) 6. The DVR did not display ID validation or the date and time stamp. This was corrected. (131609) ### Sales Adjusting a combo discounted item with restricted quantities to an unapproved amount and then restoring it within the same transaction could leave the system in an inconsistent state because quantity voids recreate the line item, leading to incorrect totals or validation errors. This resolution ensures quantity restoration no longer creates conflicting line item states, keeping totals and validations accurate throughout the transaction. (130869)

FEP Specific Changes

### HPS FEP #### Enhancement **Price Value** The Price value in Product Data Format element 63 was operating as designed under \ Specification version 23.1; however, Specification version 24.1 deprecated value 3 in favor of 4 \ for Visa Fleet 2.0, requiring an update to element 63. Merchandise processing was updated to \ send a space for service level and to include amount and quantity. (121950/122300) #### Resolution Time conversions used milliseconds instead of seconds, causing site asset data to be sent after \ two months instead of 90 minutes. This was corrected and now all time conversions have been \ corrected to use the correct units. (128808) ### Rapid Connect FEP #### Resolution EBT void transactions attempted to send Track 2 data after it had already been cleared, resulting \ in neither Track data nor PAN being sent. This was corrected by sending the PAN as required by \ the specification. (133105) ### Verifone EPS #### Resolution In the Verifone EPS distribution, some Latin America and Caribbean timezones were missing. \ These were added. (133248) --- # 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 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-highlights-user-guides-and-release-notes/commander-55.02/commander-55.02.09-release-notes/whats-new-in-release-55.02.09.md?ask= ``` 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.