Please follow the steps below to complete your installation of NETePay Worldpay IP (Mercury) US EMV + Debit - MPH 5.07.31

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

Release date: 12/15/2021

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

  • For IDTech VP3300 and VP8300 devices, the cardholder name was not being returned for chip card transactions. In cases where the POS requests the cardholder name, dsiEMVUS now disables autoAuthenticate for EMV. This slows the transaction somewhat, but causes the device to perform an additional command so that more card and terminal data are returned. If the POS does not request the cardholder name, then there are no changes to the transaction flow for EMV. DDT-327
  • For Ingenico devices, two new Display Message events are now triggered during the EMV transaction flow. After a card is detected and the EMV flow begins, the Display Message event "Please Wait…" is now triggered. After the conversation with the card is completed and the transaction is out at NETePay for authorization, the Display Message event "Please Wait … Authorizing" is now triggered. DDT-229
  • For Ingenico devices, during external AID selection when a card includes both a Credit AID and a Debit AID, dsiEMVUS typically prompts the cardholder "Select Debit?". However, if the POS requires Debit by sending <CardType>Debit</CardType>, then dsiEMVUS no longer prompts and automatically chooses the Debit AID. The same is now true for Credit. If the POS requires Credit by sending <CardType>Credit</CardType>, then dsiEMVUS no longer prompts and automatically chooses the Credit AID. DDT-220
  • For all devices that support manual card entry, the POS can now disallow the prompt for Zip Code. The POS can provide the cardholder’s billing Zip Code in the <Zip> tag or send <Zip>Disallow</Zip> to prevent the device from prompting the cardholder for a Zip Code. DDT-158

New build released 12/17/21 - EncryptedFormat error fixed for Mercury Vx805 XPI 12.

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

OR

dsiPDCX® 1.76

Release date: 11/30/2021

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

  • Support is added for the following IDTech devices.
    • IDTech Augusta for First Data Rapid Connect with TDES DUKPT PAN encryption.
    • IDTech SecureHead MSR for First Data Rapid Connect with TDES DUKPT PAN encryption.
    • IDTech VP3300 for First Data Rapid Connect with TDES DUKPT PAN encryption.
    • IDTech VP8300 for First Data Rapid Connect with TDES DUKPT PAN encryption.
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 Worldpay IP (Mercury) US EMV + Debit - MPH 5.07.31

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: 01/16/2019

  • 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.
  • For the “EMV Support” parameter, the choices now include …
    • None
    • Credit
    • Credit and Swiped PIN Debit
    • Credit and EMV Debit
    • Credit and Debit - Prefer Debit
  • This version also supports new parameters for contactless. The new parameters are …
    • "Contactless Support" – the choices are MSR or EMV.
    • “EMV Contactless CVM Limit (dollars)” – for EMV Contactless this amount will control whether or not a CVM is required. Over the amount some cardholder verification method is required.
Microsoft Windows 10 Pro / 8 Pro / 7 Pro (Windows XP and Vista do not support TLS 1.2 which is now an industry requirement)