> 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-release-notes-and-certifications/commander-55.02/commander-55.02.11-release-notes.md). # Commander 55.02.11 Release Notes ## Versions and Information
Release (Base) Version55.02.11
Release DateJuly 7, 2026
Publication DateJuly 7, 2026
## Distribution Components
Release055.02.11
OS6.01.00
EPS9.06.02
RCI6.00.01
WEB5.05.00
FEPSuiteFEP VersionEVPAYViperPAYNetwork
Buypass55.02.11UMF 55.02.112.06.00 r044.07.11TPPID: RVE106
Chase55.02.1155.02.112.04.02 r014.07.11—
Chevron55.02.1108.55.02.112.04.02 r014.07.11—
HPS55.02.1155.02.112.06.00 r044.07.11—
NBS55.02.1155.02.112.04.02 r014.07.11—
Phillips 6655.02.1155.02.112.06.00 r044.07.1143
Shell55.02.1155.02.11N/A4.07.11—
VAPS55.02.1155.02.112.06.00 r044.07.1104
Verifone EPS (LAC)55.02.1155.02.112.04.02 r014.07.11—
WorldPay55.02.1155.02.112.04.02 r014.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 padVersionXPIKernelsOS Version
PIN padVersionXPIKernelsOS Version
Verifone MX 900 Series4.07.115300w2Velocity L2 702/703Minimum - 30140200
Recommended - 30251000
--- # 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://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-highlights-user-guides-release-notes-and-certifications/commander-55.02/commander-55.02.11-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.