Please follow the steps below to complete your installation of NETePay FDMS Rapid Connect Host EMV - RCH 5.06.12

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 NETePay FDMS Rapid Connect Host EMV - RCH 5.06.12

Release date: 07/12/2016

Support is added for an EMV PreAuth transaction and PreAuthCaptureByRecordNo (with token). These two new transactions have been added since Rapid Connect does not support an Adjust transaction to add a TIP after the initial authorization (Sale). Restaurant systems need to make an integration change to support the EMV PreAuth and subsequent PreAuthCaptureByRecordNo transaction. The PreAuth must be captured in order for the transaction to be settled. The PreAuthCaptureByRecordNo must be performed only once since it captures a transaction to the current batch. The TIP amount may be zero. If a mistake occurs with the amount captured, the integration must use a VoidSaleByRecordNo to remove the transaction from the batch. The dsiEMVUS Integration Spec has been revised to add these two new transactions. The document version is now V02.13.

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