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

dsiPDCX® 1.86

Release date: 02/03/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.86

  • The PAX IM30 for Worldpay Core (Vantiv) is released now that we have a full certification for this unattended device.
  • The previous versions of dsiPDCX required swiped EBT cards to be encrypted when using an encrypted Verifone device. Swiping an EBT card where the track 2 data contained only the account number resulted in an error from Verifone and an error from dsiPDCX (“No Encrypted Track Data.”). Swiping an EBT card where the BIN was in the white list resulted in a successful read from Verifone, but an error from dsiPDCX because the data was not encrypted (“Command Currently Not Supported.”). In both of these cases, dsiPDCX will now return the clear card data. Major credit cards have Track 2 data that Verifone will always encrypt, so would not be returned clear for an encrypted device. For EBT transactions, swiping any card that produces some card data (clear or encrypted) should result in dsiPDCX using that card data for the transaction and sending it to NETePay for processing.
Microsoft Windows 10 Pro / 8 Pro / 7 Pro / Vista Pro / XP Pro

OR

dsiEMVUS® 1.67

Release date: 01/27/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.67

  • The PAX IM30 for Worldpay Core (Vantiv) is certified.
  • A new response field <SystemTraceAuditNo> is passed back through the client when provided by NETePay.
  • For PAX devices, the following new TranCodes are supported. The latest PAX forms package is required.
    • GetYesNo
    • GetMultipleChoice
    • GetSuggestiveTip
Microsoft Windows 10 Pro / 8 Pro / 7 Pro / Vista Pro / XP Pro

OR

DSIClientX® 3.86

Release date: 01/05/2023

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

1/5/23 - New DSIClient test application released to remove username from the usertrace field.

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.32 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: 07/16/2018

  • PA-DSS 3.2
  • Store and Forward is added. This is an optional feature that must be enabled via PSCS and requires integration changes.
  • Pay At The Table is added. This is an optional feature that must be enabled via PSCS and requires integration changes.
  • Local Batch Reporting data storage is added. This is an optional feature that must be enabled via PSCS. Data can be viewed using the Local Batch Report Viewer.

New build released 8/7/18 - Fix for incorrectly initialized variables related to tokenization which can result in declines with response "SETUP TOKEN REQD M71".

New build released 10/26/18 - Change made to store and forward logic to fix an issue where transactions that should have been stored were forced online instead.

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