Please follow the steps below to complete your installation of NETePay 5 Director

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

AND / OR

ePay Administrator 5.00 (Terminal capture only)

Release date: 05/31/2018

ePay admin is used for local reporting and batch close functions where not available via the POS. It is only compatible with versions of NETePay that require a local database. Auto-batching is now available for Terminal-Based payment processors..... Please contact Datacap Systems technical support for more details.

Microsoft Windows 10 Pro / 8 Pro / 7 Pro / Vista Pro / XP Pro
Step 3 - Install NETePay 5 Director

Release date: 08/14/2020

This version of NETePay is equipped with an installer that allows for a simplified installation process and go-forward automatic software updates. In lieu of a processor-specific NETePay, download the NETePay 5 Director to get started.

To learn more about the NETePay 5 Director click here.

  • New build released 02/19/18
    • When applications are configured and running, the context menu now includes a new selection – Load Parameters (Stop/Start Director). The user can click one menu item to restart which will cause ePays to restart and reload parameters.
    • When a NETePay or GIFTePay window is opened, there are now four icons in the upper right corner that have the following functions.
      • View Merchant Parameters
      • PSCS
      • Email log
      • View log

New build released 02/27/18 - Change made to properly close the connection between manager and director if an ePay window is being shown while manager is used to "Load Parameters [Start/Stop Director]" or "Stop Director".

New build released 08/28/18 - Changes to facilitate future release of terminal capture NETePays via NETePay Director.

New build released 08/27/19 - Fixed an issue where failure to start director on 64 bit machine results in increased memory usage.

New build released 08/14/20 - New to this version is a Menu item – Software Deactivation. This feature will allow a user to deactivate the Director so that a new serial number can be obtained and a new Deployment ID can be entered.

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