Please follow the steps below to complete your installation of NETePay EVO US EMV (CP) Host - PRH 5.07.35 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.66

Release date: 11/14/2022

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

  • Support is added for the PAX A35. Also, the PAX IM30 for EVO is released now that we have a full certification for this unattended device. New SecureDevice values listed below...
    • EMV_A35_PAYMENTECH
    • EMV_A35_VANTIV_E2E
    • EMV_A35_TSYS
    • EMV_A35_TSYS_VOLT
    • EMV_A35_RAPIDCONNECT
    • EMV_A35_RAPIDCONNECT_E2E
    • EMV_A35_HEARTLAND
    • EMV_A35_DATACAP_E2E
    • EMV_A35_EVO
    • EMV_IM30_EVO
  • For Ingenico devices, the left 4 characters of the kernel version is now checked rather than the entire kernel version field returned in the 07. command response.
  • Previously, the IDTech VP6800 would quickly flash “Canceled” during a PadReset. This message has been removed.
  • This version of dsiEMVUS allows the new VoidByInvoiceNo transaction to be passed through to NETePay. The VoidByInvoiceNo trancode does not collect card data.
  • The IDTech VP3300 whitelist is now enabled during the end of an EMVParamDownload. It is expected that an ISV will perform an EMVParamDownload rather than a dsiPDCX SecureDeviceInit which also loads the whitelist for the VP3300.
Microsoft Windows 10 Pro / 8 Pro / 7 Pro / Vista Pro / XP Pro

OR

dsiPDCX® 1.85

Release date: 11/14/2022

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

  • Support is added for the PAX A35. Also, the PAX IM30 for EVO is released now that we have a full certification for this unattended device. New SecureDevice values listed below...
    • PAXA35
    • PAXA35_DATACAP_E2E
    • PAXA35_VANTIV_E2E
    • PAXA35_EVO_E2E
    • PAXA35_RAPIDCONNECT_E2E
    • PAXA35_TSYS_VOLT
    • PAXA35_HEARTLAND_VOLT
    • PAXIM30_EVO_E2E
  • This version of dsiEMVUS allows the new VoidByInvoiceNo transaction to be passed through to NETePay. The VoidByInvoiceNo trancode does not collect card data.
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 EVO US EMV (CP) Host - PRH 5.07.35 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: 12/10/2021

We recently received a certification letter for our EMV certification with Chase for PAX devices. In addition to supporting PAX devices, a CardLookup transaction has been added to allow a Chase Safetech token to be retrieved without performing a Sale or ZeroAuth transaction. The CardLookup will return the credit card brand in the <CardType> tag and the Chase token in the <RecordNo> tag. It will not determine if a card is credit, debit or FSA.

New build released 1/12/22 - Host response timeout corrected.

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