> 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-57.01/commander-57.01.00-release-notes.md).

# Commander 57.01.00 Release Notes

## Versions and Information

| **Release Version**  | 57.01.00      |
| -------------------- | ------------- |
| **Release Date**     | July 21, 2026 |
| **Publication Date** | July 21, 2026 |

## Distribution and Component Versions

| **Buypass Distribution** | **Names** | **Versions** |
| ------------------------ | --------- | ------------ |
| **Foundation**           | Buypass   | 57.01.00     |
| **EPS**                  | Buypass   | 57.01.00     |
| **Network Version**      | TTPID     | RVE106       |
| **UMF**                  |           | 57.01.00     |
| **Bundled EVPAY**        |           | 2.08.00 r09  |
| **Bundled ViperPAY**     |           | 4.07.11      |

| **Chevron Distribution** | **Names** | **Versions** |
| ------------------------ | --------- | ------------ |
| **Foundation**           | Chevron   | 57.01.00     |
| **EPS**                  | Chevron   | 57.01.00     |
| **Network Version**      |           | 08.57.01.00  |
| **Bundled EVPAY**        |           | 2.08.00 r09  |
| **Bundled ViperPAY**     |           | 4.07.11      |

| **HPS Distribution** | **Names** | **Versions** |
| -------------------- | --------- | ------------ |
| **Foundation**       | HPS       | 57.01.00     |
| **EPS**              | HPS       | 57.01.00     |
| **Bundled EVPAY**    |           | 2.08.00 r09  |
| **Bundled ViperPAY** |           | 4.07.11      |

| **Phillips 66 Distribution** | **Names**   | **Versions** |
| ---------------------------- | ----------- | ------------ |
| **Foundation**               | Phillips 66 | 57.01.00     |
| **EPS**                      | Phillips 66 | 57.01.00     |
| **Network Version**          |             | 49           |
| **Bundled EVPAY**            |             | 2.08.00 r09  |
| **Bundled ViperPAY**         |             | 4.07.11      |

{% hint style="info" %}
The EXE file name has been changed from Phillips 66 to COP (Cop\_F57.01.00-\
V57.01.00\_productionSigned.exe).
{% endhint %}

| **Shell Distribution** | **Names** | **Versions** |
| ---------------------- | --------- | ------------ |
| **Foundation**         | Shell     | 57.01.00     |
| **EPS**                | Shell     | 57.01.00     |

| **VAPS Distribution** | **Names** | **Versions** |
| --------------------- | --------- | ------------ |
| **Foundation**        | VAPS      | 57.01.00     |
| **EPS**               | VAPS      | 57.01.00     |
| **Network Version**   |           | 10           |
| **Bundled EVPAY**     |           | 2.08.00 r09  |
| **Bundled ViperPAY**  |           | 4.07.11      |

{% hint style="info" %}
The EXE file name has been changed from VAPS to NTS (Nts\_F57.01.00-\
V57.01.00\_productionSigned.exe).
{% endhint %}

| **VerifoneEPS (LAC) Distribution** | **Names**   | **Versions** |
| ---------------------------------- | ----------- | ------------ |
| **Foundation**                     | VerifoneEPS | 57.01.00     |
| **EPS**                            | VerifoneEPS | 57.01.00     |
| **Bundled EVPAY**                  |             | 2.08.00 r09  |
| **Bundled ViperPAY**               |             | 4.07.11      |

| Components  | Versions  |
| ----------- | --------- |
| **Release** | 057.00.00 |
| **OS**      | 6.02.00   |
| **EPS**     | 9.09.00   |
| **RCI**     | 6.00.01   |
| **WEB**     | 5.05.00   |

{% 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).

{% hint style="info" %}
If VCL (TAVE key) is used, the PIN pad must have the EVPAY 2.08.00 R09 version.
{% endhint %}

#### Attendant Payment Terminal (APT) Version

This Verifone EPS (LAC) Commander software requires APT version 1.03.08.

#### Minimum EMV Certified Verifone ViperPAY Versions

{% hint style="info" %}
For the ViperPay Certified Versions for Verifone MX PIN pads, click on [Current VRSD Production Software List](https://docs.verifone.com/petroleum-docs/vrsd-updates/software-updates-vrsd/current-vrsd-production-software-list).
{% endhint %}

Make sure the minimum OS and any OS Updates are loaded before installing Verifone ViperPAY. See the Verifone ViperPAY release notes.

| **PIN pad**                | **Version** | **XPI** | **Kernel**       | **OS Version**                                      |
| -------------------------- | ----------- | ------- | ---------------- | --------------------------------------------------- |
| **Verifone MX 900 Series** | 4.07.11     | 5300w2  | Velocity L2 7.02 | <p>Minimum - 30140200<br>Recommended - 30251000</p> |


---

# 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, and the optional `goal` query parameter:

```
GET https://commanderhelp.verifone.com/customer-documentation/petro-and-c-store/commander-highlights-user-guides-release-notes-and-certifications/commander-57.01/commander-57.01.00-release-notes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
