EVPAY 2.08.01 R01
Versions and Information
Verifone Engage ViperPAY (EVPAY)
2.08.01 Revision 1 (703 only)
Release Level
Production
PIN pads
Verifone P400 and M400
Minimum EVPAY Software
2.03.03 R04 Note: The PIN pad must be at a minimum 2.03.03 R04 to upgrade to 2.08.01 r01.
Minimum OS Version
VOS2 release 31610800
Payment Kernel
6.9.1.17-6
Target OS
31615600
Target ADK
4.8.42.1-1986
Target VHQ
5.0.5.2
Reference Set
Verifone P400 Implementation Guide Verifone M400 Implementation Guide
Additional Release Notes
Release Date
September 15, 2026
Publication Date
September 15, 2026
Important Information
EVPAY 2.06.00 and Higher
Kernel 7.0.3 is only used with EVPAY 2.06.00 and Higher software.
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 Docs.Verifone.com > Commander Central.
Debit Keys
When ordering a Debit Key on the Premier Portal, select “Engage” for the M400 and P400 PIN pads.”
Installation Information
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.
Installing VHQ Configuration After the EVPAY 2.08.01 Full Installation
This needs to be done only by customers who wish to connect to VHQ petrohome or customer instance.
Follow the full installation steps
Follow the EVPAY 2.08.01 Full Installation steps in the next section.
Follow SAM agreement prompts
The PIN pad prompts for Service and Maintenance (SAM) agreement. Follow the prompts.
Install customer configuration file
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.
Obtain 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.
Verifone VHQ Upgrade Installation Instructions for Version 2.08.01
Not Communicating to Verifone VHQ
If the customer's PIN pads are not communicating to VHQ, but wish to upgrade to 2.08.01, 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 own 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.08.01, 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
This is Kernel 7.03 version.
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.
Use these steps in order to do a full installation of the Verifone EVPAY and components on Verifone P400 PINpad.
Download and extract the package
Download the zipped package for the kernels 7.03 and extract it.
EVPAY-2.08.01-r01-Kernel-703-Engage-FullInstall-Petrohome-Prod.zip
Load the OS VOS2 release
Load the OS VOS2 release 1.dl.vos2-prod-Engage-release-31615600.tgz file. If the PIN pad prompts to reboot, select “Yes.”
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.
Load the Adkcert Package
Load the Adkcert Package 2.dl.adkcrt-201527.tgz file. If the PIN pad prompts to reboot, select “Yes.”
Load the Payment Kernel
Load the Payment Kernel version 3.PETRO_VIPA_6.9.1.17-6_engage-prodsigned.tgz for Verifone P400. If the PIN pad prompts to Reboot, select “Yes.”
Load the P400 application
Load 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.03 Kernel 4.Engage_Evpay-2.08.01-r01-Kernel-703-prodsigned.tgz file. If the PIN pad prompts to Reboot, select “Yes.”
Accept the SAM Agreement
Accept the SAM Agreement if the PIN pads need to be connected to VHQ Petrohome.
Load the VHQ configuration
Load the 5.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.03 Full Installation” above.
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.
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.
Verifone P400 Upgrade Installation
Use these steps in order to do an upgrade of the Verifone EVPAY and components on Verifone P400 PINpad.
Download and extract the package
Download the following zipped package for the kernels 7.03 and extract it.
EVPAY_2.08.01-r01-Kernel-703-Engage-Upgrade-Prod.zip
Load the Payment Kernel
Load the Payment Kernel version 1.PETRO_VIPA_6.9.1.17-6_engage_Upgrade-prodsigned.tgz for Verifone P400. If the PIN pad prompts to Reboot, select “Yes.”
Load the P400 application
Load 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.03 Kernel 2.Engage_Evpay-2.08.01-r01-Kernel-703_Upgrade-prodsigned.tgz file. If the PIN pad prompts to Reboot, select “Yes.”
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.
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.
Verifone M400 Full Installation
This is Kernel 7.03 version.
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.
Use these steps in order to do a full installation of the Verifone EVPAY and components on Verifone M400 PINpad.
Download and extract the package
Download the following zipped package for the kernel 7.03 and extract it.
EVPAY-2.08.01-r01-Kernel-703-Engage-FullInstall-Petrohome-Prod.zip
Load the OS VOS2 release
Load the OS VOS2 release 1.dl.vos2-prod-Engage-release-31614800-A600.tgz file. If the PIN pad prompts to reboot, select “Yes.”
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.
Load the Adkcert Package
Load the Adkcert Package 2.dl.adkcrt-201527.tgz file. If the PIN pad prompts to reboot, select “Yes.”
Load the Payment Kernel
Load the Payment Kernel version 3.PETRO_VIPA_6.9.1.17-6_engage-prodsigned.tgz for Verifone M400. If the PIN pad prompts to Reboot, select “Yes.”
Load the M400 application
Load 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.03 Kernel 4.Engage_Evpay-2.08.01-r01-Kernel-703-prodsigned.tgz file. If the PIN pad prompts to Reboot, select “Yes.”
Accept the SAM Agreement
Accept the SAM Agreement if the PIN pads need to be connected to VHQ Petrohome.
Load the VHQ configuration
Load the 5.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.03 Full Installation” above.
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.
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.
Verifone M400 Upgrade Installation
This is Kernel 7.03 version.
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.
Use these steps in order to do an upgrade of the Verifone EVPAY and components on Verifone M400 PINpad.
Download and extract the package
Download the following zipped package for the kernel 7.03 and extract it.
EVPAY_2.08.01-r01-Kernel-703-Engage-Upgrade-Prod.zip
Load the Payment Kernel
Load the Payment Kernel version 1.PETRO_VIPA_6.9.1.17-6_engage_Upgrade-prodsigned.tgz for Verifone M400. If the PIN pad prompts to Reboot, select “Yes.”
Load the M400 application
Load 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.03 Kernel 2.Engage_Evpay-2.08.01-r01-Kernel-703_Upgrade-prodsigned.tgz file. If the PIN pad prompts to Reboot, select “Yes.”
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.
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.
What’s New In This Release: 2.08.01 Revision 1
Enhancements
VIPA and ADK
This release integrates VIPA 6.9.1.17-6 and ADK 4.8.42 into EVPAY 2.08.01. It also includes the underlying platform improvements.
In any case, change the EVPAY version to 2.08.01.
Platform Enhancements
Verifone has made continuous security enhancements across the platform, spanning application and package integrity, cryptography and key protection, authentication and access controls, deprecation of legacy components, and ongoing platform hardening. Each release builds incrementally on the last, making the current version the most secure and fully enhanced release available today. Verifone strongly recommends that all partners and customers running a supported device upgrade to this version, regardless of which version they are currently on.
Staying current is the most direct way to bring deployed devices up to the platform's latest security baseline as threats continue to evolve. Here are the Platform Release Notes.
Last updated