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

# Software Installation

Prepare a factory-installed M425A terminal for a site.

## Software Installation

{% hint style="info" %}
**Sponsor Certificate Requirement**

A **sponsor certificate** is a digital certificate issued by the payment sponsor.

It identifies and authorizes a terminal within that sponsor’s payment network. The certificate helps the terminal establish a trusted connection to payment services.

For the M425A, it is part of terminal provisioning. It is typically loaded during installation or replacement. Verifone or the payment sponsor manages it.

It is **not** a merchant sponsorship document or a PCI compliance certificate.

 All M425A terminals leaving Verifone require the current Sponsor Certificate. Technicians must remove any existing Sponsor Certificate before installing the new package. Use the internal certificate procedure and the approved certificate package.
{% endhint %}

EVPay arrives pre-installed on the M425A. A setup visit is still required before the terminal can process payments.

A Verifone technician or designated setup contact completes the following steps.

{% stepper %}
{% step %}

### Confirm the operating system

Confirm the Android version is approved for the production site. Apply any required OS update.
{% endstep %}

{% step %}

### Configure the network

Configure the IP address, gateway, and DNS. Connect the terminal to Commander through Wi-Fi or Ethernet.
{% endstep %}

{% step %}

### Load the identity certificate

Install the terminal identity certificate (sponsor certificate). This certificate identifies the terminal to Verifone services.
{% endstep %}

{% step %}

### Load encryption keys

Load debit PIN encryption keys securely using TR-34. Keys are unique to each terminal.
{% endstep %}

{% step %}

### Configure VHQ

Point the terminal to its correct VHQ instance. Petroleum terminals normally use PetroHome VHQ.
{% endstep %}

{% step %}

### Apply Commander configuration

Apply payment settings, prompts, and fleet parameters through Commander Configuration Client.
{% endstep %}

{% step %}

### Complete test transactions

Test chip, contactless, magnetic-stripe, and debit PIN transactions before going live.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Replacement terminals require the full setup process. They do not inherit certificates, keys, or settings from the replaced terminal.
{% endhint %}

### Software updates

M425A terminals receive approved EVPay and configuration updates through VHQ. Updates normally run during scheduled maintenance windows.

* The terminal waits until no transaction is active.
* It restarts automatically after the update.
* Commander can also trigger an approved on-demand update.

Do not disconnect power while an update is running.


---

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