> 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/pin-pads/implementation-guides/m425a/device-overview.md).

# Device Overview

## Device Overview

The Verifone M425A is a multi-lane, media-capable, consumer-facing PIN pad. It processes electronic payments and supports Verifone cloud services, advanced payment methods, and e-commerce capabilities.

The integrated camera scans barcodes, QR codes, and products. With Verifone Connect services, the terminal can run Android applications for loyalty and inventory. Verifone estate management supports remote monitoring and updates.

The M425A supports serial-over-USB and IP-over-USB communication with the ECR. It supports multiple SAM cards, video playback, and external power, USB, and Ethernet connections.

![M425A payment terminal](/files/f2ce161f5d84f1c9ebcbd1002d07b932abca82d1)

### Why upgrade terminals?

MX915, MX925, and M400 terminals are reaching end of support. MX900 devices reach end of service in 2026. M400 PCI validity expires in April 2026. A terminal cannot process payment cards after its PCI expiry.

The M425A runs Android and meets PCI PTS 6 and 7 requirements. This supports continued payment acceptance for years ahead.

| Previous terminals   | Platform               | M425A                                          |
| -------------------- | ---------------------- | ---------------------------------------------- |
| MX915 / MX925        | VOS                    | Android 13                                     |
| M400                 | VOS2                   | EVPay on Android with VIPA 7                   |
| End of service: 2026 | PCI expiry: April 2026 | PCI 6/7 validity for years ahead               |
| Limited card support | Limited card support   | Contactless, chip, swipe, fleet, and debit PIN |

### Terminal at a glance

| Feature             | Details                                                             |
| ------------------- | ------------------------------------------------------------------- |
| Screen              | 5.5-inch full-colour touchscreen                                    |
| Keypad              | Backlit tactile keypad for PIN entry                                |
| Operating system    | Verifone Secure OS on Android 13                                    |
| Payment acceptance  | Chip, contactless, magnetic stripe, and NFC                         |
| Digital wallets     | Apple Pay, Google Pay, Samsung Pay, and other NFC wallets           |
| Connectivity        | Dual-band Wi-Fi, Bluetooth, and Ethernet                            |
| Code scanning       | QR, barcode, and PCR code scanning                                  |
| Security            | PCI PTS 6.x / 7.x, encryption, P2PE readiness, and tamper detection |
| Payment application | EVPay on VIPA 7                                                     |
| Factory software    | EVPay is pre-installed. Site setup remains required.                |

### What is new

* **Android platform:** Android 13 provides a modern, secure terminal platform.
* **Payment support:** The terminal supports chip, contactless, swipe, fleet, debit PIN, PIN bypass, and digital wallets.
* **Refreshed payment screen:** Larger fonts and improved layouts simplify customer interaction.
* **Automatic updates:** VHQ and Commander can deliver approved EVPay updates.
* **QR and barcode scanning:** Customers can scan loyalty codes and digital coupons from their phone.
* **Customer engagement:** Configured splash screens, tipping prompts, loyalty, and promotions display on-screen.

### Refreshed payment screen

The payment flow remains unchanged: tap, insert, or swipe, enter a PIN when prompted, then confirm the amount.

| Change           | Previous experience                            | M425A experience                                         |
| ---------------- | ---------------------------------------------- | -------------------------------------------------------- |
| Buttons          | Full-width buttons could be hard to read.      | Natural-sized buttons support more precise taps.         |
| Fonts            | Small text was difficult to read.              | Larger, clearer text improves readability.               |
| Contactless area | Card placement could trigger accidental reads. | The contactless area is repositioned and clearly marked. |
| Scrolling        | Narrow scroll bars were hard to use.           | Wider controls and improved layouts reduce scrolling.    |
| Choices          | Fewer choices were visible.                    | More choices display at once.                            |

### Customer engagement features

| Feature                 | Site benefit                                                  |
| ----------------------- | ------------------------------------------------------------- |
| Custom splash screens   | Show site branding and promotions while the terminal is idle. |
| On-screen tipping       | Customers select a tip on the terminal.                       |
| Loyalty recognition     | Show points balances and targeted offers.                     |
| Online specials         | Promote offers at payment.                                    |
| QR and barcode scanning | Scan loyalty codes and digital coupons from a phone.          |
| Self-checkout           | Support customer self-service during busy periods.            |
| Alternative payments    | Accept configured wallet and alternative payment methods.     |
| Electronic signing      | Capture signatures on-screen when required.                   |

{% hint style="info" %}
Verifone deployment teams configure loyalty, tipping, splash screens, and scanning features.
{% endhint %}

### Payment types accepted

| Payment method  | Customer action                                           | Notes                                         |
| --------------- | --------------------------------------------------------- | --------------------------------------------- |
| Chip card       | Insert the card and follow prompts.                       | Supports major payment networks.              |
| Contactless     | Hold a card, phone, or watch near the contactless symbol. | Supports NFC cards and digital wallets.       |
| Magnetic stripe | Swipe through the card reader.                            | Used when chip reading is unavailable.        |
| Fleet card      | Insert or swipe and complete programme prompts.           | Commander controls fleet prompts.             |
| Debit with PIN  | Insert or swipe, then enter a PIN.                        | The physical keypad protects PIN entry.       |
| PIN bypass      | Process debit as a signature transaction.                 | Availability depends on network and setup.    |
| QR or barcode   | Show a loyalty code or coupon on the phone.               | Supports configured loyalty and coupon flows. |

### Key specifications

| Feature         | Specification                                             |
| --------------- | --------------------------------------------------------- |
| Processor       | Quad-core ARM Cortex-A53 64-bit CPU at 1.3 GHz            |
| Memory          | 2 GB LPDDR3 and 16 GB eMMC                                |
| Display         | 5.5-inch HD IPS LCD capacitive touchscreen                |
| Payment readers | MSR, smart card, contactless, NFC, and QR code            |
| Wireless        | Bluetooth 4.2 BLE and dual-band Wi-Fi                     |
| Camera          | 5 MP front QR and barcode scanner with autofocus          |
| Security        | PCI PTS 6.x, SRED, and AES DUKPT                          |
| SAM             | Three standard SAM cards                                  |
| Environment     | -10° to 50°C operating; 5% to 90% non-condensing humidity |

### Software updates

VHQ automatically delivers approved updates during a scheduled maintenance window. The terminal waits until it is idle, applies the update, restarts, and returns to the payment screen.

Commander can also show the installed EVPay version and trigger an approved on-demand update. Updates do not interrupt an active payment transaction.

### Quick reference

| Topic         | Summary                                                                     |
| ------------- | --------------------------------------------------------------------------- |
| Terminal      | Android payment terminal running EVPay on VIPA 7                            |
| Screen        | 5.5-inch colour touchscreen with tactile PIN keypad                         |
| Connectivity  | Dual-band Wi-Fi, Bluetooth, and Ethernet                                    |
| Payment types | Chip, contactless, swipe, fleet, debit PIN, PIN bypass, and digital wallets |
| Scanning      | Reads loyalty barcodes, coupons, and QR codes                               |
| Updates       | VHQ delivers automatic updates; Commander supports on-demand updates        |
| Security      | Tamper-evident hardware with no user-serviceable parts                      |
| Availability  | Base 057.01.00                                                              |


---

# 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/pin-pads/implementation-guides/m425a/device-overview.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.