Please follow the steps below to complete your installation of NETePay Worldpay IP (Mercury) US EMV + Debit - MPH 5.07.33

Step 1 - Install Client Control

In order to communicate with this NETePay your POS may use one of the following ActiveX controls depending on the integration method chosen by the POS developer. If you are unsure of which to install please contact POS technical support.

dsiEMVUS® 1.53

Release date: 03/22/2021

Datacap’s out-of-scope ActiveX control for NETePay supporting a variety of EMV-enabled hardware options.

For information on supported devices please see our PC based POS solutions page.

Release notes for v1.53

  • Support is added for the following IDTech devices via USB/HID. The VID/PID values are the same between VP3300 and VP8300 devices.
    • VP3300 for TSYS
    • VP8300 for TSYS
    • VP3300 for EVO with TDES DUKPT PAN encryption
    • VP8300 for EVO with TDES DUKPT PAN encryption
    • VP8300 for Mercury with TDES DUKPT PAN encryption
    • VP8300 for Datacap Hosted with TDES DUKPT PAN encryption
    • VP8300 for Monetary with TDES DUKPT PAN encryption
  • For IDTech devices with PAN encryption, the masked card data is now masked with zeroes rather than asterisks or any other character. This change allows IDTech transactions to be stored using Store and Forward.
  • Support is added for Tetra LANE devices for Global Payments.
  • When Calling "ProcessEasyCheckout", if "<MsgPump>Allow</MsgPump>") is included in the XML request:
    • The ocx will create a new thread to process the connection to EZCheckout and mainatain the windows message pump on the calling thread.
    • Depending on the software design this may be needed.
      • A single threaded integrator (since by definition the ocx is in the GUI thread) will not be able to process windows messages, therefore the new function of sending a windows message reporting progress will never be delivered to the caller.
      • A multithreaded integrator who uses the OCX in a separate thread only blocks that thread and he is fine AS LONG AS he follows the rules and never calls across the thread boundary to the OCX(this could lock the entire POS).
      • A multithreaded integrator who uses the OCX in the GUI thread can process his background stuff in the other threads. Windows messages will still be blocked in the calling thread, but he can steer messages to any thread with a (window and) message pump, so he can use this as he sees fit. This can lead to a nicer GUI experience for the cashier depending on how much control the integrator wants to give the human being.
Microsoft Windows 10 Pro / 8 Pro / 7 Pro / Vista Pro / XP Pro

OR

dsiPDCX® 1.73

Release date: 03/22/2021

Datacap’s out-of-scope ActiveX control for NETePay and GIFTePay software that supports dozens of plug and play hardware options, including PIN Pads, Mag stripe readers, all-in-one touch terminals and contactless readers.

Release notes for v1.73

  • Support is added for the following IDTech devices via USB/HID. The VID/PID values are the same between VP3300 and VP8300 devices.
    • VP3300 with clear card data
    • VP8300 with clear card data
    • VP3300 for EVO with TDES DUKPT PAN encryption
    • VP8300 for EVO with TDES DUKPT PAN encryption
    • VP8300 for Mercury with TDES DUKPT PAN encryption
    • VP8300 for Datacap Hosted with TDES DUKPT PAN encryption
    • VP8300 for Monetary with TDES DUKPT PAN encryption
  • For IDTech devices with PAN encryption, the masked card data is now masked with zeroes rather than asterisks or any other character. This change allows IDTech transactions to be stored using Store and Forward.
Microsoft Windows 10 Pro / 8 Pro / 7 Pro / Vista Pro / XP Pro

OR

DSIClientX® 3.86

Release date: 09/01/2011

Datacap’s long-standing in-scope ActiveX control for NETePay and GIFTePay software.

Microsoft Windows 10 Pro / 8 Pro / 7 Pro / Vista Pro / XP Pro
Step 2 - Install Administrative tools (optional)
Local Batch Report Viewer

Release date: 05/11/2020

Local Batch Report Viewer can be used to view the locally stored batch report of Host based NETePay who support support this feature and have it enabled via PSCS.

Release notes for v1.03

  • Fix for an issue which prevented errors from the open batch being shown in the decline/error tab.
Microsoft Windows 10 Pro / 8 Pro / 7 Pro / Vista Pro / XP Pro
Step 3 - Install NETePay Worldpay IP (Mercury) US EMV + Debit - MPH 5.07.33

This NETePay is available via the NETePay 5 Director which provides a simplified installation process and go-forward automatic software updates. NETePay 5 Director is recommended but if needed the classic installation process is still available by clicking Download as usual.

To learn more about the NETePay 5 Director click here.

Release date: 08/23/2019

  • For the "EMV Support" parameter, the choice now includes "Debit Only".
  • EMV Support is added for China Union Pay.
  • An EMV card brand certification was completed for Ingenico Tetra devices. These include the Lane/3000, 5000, 7000 and 8000. It also includes the Move/3500, Move/5000 and Link/2500. The latest client controls (dsiPDCX and dsiEMVUS) support these devices with TDES PAN encryption for Worldpay.
  • An EMV card brand certification was completed for the Ingenico Telium iUC285.
  • Support is added for a "VAS Gift – Apple Pass Type ID" which is used with the Verifone P400.
  • Support is added for BatchReportQuery and BatchReportTransaction TranCodes.

New build released 9/17/19 - Updated to SAF library 6.0. This fixes a critical stop error which can occur while forwarding without IP connectivity.

New build released 10/23/19 - Update to SAF library 7.0. This fixes a critical stop error which can occur where a forward contains a voided transaction with more than 1 child. This also corrects an issue where transactions may go online even though ForceOffline is set to "Y".

New build released 11/4/19 - Update to SAF library 8.0. This fixes an issue where Authorize amounts over 999.99 may be formatted with commas.

New build released 1/17/20 - Local Batch Report library updated to v2.11. This corrects an issue where SAF transactions can fail after BatchReportTransaction is called.

Microsoft Windows 10 Pro / 8 Pro / 7 Pro (Windows XP and Vista do not support TLS 1.2 which is now an industry requirement)