Please follow the steps below to complete your installation of NETePay FDMS Rapid Connect Host EMV - RRH 5.07.31 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.72

Release date: 08/17/2023

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 Compatible devices page.

Release notes for v1.72

  • Support for <DraftLocator>Disallow</DraftLocator> is added. This along with a new version of Worldpay Core (Vantiv) NETePay will disable the Draft Locator.
  • The IDTech VP3300 for TSYS is a clear device, no PAN encryption. For a VP3300 without encryption, a change is included to allow magstripe data to be read and parsed.
Microsoft Windows 11 Pro / 10 Pro / Server 2019 / Server 2016

OR

dsiPDCX® 1.89

Release date: 06/21/2023

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

  • Support is added for the Ingenico Lane/3600 device for Datacap Hosted.
  • Support is added for PAX devices with Bluefin validated E2E. This includes 6 models.
  • For PAX devices, a new XML tag is added so that an ISV can specify the PAX forms package to be used for any transaction or TranCode that uses a PAX device.
  • For the latest PAX forms package, the STR.AMOUNT_TEXT variable is cleared when displaying the "swipe screen".
Microsoft Windows 11 Pro / 10 Pro / Server 2019 / Server 2016

OR

DSIClientX® 3.86

Release date: 09/01/2011

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

Microsoft Windows 11 Pro / 10 Pro / Server 2019 / Server 2016
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 11 Pro / 10 Pro / Server 2019 / Server 2016
Step 3 - Install NETePay FDMS Rapid Connect Host EMV - RRH 5.07.31 Rental

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: 04/16/2018

  • The following changes are made related to store and forward processing.
    • The SAF_ForwardAll operation will now recover if communication failures occur during the forwarding process. An error will be returned along with the number of transactions that have completed forwarding. A subsequent SAF_ForwardAll will pick up where the previous one left off.
    • If there are no transactions to forward, a SAF_ForwardAll operation will now return SUCCESS along with zero totals.
    • The SAF Totals now include a count of Uncaptured PreAuth requests. All PreAuth transactions should be captured prior to forwarding stored transactions. There is no way to be paid for a forwarded PreAuth that was not captured.
    • There is a purchase amount limit parameter set on PSCS and a purchase limit sent in from the POS. The smaller of the two is compared to the transaction purchase amount. If the transaction purchase amount is less than or equal to the smaller of the two limits, then the transaction can possibly be stored offline. Otherwise, the transaction will go online.
    • There is a maximum stored transaction limit set on PSCS and a stored transaction limit sent in from the POS. The smaller of the two is compared with the current number of stored transactions. If the addition of one more transaction would keep the number of stored transaction under or equal to the smaller of the two limits, then the transaction can possibly be stored offline. Otherwise, the transaction will go online.
  • Rapid Connect AthNtwkID is now returned as part of AcqRefData and used for subsequent Void and ChipOverride transactions.

New build released 4/23/18 - Fix to return correct CaptureStatus of TeleCheck transactions.

Microsoft Windows 11 Pro / 10 Pro / Server 2019 / Server 2016