> 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/release-notes/evpay-release-notes/evpay-2.04.04-r01.md).
# EVPAY 2.04.04 R01
## Versions and Information
| Verifone Engage ViperPAY (EVPAY) | 2.04.04 Revision 1 |
| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Release Level** | Production |
| **PIN pads** | Verifone P400 and M400 |
| **Minimum EVPAY Software** |
2.03.03 R4 Note: The PIN pad must be at a minimum 2.03.03 R4 to upgrade to 2.04.04 R01.
|
| **Release Date** | February 19, 2026 |
| **Publication Date** | February 19, 2026 |
## Important Information
### Commander Central Documentation
Commander Central documentation can be found at Verifone Premier Portal > Manage > Petro Downloads > Verifone C-Site Management > Documentation area.
Also, can be found at [Commander Central](https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-central).
### Debit Keys
When ordering a Debit Key on the Premier Portal, select “Engage” for the M400 and P400 PIN pads.”
### FEP and Kernel Versions
Use these kernel versions to decide which one to use when loading the software.
| FEP | Kernel Version |
| --------------------------------- | -------------- |
| **Buypass** | 7.02r |
| **Chase** | 7.03r |
| **Chevron** | 7.03r |
| **HPS NWS** | 7.02r |
| **HPS VAPS (CITGO and Marathon)** | 7.02r |
| **NBS** | 7.03r |
| **Phillips 66** | 7.02r |
| **Shell** | 7.02r |
| **WorldPay** | 7.03r |
## Installation Information
{% hint style="warning" %}
Installing a current operating system over OS version 31610800 or lower without an intermediate step-up version may cause the device to fail, requiring it to be sent in for repair. See VASC Field Service Bulletin 0322\_002 posted at the Premier Portal under Manage > Petro Downloads > General VASC Info > VASC Bulletins for more details.
If the prompt below “Start install?” is displayed, press “OK”. Do NOT press Add.
{% endhint %}
{% hint style="info" %}
If the screen below “Searching for upgrades” displays, press 1,5,9 and continue with the installation.
{% endhint %}
### Installing VHQ configuration after the EVPAY 2.04.04 Full Installation
This needs to be done only by customers who wish to connect to VHQ petrohome or customer instance.
{% stepper %}
{% step %}
### Complete the full installation
Follow the EVPAY 2.04.04 Full Installation steps in the next section.
{% endstep %}
{% step %}
### Accept the SAM agreement
The PIN pad prompts for Service and Maintenance (SAM) agreement. Follow the prompts.
{% endstep %}
{% step %}
### Install the customer configuration file, if applicable
If the customer has their own instance (account) and is requesting to have a configuration file loaded during the full installation, install it at the end after the Verifone EVPAY package.
{% endstep %}
{% step %}
### Obtain the default VHQ configuration
Verifone engineering will give the default VHQ configuration (Petrohome) to the Sales Engineer (SE) and they will handle it by editing the contents, production signing and delivering it to the customer.
{% endstep %}
{% endstepper %}
### Verifone VHQ Upgrade Installation Instructions for Version 2.04.04
#### Not Communicating to Verifone VHQ
* If the customer's PIN pads are not communicating to VHQ, but wish to upgrade to 2.04.04, follow the installation steps via USB upgrade.
* If customer wants to go to VHQ on the PIN pad and communicate to Petrohome, guide them to change the setting so that VHQ SAM can be prompted.
* If the customer wants to go to VHQ on the PIN pad and talk to their ow instance (account), install the VHQ configuration file on the PIN pad with the customer's instance.
#### Communicating with Verifone VHQ
* If the customer's PIN pads are communicating to VHQ, but want to upgrade to 2.04.04, it can be performed through VHQ or USB. With the VHQ configuration file, whether it is Petrohome Configuration file or customer’s own instance (account) configuration file, load the VHQ Configuration file after the installation steps below.
### Verifone P400 Full Installation
{% hint style="warning" %}
The package can only be upgraded on M400/P400 PIN pad running EVPAY 2.03.03 R04. Make sure to unzip the files downloaded from the Verifone Premier Portal to obtain the `.TGZ` file.
{% endhint %}
Use these steps in order to do a full installation of the Verifone EVPAY and components on Verifone P400 PINpad.
{% stepper %}
{% step %}
### Download and extract the package
Download one of the following zipped packages for the kernels, **7.02** or **7.03**, that is being used and extract it.
* **EVPAY-2.04.04-r01-Kernel-702-Engage-FullInstall-Petrohome-Prod.zip**
* **EVPAY-2.04.04-r01-Kernel-703-Engage-FullInstall-Petrohome-Prod.zip**
{% endstep %}
{% step %}
### Load the OS VOS2 release
Load the OS VOS2 release **dl.vos2-prod-Engage-release-31612300.tgz** file. If the PIN pad prompts to reboot, select “Yes.”
{% hint style="warning" %}
Installing a current operating system over OS version 30620500 or lower without an intermediate step-up version may cause the device to fail, requiring it to be sent in for repair. See VASC Field Service Bulletin 0322\_002 posted at the Premier Portal under Manage > Petro Downloads > General VASC Info > VASC Bulletins for more details.
{% endhint %}
{% endstep %}
{% step %}
### Load the Adkcert Package
Load the Adkcert Package **dl.adkcrt-201527.tgz** file. If the PIN pad prompts to reboot, select “Yes.”
{% endstep %}
{% step %}
### Load the Payment Kernel
Load the Payment Kernel version **PETRO\_VIPA\_6.9.0.7\_engage-17832.tgz** for Verifone P400. If the PIN pad prompts to Reboot, select “Yes.”
{% endstep %}
{% step %}
### Load the application
Load one of the following Verifone P400 files for the application. If the PIN pad prompts to “Run Apps”, press Cancel and then press the Red X button until you return to the Information menu. At the Information Menu, select Exit and then at the prompt, reboot the PIN pad.
* Load the Verifone P400 application for **7.02** Kernel **Engage\_Evpay-2.04.04-r01-Kernel-702-ProdSigned.tgz** file. If the PIN pad prompts to Reboot, select “Yes.”
* Load the Verifone P400 application for **7.03** Kernel **Engage\_Evpay-2.04.04-r01-Kernel-703-ProdSigned.tgz** file. If the PIN pad prompts to Reboot, select “Yes.”
{% endstep %}
{% step %}
### Accept the SAM Agreement
Accept the SAM Agreement if the PIN pads need to be connected to VHQ Petrohome.
{% endstep %}
{% step %}
### Load the VHQ configuration
Load the **Vhqconfig\_3.2.7\_Engage\_petrohome-12561.tgz** or the customer specific VHQ Configuration file to connect to the specific VHQ instance. Also, see the section “Installing VHQ configuration after the EVPAY 2.04.04 Full Installation” above.
{% endstep %}
{% step %}
### Configure the PIN pad on EPS
To configure PIN pad on EPS, make sure the POP IP address is the same as Verifone P400 IP address in Configuration Client > Payment Controller > EPS Configuration > EPS Global Configuration > POP tab.
{% endstep %}
{% step %}
### Initialize EMV configuration
To initialize EMV configuration from EPS to Verifone EVPAY, navigate to Configuration Client > Payment Controller > EPS Configuration > EPS Global Configuration > EMV Initialization.
{% endstep %}
{% endstepper %}
#### Verifone P400 Upgrade Installation
Use these steps in order to do an upgrade of the Verifone EVPAY and components on Verifone P400 PINpad.
{% stepper %}
{% step %}
### Download and extract the package
Download one of the following zipped packages for the kernels, **7.02** or **7.03**, that is being used and extract it.
* **EVPAY\_2.04.04-r01-Kernel-702-Engage-Upgrade-Prod.zip**
* **EVPAY\_2.04.04-r01-Kernel-703-Engage-Upgrade-Prod.zip**
{% endstep %}
{% step %}
### Load the Payment Kernel
Load the Payment Kernel version **PETRO\_VIPA\_6.9.0.7\_Engage\_upgrade-17832-ProdSigned.tgz** for Verifone P400. If the PIN pad prompts to Reboot, select “Yes.”
{% endstep %}
{% step %}
### Load the application
Load one of the following Verifone P400 files for the application. If the PIN pad prompts to “Run Apps”, press Cancel and then press the Red X button until you return to the Information menu. At the Information Menu, select Exit and then at the prompt, reboot the PIN pad.
* Load the Verifone P400 application for **7.02** Kernel **Engage\_Evpay-2.04.04-r01-Kernel-702\_Upgrade-ProdSigned.tgz** file. If the PIN pad prompts to Reboot, select “Yes.”
* Load the Verifone P400 application for **7.03** Kernel **Engage\_Evpay-2.04.04-r01-Kernel-703\_Upgrade-ProdSigned.tgz** file. If the PIN pad prompts to Reboot, select “Yes.”
{% endstep %}
{% step %}
### Configure the PIN pad on EPS
To configure PIN pad on EPS, make sure the POP IP address is the same as Verifone P400 IP address in Configuration Client > Payment Controller > EPS Configuration > EPS Global Configuration > POP tab.
{% endstep %}
{% step %}
### Initialize EMV configuration
To initialize EMV configuration from EPS to Verifone EVPAY, navigate to Configuration Client > Payment Controller > EPS Configuration > EPS Global Configuration > EMV Initialization.
{% endstep %}
{% endstepper %}
### Verifone M400 Full Installation
{% hint style="warning" %}
The package can only be upgraded on M400/P400 PIN pad running EVPAY 2.03.03 R04. Make sure to unzip the files downloaded from the Verifone Premier Portal to obtain the `.TGZ` file.
{% endhint %}
Use these steps in order to do a full installation of the Verifone EVPAY and components on Verifone M400 PINpad.
{% stepper %}
{% step %}
### Download and extract the package
Download one of the following zipped packages for the kernels, **7.02** or **7.03**, that is being used and extract it.
* **EVPAY-2.04.04-r01-Kernel-702-Engage-FullInstall-Petrohome-Prod.zip**
* **EVPAY-2.04.04-r01-Kernel-703-Engage-FullInstall-Petrohome-Prod.zip**
{% endstep %}
{% step %}
### Load the OS VOS2 release
Load the OS VOS2 release **dl.vos2-prod-Engage-release-31612300.tgz** file. If the PIN pad prompts to reboot, select “Yes.”
{% hint style="warning" %}
Installing a current operating system over OS version 30620500 or lower without an intermediate step-up version may cause the device to fail, requiring it to be sent in for repair. See VASC Field Service Bulletin 0322\_002 posted at the Premier Portal under Manage > Petro Downloads > General VASC Info > VASC Bulletins for more details.
{% endhint %}
{% endstep %}
{% step %}
### Load the Adkcert Package
Load the Adkcert Package **dl.adkcrt-201527.tgz** file. If the PIN pad prompts to reboot, select “Yes.”
{% endstep %}
{% step %}
### Load the Payment Kernel
Load the Payment Kernel version **PETRO\_VIPA\_6.9.0.7\_engage-17832.tgz** for Verifone M400. If the PIN pad prompts to Reboot, select “Yes.”
{% endstep %}
{% step %}
### Load the application
Load one of the following Verifone M400 files for the application. If the PIN pad prompts to “Run Apps”, press Cancel and then press the Red X button until you return to the Information menu. At the Information Menu, select Exit and then at the prompt, reboot the PIN pad.
* Load the Verifone M400 application for **7.02** Kernel **Engage\_Evpay-2.04.04-r01-Kernel-702-ProdSigned.tgz** file. If the PIN pad prompts to Reboot, select “Yes.”
* Load the Verifone M400 application for **7.03** Kernel **Engage\_Evpay-2.04.04-r01-Kernel-703-ProdSigned.tgz** file. If the PIN pad prompts to Reboot, select “Yes.”
{% endstep %}
{% step %}
### Accept the SAM Agreement
Accept the SAM Agreement if the PIN pads need to be connected to VHQ Petrohome.
{% endstep %}
{% step %}
### Load the VHQ configuration
Load the **Vhqconfig\_3.2.7\_Engage\_petrohome-12561.tgz** or the customer specific VHQ Configuration file to connect to the specific VHQ instance. Also, see the section “Installing VHQ configuration after the EVPAY 2.04.04 Full Installation” above.
{% endstep %}
{% step %}
### Configure the PIN pad on EPS
To configure PIN pad on EPS, make sure the POP IP address is the same as Verifone M400 IP address in Configuration Client > Payment Controller > EPS Configuration > EPS Global Configuration > POP tab.
{% endstep %}
{% step %}
### Initialize EMV configuration
To initialize EMV configuration from EPS to Verifone EVPAY, navigate to Configuration Client > Payment Controller > EPS Configuration > EPS Global Configuration > EMV Initialization.
{% endstep %}
{% endstepper %}
### Verifone M400 Upgrade Installation
{% hint style="warning" %}
The package can only be upgraded on M400/P400 PIN pad running EVPAY 2.03.03 R04. Make sure to unzip the files downloaded from the Verifone Premier Portal to obtain the `.TGZ` file.
{% endhint %}
Use these steps in order to do an upgrade of the Verifone EVPAY and components on Verifone M400 PINpad.
{% stepper %}
{% step %}
### Download and extract the package
Download one of the following zipped packages for the kernels, **7.02** or **7.03**, that is being used and extract it.
* **EVPAY\_2.04.04-r01-Kernel-702-Engage-Upgrade-Prod.zip**
* **EVPAY\_2.04.04-r01-Kernel-703-Engage-Upgrade-Prod.zip**
{% endstep %}
{% step %}
### Load the Payment Kernel
Load the Payment Kernel version **PETRO\_VIPA\_6.9.0.7\_Engage\_upgrade-17832-ProdSigned.tgz** for Verifone M400. If the PIN pad prompts to Reboot, select “Yes.”
{% endstep %}
{% step %}
### Load the application
Load one of the following Verifone M400 files for the application. If the PIN pad prompts to “Run Apps”, press Cancel and then press the Red X button until you return to the Information menu. At the Information Menu, select Exit and then at the prompt, reboot the PIN pad.
* Load the Verifone M400 application for **7.02** Kernel **Engage\_Evpay-2.04.04-r01-Kernel-702\_Upgrade-ProdSigned.tgz** file. If the PIN pad prompts to Reboot, select “Yes.”
* Load the Verifone M400 application for **7.03** Kernel **Engage\_Evpay-2.04.04-r01-Kernel-703\_Upgrade-ProdSigned.tgz** file. If the PIN pad prompts to Reboot, select “Yes.”
{% endstep %}
{% step %}
### Configure the PIN pad on EPS
To configure PIN pad on EPS, make sure the POP IP address is the same as Verifone M400 IP address in Configuration Client > Payment Controller > EPS Configuration > EPS Global Configuration > POP tab.
{% endstep %}
{% step %}
### Initialize EMV configuration
To initialize EMV configuration from EPS to Verifone EVPAY, navigate to Configuration Client > Payment Controller > EPS Configuration > EPS Global Configuration > EMV Initialization.
{% endstep %}
{% endstepper %}
## What’s New In This Release: 2.04.04 Revision 1
{% hint style="warning" %}
The PIN pad must be at a minimum 2.03.03 R4 to upgrade to 2.04.04 R01.
The package can only be upgraded on M400/P400 PIN pad running EVPAY 2.03.03 R04.
{% endhint %}
Enhancement
#### System
**Tipping**
The Verifone Commander now provides flexible tipping options for sites that sell prepared items. The tipping prompt will be displayed on the PIN pad. Preset amounts or percentages for customer selection will be configured in Verifone Configuration Client or Verifone C-Site Management. The “Prompt for Tip” will be enabled in the department and will apply to all PLUs within that department. Customers will have the option to enter a custom amount. The prompt is customizable.
## What’s New In This Release: 2.04.03 Revision 1
{% hint style="warning" %}
The PIN pad must be at a minimum 2.03.03 R4 to upgrade to 2.04.03 R01. This is Kernel 7.03 version.
The package can only be upgraded on M400/P400 PIN pad running EVPAY 2.03.03 R04.
{% endhint %}
### Enhancement
Card support has been added to the Chevron brand for EMV WEX Fleet 4.1, EMV Visa Fleet 2.0, additional prompts, and host-based product restrictions.
## What’s New In This Release: 2.04.02 Revision 1
Enhancements
### System
1. Contactless symbol on the screen that displays to the user has been moved closer to the antenna or landing area where the signal is the strongest. It also has been increased in size.
2. Space has been added between the Contactless symbol and Loyalty ID to eliminate an incorrect selection.
Resolution
### System
When line items were enabled, items and fees/amounts disappeared every few transactions. This was corrected.
## What’s New In This Release: 2.04.01 Revision 2
{% hint style="danger" %}
This software version can be installed on an old P400, P/N M435-003-04-WWA-4. The new P400, P/N M435-303-14-NAA-5 MUST have full installation of 2.04.01 R02. The older software CANNOT be installed on the new P400 P/N M435-303-14-NAA-5. If older software is used, the P400 will be unrecoverable and will need to be replaced.
{% endhint %}
Enhancements
### System
* The new P400, P/N M435-303-14-NAA-5, is now supported with this version only.
* EMV Fleet cards are now supported.
* The End-to-End Encryption (E2EE) solution is now supported.
### Resolutions
### System
The following issues were corrected:
* The 9F5B tag was not being returned for contactless transactions.
* M400 was stuck at “Waiting for cashier” prompt when APM was enabled and Loyalty Alt ID was disabled.
* The enter button was enabled when the Get Any Key or Card Device request was sent without loyalty softkeys.
* The PIN pads were constantly locking up.
---
# 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://docs.verifone.com/petroleum-docs/petro-and-c-store/pin-pads/release-notes/evpay-release-notes/evpay-2.04.04-r01.md?ask=&goal=
```
`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.