IPC updates

Your Worldpay contact will inform you about new software versions, we advise you keep your estate up-to-date with the latest versions. Old firmware versions may prevent you from using new features in IPC.

When changing software versions it might be necessary to change the profile ID of each TID.

There are two ways of upgrading the software on the PED if your PED is already using IPC software.

  • The TIDs can be flagged to automatically download the latest version from the WP server

  • The mini installer can be run on each till.

If you need to upgrade from EVT then you will need to run a mini installer to upgrade to IPC111, then you will can use the automatic download facility or another mini installer to reach the latest version of IPC.

All upgrading activities must be discussed with and approved by the Total Support Team so that a technical resource can be assigned. Please contacttotal.support@worldpay.comto arrange your upgrading activities.

Warning: Scheme mandates must be applied to PEDs to avoid fines and chargebacks. You will be contacted by your partner manager, corporate support manager, or the technical service desk about mandated changes.

Critical patches

If critical patches needs to be made available to merchants, Worldpay will notify the affected merchants by email.

Critical vulnerabilities can be reported from various sources:

  • Kernel or firmware patches for the PEDs provided by the PED supplier through Worldpay

  • IPC patches provided by Worldpay

  • Java or Operating System patches announced industry wide with potential subsequent patches for IPC through Worldpay

Critical vulnerabilities are defined as follows:

Vulnerabilities may be considered critical if they pose an imminent threat to the environment, impact critical systems, or would result in a potential compromise if not addressed.

Changes to operating systems and Java

IPC depends on the operating systems and more importantly on Java. It is essential to the security of IPC to stay in touch with security vulnerabilities identified in either of those dependencies on an ongoing basis. Worldpay operates a vulnerability and patch management process to ensure IPC is tested against any security relevant change to the OS or Java. Should an OS or Java patch or upgrade impact the functionality of IPC Worldpay’s process will capture this, followed by the implementation of the necessary changes to the software and/or this guide. The relevant communications will be sent, including the updated guide and IPC patch if required, to the merchants with instructions on how to keep their cardholder data environment secure. It is important for the security of the merchant cardholder data environment to stay alert and react upon patches issued by Worldpay.

IPC upgrades and bug fixes

It is common practice to provide regular upgrades or bug fixes for IPC in the market and necessary notifications are sent by email to affected merchants.

With every version of IPC the updated integration guide will be packaged with other necessary files in the installer.

IPC software and PED firmware updates are provided from the WPH. The IPC manages the process of downloading and deploying its software upgrades, and the firmware upgrades for the connected PED.

Connections to enable Upgrade

The software and firmware upgrade components are downloaded from www.yes-pay.net/downloads through an https connection.

The https connection supports TLS 1.0, 1.1 and 1.2. Connection via SSL is not supported.

The SSL certificate that enables the https connection is based on the domain name yes-pay.net. For networks that do not support DNS, please create an entry in the host file of the IPC host machine to map the domain name www.yes-pay.net to its IP address. This will allow the IP address to be resolved to the domain name and allow the https handshake to succeed.

Hosts file entries

  1. Go to: Windows: C:\Windows\System32\Drivers\etc Linux: /etc/
  2. Open the hosts file and add this to the file: www.yes-pay.net

Note: On some Windows systems, similar changes might be needed in the lmhosts file If it is necessary to define entries in the hosts file be aware that these might need changing in future if the IP address of the WPH domains change. Worldpay will advise in advance of such IP address changes.

If using, or upgrading software to, IPC v2.1.9 and above, please be aware that urls for transaction data have changed to access domain name worldpay.com (see section 2.2.3). Hence, for networks that do not support DNS, the ip address for transaction urls would also need to be added into hosts/lmhosts, along with the entry for domain www.yes-pay.net - see the example hosts files entries below

Example hosts files entries: www.yes-pay.net total1.worldpay.com total2.worldpay.com

Software Upgrade

At the time of initialisation a check is made by IPC with the WPH for availability of software and firmware updates.

If an upgrade is available IPC will commence the upgrade process, IPC will prompt for acceptance of the upgrade. This can be changed by setting the Auto Upgrade flag in IPC configuration, Software Upgrade (seeSoftware Upgrade).

If a problem occurs during the installation of the software upgrade IPC an error message will show.

Firmware Upgrade

At the time of initialisation a check is made by IPC with the WPH for availability of software and firmware updates.

The firmware upgrade functionality is supported with iPP350 and Vx820-7816 PED. If any other PED device is configured IPC will display an error message

If an upgrade is available IPC will commence the upgrade process, IPC will prompt you to accept the upgrade. You can change this by setting the Auto Upgrade flag in IPC configuration, Software Upgrade (seeSoftware Upgrade).

If a problem occurs during the installation of the firmware upgrade IPC an error message will show.

If the Firmware Upgrade process should fail, which could happen due to communication failure between IPC client and PED, then IPC displays the prompt below and retries 3 times to download firmware files into PED.

If after 3 attempts the firmware upgrade has not been successful, IPC displays an error and exits from the upgrade process.

Firmware Upgrade process for Vx820-7816

There are five components to upgrade pin-pad software of Vx820-7816 which are:- EOS - > OS -> CTLS -> VIPA->Whitelist.

The Vx820-7816 firmware upgrade process is the same as inConnections To Enable Upgrade.

If the firmware upgrade process fails at any component due to fail in command API process into PED then IPC retry once again that running component.

Rollback of firmware Upgrade: Ingenico PEDs has the capability to rollback automatically to original firmware version but the Vx820-7816 PED does not support automatic rollback of firmware upgrade.

Rollback is implemented by re-installing the original firmware version. A copy of the original (base) firmware version is provided within the firmware upgrade folders for this purpose.