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

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.34

Release date: 07/16/2019

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.34

Support is added for the IDTech MiniSmart II device and SecureHead MSR for TSYS. The IDTech device does not encrypt the card data for TSYS. The IDTech MiniSmart firmware required is at least V2.00.020. Both devices must be accessible on a system to use either one.

Microsoft Windows 10 Pro / 8 Pro / 7 Pro / Vista Pro / XP Pro

OR

dsiPDCX® 1.61

Release date: 07/16/2019

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.61

  • Support is added for Ingenico Tetra devices for Heartland using Voltage PAN encryption.
  • For Ingenico, if Contactless EMV enabled, do not include MSD tap on get stripe command. If Contactless EMV not enabled, include MSD tap on get stripe command.
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 - RRH 5.06.12 Rental

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)