> 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.md). # Commander 56.03.03 Release Notes ### Versions and Information | Release (Base) Version | 56.03.03 | | ---------------------- | ------------------ | | Release Date | September 30, 2026 | | Publication Date | September 30, 2026 | **Distribution Components** | **Release** | 056.03.03 | | ----------- | --------- | | OS | 6.02.00 | | EPS | 9.09.00 | | RCI | 6.00.01 | | WEB | 5.05.00 | | Network | FEP | Suite | FEP Version | EVPAY | ViperPAY | | ------------ | -------- | ----------- | ----------- | ------- | -------- | | Buypass | 56.03.03 | 56.03.03 | 2.08.01 r01 | 4.07.11 | — | | Chevron | 56.03.03 | 08.56.03.03 | 2.04.05 r01 | 4.07.11 | — | | Verifone EPS | 56.03.03 | 56.03.03 | 2.04.05 r01 | 4.07.11 | — | {% hint style="info" %} The EVPAY and ViperPAY versions listed above are bundled with the software. They do not convey their release status/state. {% endhint %} ### PIN Pad Software Versions #### Minimum EVPAY (Engage) Certified Versions For the EVPAY (Engage) Certified Versions for Verifone M400 and P400, click on [Current VRSD Production Software List ](https://docs.verifone.com/petroleum-docs/vrsd-updates/software-updates-vrsd/current-vrsd-production-software-list). #### Attendant Payment Terminal (APT) Version This Verifone EPS (LAC) Commander software requires APT version 1.03.08. #### Minimum EMV Certified Verifone ViperPAY Versions | PIN pad | Version | XPI | Kernels | OS Version | | ----------------------------- | --------------- | ---------- | -------------------------- | ---------------------------------------------- | | PIN padVerifone MX 900 Series | Version 4.07.11 | XPI 5300w2 | KernelsVelocity L2 702/703 | OS VersionMinimum - 30140200Recommen- 30251000 | ## Important Information #### Table Updates Table changes for Release 56.03.02 are now published, affecting FEPs NTS/VAPS (CITGO) and NBS. #### Ticket References Ticket numbers appearing in parentheses at the end of each new feature, enhancement and resolution (e.g., 135924) correspond to internal development tracking references and can be used when contacting Verifone support for additional information related to a specific change. #### Security Log Servers After configuring security log servers in Verifone Commander Configuration Client, reload the form after clicking Save to ensure the changes are stored correctly. If a slot does not save as expected, temporarily assign a placeholder IP address, save, and then update it to the intended IP. #### Prompt Restriction Outside “Prompt Restriction Outside” is no longer needed for the Verifone Commander 55.02.05 and higher versions except for the 56.00.00 and 56.01.00 versions. #### White-Labeled Printer White-label firmware is required for the RP-700 printer. For more information on the Verifone RP-700 printer, see the Verifone RP-700 Printer Installation Guide at the Verifone Premier Portal > Manage > Petro Downloads > Fuel and Hardware Peripherals > Printers. **Verifone RP-700 Printer** Details specific to the white-labeled Verifone RP-700 receipt printer are provided below: * Part Number (PN): 930001L13A018 * White-Label Firmware Versions: * **Boot Firmware**: FV1.010 * **Main Firmware**: FV1.101.02 To verify the firmware: {% stepper %} {% step %} ### Turn off the printer {% endstep %} {% step %} ### Hold the Feed button and power the printer on A self-test printout will be generated. {% endstep %} {% step %} ### Check the firmware version The firmware version should appear near the top of the printout. {% endstep %} {% endstepper %} #### Fuel Initialization Fuel initialization must be initiated when all dispensers are idle. Site should use an appropriate method, such as Site Pause, bagging handles, or placing cones, to prevent authorization attempts while fuel initialization is in progress. Otherwise, unintended consequences may occur. #### Verifone Commander Registration If a site is auto upgrading using a USB flash drive or the autoupgrade.jar process, the Verifone Commander will need to be re-registered. Only auto upgrades sent through the VRSD request will maintain registration. #### M400 PINpad Automatic Software Updates M400 PINpads connected on the Verifone Commander system loaded with EVPAY 2.03.03 r04 or higher will automatically upgrade to the version listed in the Distribution Component Versions section. Also, the Shell FEP will not automatically upgrade to any EVPAY version. #### Upgrading From Release 53.26 or Lower to Release 55.02 and Higher If a site is upgrading from release 53.26 or lower to release 55.02 and higher, it is recommended to use the following instructions instead of the Package Sender (Auto\_Upgrade.jar): {% stepper %} {% step %} ### Back up site data Back up the site data using the SMS Import/Export Utility. {% endstep %} {% step %} ### Perform a manual reload Perform a manual reload using the Petro Suite Installer. {% endstep %} {% step %} ### Restore site data Restore the site data using the SMS Import/Export Utility. {% endstep %} {% endstepper %} The alternative software loading methods are VRSD and USB. See the Verifone Commander and POS Software Installation Guides for more information. #### Verifone Expired Site Solution (ASM) and Onboarding Messages Starting with Release 53.41.00, expired Site Solution (ASM) and C-Site Management Onboarding requirement messages and alarms will display on the POS. The messages briefly explain the appropriate actions that the site needs to take for the messages to stop. #### Base Release, Suite, and FEP Version Alignment Starting with Release 55.00.00, the Distribution Suite and FEP version have been updated to align and, in most cases, have the same version as the Base version. #### OS Update Starting with Release (Base) 55.00.00, the Verifone Commander and POS Workstations will now share one common OS with SELinux (Security-Enhanced Linux). #### Downgrading from Release (Base) 55 to a Lower Version If a site needs to downgrade their Verifone Commander or POS from Release (Base) 55.00.00, follow the procedures in the downgrade document located at: * Premier Portal > Manage > Petro Downloads > Commander & RubyCi > Commander Tools, User References, and Other Documentation > Documentation * Premier Portal > Manage > Petro Downloads > Commander & RubyCi > POS > C18, Ruby2, or Topaz Documentation areas. #### Release 55.00.00 and POS Pairing The POS Pairing process may take up to two additional minutes to complete while “Processing, please wait...” is displayed on the POS workstation screen. Do not reboot the POS while this message is displayed. #### Lab, Beta, or Production Software Status See the Lab, Beta, or Production software sections on the Premier Portal for the release status of each FEPʼs software at Manage > Petro Downloads > Commander and RubyCi > Commander Software Suites, Release Notes and Documentation. These release notes contain all the information for all release statuses. #### Configuring the Verifone C18 when using a Legacy Scanner Sites that do not have a 2D scanner will need to disable swipe ahead in order to process Easy ID or a POP Membership card at the PIN pad. Do the following two steps consecutively: {% stepper %} {% step %} ### Disable Swipe Ahead on the Verifone C18 POS On the Verifone C18 POS, disable Swipe Ahead at Cashier Functions (CSR Func) > Maintenance > Device Configuration > PINPAD configuration > EPS PINPAD with Driver License and POP Membership. {% endstep %} {% step %} ### Disable Swipe Ahead on the Verifone MX 900 Series PIN pad Edit the Config.Usr1 Swipe Ahead value found in System Mode at Home > Administration > Config by entering the Config.Usr1 file. Under the \[PERM] section, there will be a Swipe Ahead parameter with a '0' or a '1' value. The value should be set to ‘0ʼ to disable it. After the change, reboot the PIN pad. {% endstep %} {% endstepper %} See the Commander User Reference for Release 55.02 for more information on scanners. #### EMV Certified This software version supports Contact and Contactless Indoor. See the Dispenser Card Reader section towards the back of these release notes for EMV Contact and Contactless Support for each dispenser manufacturer. #### Verifone EPS (LAC) Outdoor EMV Outdoor EMV is only for Trinidad and Tobago locations. #### Transport Layer Security (TLS) Support {% hint style="info" %} The steps below are only required for a manual software installation. The Auto Upgrade automatically sets the TLS settings. {% endhint %} To set up TLS and if this is a manual software installation: {% stepper %} {% step %} ### Configure the Verifone MX PINpad Set the Port to ‘5000ʼ at Configuration > Network Settings. {% endstep %} {% step %} ### Configure the Verifone Commander Configure the POP to “Connect with SSL” and Secure Port ‘5000ʼ at Configuration Client > Payment Controller > EPS Global Configuration > POP. {% endstep %} {% endstepper %} See the latest Verifone ViperPAY User Guide and Commander documentation for more details on accessing these areas. #### Buypass Software Installation During the software installation, the system prompts for Brand Selection. Choose from the drop-down menu and then click OK. After installation, see the Help Menu and the About to check the Brand selection. #### VAPS Software Installation During the software installation, the system prompts for Brand Selection. Choose from the drop-down menu and then click OK. After installation, see the Help menu and the About to check the Brand selection. #### Verifone Remote Software Delivery (VRSD) The Verifone Commander supports the Verifone Remote Software Download (VRSD) to allow automated software updates from the Verifone servers. See the Verifone Remote Software Delivery Implementation Guide for more information. #### FEP Configuration Documentation See the Verifone Commander Network Configuration Guide. ## What’s New In Version: 56.03.03 ### --- # 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.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.