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

Release date: 02/12/2024

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

  • Support is added for Pax A3700 devices. New SecureDevice values are below.
    • EMV_A3700_PAYMENTECH
    • EMV_A3700_VANTIV_E2E
    • EMV_A3700_TSYS
    • EMV_A3700_TSYS_VOLT
    • EMV_A3700_RAPIDCONNECT
    • EMV_A3700_RAPIDCONNECT_E2E
    • EMV_A3700_HEARTLAND
    • EMV_A3700_DATACAP
    • EMV_A3700_DATACAP_BLUEFIN
  • For Pax devices configured for EMV Debit Only,the contactless CVM limit is now set to zero causing a PIN prompt to occur when a Debit card is tapped regardless of the amount.
  • For Verifone P400, P200 and M400 devices, this version explicitly enables the U01 command – external AID selection. The previous version,1.75, disables external AID selection. If a merchant supports Credit and Debit and a chip card includes both a Debit and Credit AID, then the card holder will be prompted with two application labels to choose between. We cannot display “Select Debit?” like Ingenico and Pax devices. If the POS sends a transaction with <CardType>Credit</CardType> (demands credit) or sends a transaction with <CardType>Debit</CardType> (demands debit), then external AID selection allows the specific AID to be chosen automatically without the cardholder being prompted with one or more application labels.
  • Pre-dip functionality is added for Pax devices. The normal EMV transaction is split into two parts where the first part involves only collecting the card data and the second part involves processing a payment using the card data previously stored. A new method (function call) is added called CollectCardData. Once card data is collected, it can be used repeatedly by including XML tag <UseLastCardID> in any “EMV” payment request. The transaction will process without any prompts for card data. Amount prompting will still occur if not suppressed. Any “ByRecordNo” transaction will ignore a <UseLastCardID> tag in the request and process as “ByRecordNo” using the token in the <RecordNo> tag. Today, CollectCardData is supported only for Pax devices. However, when a “normal” transaction is performed with any Secure Device, the card data is now stored in memory allowing the same card data to be used repeatedly on the following transaction using the <UseLastCardID> tag and supplying the correct last four digits from the card account number. This allows the same card data to be used for a split payment. dsiEMVUS stores only the last card data collected and must be identified with a matching value in the <UseLastCardID> tag to be used for any subsequent transaction.
Microsoft Windows 11 Pro / 10 Pro / Server 2019 / Server 2016

OR

dsiPDCX® 1.91

Release date: 02/12/2024

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

  • Support is added for Pax A3700 devices. The PAX devices support Credit, Debit, EBT and PrePaid. New SecureDevice values are below.
    • PAXA3700
    • PAXA3700_DATACAP_E2E
    • PAXA3700_DATACAP_BLUEFIN
    • PAXA3700_VANTIV_E2E
    • PAXA3700_RAPIDCONNECT_E2E
    • PAXA3700_TSYS_VOLT
    • PAXA3700_HEARTLAND_VOLT
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 EVO US EMV (FD-RC) Host - 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