EVPay on Android M425

EVPay software updates and the refreshed EVPay interface for the Android M425.

Overview

The M425 is Verifone's Android payment terminal for the counter. EVPay runs on the terminal and handles card entry, PIN entry, contactless payments, and customer prompts.

This release adds three EVPay improvements for M425 sites:

• VHQ updates (PPA-99) let Verifone deliver EVPay updates remotely.
• Commander/EPS updates (PPA-98) add a second update path through the site controller.
• UI revamp (PPA-20) refreshes the EVPay screens across Android and legacy devices.

These changes do not change payment processing. Card, PIN, and contactless flows work the same way.

Key concepts

• M425 — Verifone's Android PIN pad for the counter. It replaces older devices such as the M400.
• 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.

Available from Base 057.01.00.

VHQ-managed updates are handled by Verifone or your help desk. Site staff do not approve or schedule each update.

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.

Planned for Base 057.02.00. Until then, M425 EVPay updates are delivered through VHQ.

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.

Devices covered

The refreshed design applies to the M425, M450, P630, UX700, and VICTA Portable. It also applies to legacy VOS terminals such as the M400.

Behind the scenes

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

Available from Base 057.01.00.

No retraining is required. Customers still insert, tap, or swipe and follow the same prompts.

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. Base 057.01.00 uses VHQ. Commander-managed updates are planned for Base 057.02.00.

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 supported legacy VOS terminals.

Quick reference

• VHQ updates — Remote EVPay updates for M425. Available in Base 057.01.00.
• Commander/EPS updates — Commander-managed EVPay updates for M425. Planned for Base 057.02.00.
• UI revamp — Larger text, clearer buttons, and improved screen layout. Available in Base 057.01.00.
• Site action — None for automatic updates.
• Customer impact — Clearer screens. Same payment flow.