> 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/cug-57.02/commander-user-reference-57.02/evpay.md).

# EVPay

EVPay software updates and the refreshed EVPay interface for Verifone PIN pads, including the M425, M450, UX700, M400 and P400.

### Overview

EVPay is the payment application on Verifone PIN pads. It handles card entry, PIN entry, contactless payments, and customer prompts. This page covers the Android PIN pads (M425, M450 and UX700) and the legacy M400 and P400 PIN pads.

This release adds three EVPay improvements:

* **VHQ updates** let Verifone deliver EVPay updates remotely to the Android PIN pads.
* **Commander/EPS updates** add a second update path through the site controller.
* **UI revamp** refreshes the EVPay screens on the Android PIN pads and on the M400 and P400.

{% hint style="info" %}
These changes do not change payment processing. Card, PIN, and contactless flows work the same way.
{% endhint %}

### Key concepts

* **M425** — Verifone's Android PIN pad for the counter. It replaces older devices such as the M400.
* **M450 and UX700** — Other Android PIN pads that use the refreshed EVPay interface.
* **M400 and P400** — Legacy PIN pads. They receive the refreshed EVPay interface from Commander Release 57.02.
* **EVPay** — The payment application on the terminal. It shows prompts and passes payment data to the site controller.
* **VHQ** — Verifone's remote device management service. It can deliver approved software packages across a device estate.
* **Commander / EPS** — The site payment controller. It processes transactions and can distribute EVPay software packages.
* **Update window** — The scheduled idle period when software updates install.

### EVPay updates from VHQ

EVPay on the M425 can now update through VHQ. This gives Android sites the same remote, hands-off update path used across managed terminal estates.

#### What this adds

* Remote EVPay delivery with no site action.
* Consistent approved versions across all sites.
* Overnight installation during the update window.
* No interruption to active payments.

{% hint style="success" %}
Available from Commander Release **57.01**.
{% endhint %}

{% hint style="info" %}
VHQ-managed updates are handled by Verifone or your help desk. Site staff do not approve or schedule each update.
{% endhint %}

### EVPay updates from Commander and EPS

Commander can also deliver EVPay updates to the M425. This aligns Android terminal updates with the update flow already used for older M400 devices.

#### Update paths

1. **Automatic push from EPS**

   Commander pushes a newer approved EVPay package during the normal update window. If the terminal is busy, the update waits.
2. **On-demand from EPS Configuration**

   An operator or service representative can check the installed EVPay version and trigger an update when a newer approved package is available.

#### What this means for your site

* Commander can manage payment software and terminal software together.
* EVPay packages can ship with the normal Commander software distribution.
* Mixed M400 and M425 sites receive the correct package automatically.
* Support staff can verify the installed EVPay version from EPS Configuration.

### Refreshed EVPay interface

EVPay screens now use a cleaner layout across Android and legacy terminals. The update improves readability and touch accuracy without changing the payment flow.

#### Customer-facing changes

* Larger text for amounts, prompts, and button labels.
* Larger and clearer buttons.
* Better-sized selection buttons.
* Fewer scroll bars and wider scroll targets.
* Improved contactless icon placement.
* More visible choices on selection screens.
* On the M400 and P400, text on prompt screens such as loyalty program selection, charity donation and fuel rewards sign-up is larger, as easy to read as the amount-entry screens.
* On the M400 and P400, selection screens use individually sized buttons instead of full-width buttons, and show up to five choices on one screen without scrolling. For example, a tip screen shows three preset amounts, a custom amount and a no-tip choice.
* On the M400 and P400, the Rewards/Loyalty button sits away from the contactless (tap-to-pay) icon, including on screens that show line items, to reduce accidental taps.
* Where a list still needs a scroll bar, the scroll bar is wider and easier to grab.

#### Devices covered

The refreshed design applies to the **M425**, **M450** and **UX700**. It also applies to legacy VOS terminals, specifically the **M400** and **P400** PIN pads.

{% hint style="info" %}
The refreshed interface was first available on the Android terminals from Commander Release 57.01. On the M400 and P400 PIN pads it is available from Commander Release 57.02, when the refreshed EVPay build ships with the Commander software distribution.
{% endhint %}

{% hint style="info" %}
Starting in Commander Release 57.02, EVPay runs natively on the M450-A pinpad, hosted on Android 13, with full feature parity to the certified M425-A for EMV chip, contactless/NFC tap, magstripe, PIN entry, loyalty (up to 4 programs), cash back, fleet odometer, tip, charity, and signature capture. The EVPay UI is scaled to the M450-A's larger landscape display. EVPay for the M450-A is deliverable and upgradable OTA through both Auto Upgrade and VHQ.
{% endhint %}

#### Behind the scenes

EVPay installation packages now use fewer files and a cleaner install order. This makes installation and update handling simpler.

{% hint style="success" %}
Available on the Android terminals from Commander Release **57.01**. Available on the M400 and P400 from Commander Release **57.02**.
{% endhint %}

{% hint style="info" %}
No retraining is required. Customers still insert, tap, or swipe and follow the same prompts.
{% endhint %}

### What site staff will notice

* The PIN pad screens look different after the update.
* Customers need less help at the counter.
* The terminal may restart briefly overnight during updates.
* Site staff do not manually load EVPay updates.
* Payments and receipts stay the same.

### Frequently asked questions

#### Do I need both VHQ and Commander updates?

No. They are two update paths for the same EVPay application. Commander Release **57.01** uses VHQ. Commander-managed updates are planned for Commander Release **57.02**.

#### Can an update interrupt a payment?

No. Updates install during the update window. If the terminal is in use, the update waits.

#### How do I check the EVPay version?

With EPS-managed updates, support staff can view the installed version in **EPS Configuration**. VHQ can also report installed versions.

#### Do mixed M400 and M425 sites need special handling?

No. Commander identifies the terminal type and sends the correct package.

#### Do customers need to learn a new payment flow?

No. The screens look different, but the payment flow stays the same.

#### Does the refreshed interface apply to older terminals?

Yes. The refreshed design also applies to the M400 and P400 PIN pads, from Commander Release 57.02.

### Quick reference

* **VHQ updates** — Remote EVPay updates for M425. Available in Commander Release **57.01**.
* **Commander/EPS updates** — Commander-managed EVPay updates for M425. Planned for Commander Release **57.02**.
* **UI revamp** — Larger text, clearer buttons, and improved screen layout. Available in Commander Release **57.01** on the Android terminals and in Commander Release **57.02** on the M400 and P400.
* **Site action** — None for automatic updates.
* **Customer impact** — Clearer screens. Same payment flow.


---

# 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/cug-57.02/commander-user-reference-57.02/evpay.md?ask=<question>&goal=<user_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.
