Please follow the steps below to complete your installation of NETePay Global Payments Portico Host EMV - GPP 5.07.36

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

Release date: 04/13/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.61

Support is added for a "non-cash adjustment" that an ISV can include as part of an electronic payment. This new fee must be included in the purchase amount supplied to dsiEMVUS by the ISV. For receipt formatting, the ISV must also provide the adjustment amount in a new tag <PaymentFee>. This will allow the fee to be broken out on the receipt that is built by dsiEMVUS. The ISV can also supply the description of the fee by providing the new tag <PaymentFeeDescription>. If the description is not provided, then "Payment Fee" will be used as the description for the fee on the receipt. The value of <PaymentFee> is also passed through to NETePay, but all NETePays today ignore this new tag. This is one reason why the ISV must include the fee in the purchase amount provided.

As an example, if the purchase amount with tax is $20 and the fee is $1.50, then 21.50 must be provided in the <Purchase> tag. The <PaymentFee> tag would be provided with 1.50. And the value of the <PaymentFeeDescription> in this example is "NON-CASH ADJ".

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


dsiPDCX® 1.79

Release date: 04/04/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.79

GetPrePaidStripe is modified for the IDTech VP3300 device. The MSR read is now more reliable because any whitelisted BIN ranges are loaded during the SecureDeviceInit. ISV’s should always perform a SecureDeviceInit as least once to load the BIN file and verify that the device successfully communicates with dsiPDCX.

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


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 Global Payments Portico Host EMV - GPP 5.07.36

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: 03/31/2021

  • The value of the InvoiceNo field is now sent to Portico in the “DirectMktInvoiceNbr” field for select Credit card transactions.
  • This version is built with the latest Store & Forward library (8.20). Version 8.20 includes a fix for Incremental Auth transactions when interwoven with multiple transaction sequences of PreAuth, Incremental Auth, Partial Reveral and PreAuthCapture. Each sequence is now forwarded in order, regardless of how the transactions were stored originally.

New build released 5/17/21 - <DirectMktData> removed.

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