Please follow the steps below to complete your installation of NETePay Monetary - Host Server - MTR 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.25

Release date: 08/13/2018

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 PC based POS solutions page.

Release notes for v1.25

  • Support for a new field on EMVParamDownload is added to specify a reboot time for Ingenico devices. Ingenico PCI v4 devices must reboot once a day and the Datacap PIN pad loader software used by distributors automatically sets the reboot time to 0400. This time can be changed by an integrator by send a new tag <PinPadRebootTime> (HHMM – 24 hour) during the EMVParamDownload operation. Setting the reboot time of an Ingenico PCI v3 device in this way will also enable 24 hour reboot. The EMV US Client Test app provides an edit box to send a PIN pad reboot time during an EMVParamDownload.
  • For Ingenico devices, dsiEMVUS typically sends commands to request device specific information on each transaction. Starting with version 1.25, dsiEMVUS remembers certain information for subsequent transactions provided the integrator keeps the control in memory. This speeds up subsequent transactions by limiting the commands. An EMVParamDownload will force all device specific commands to be sent to a device.
  • Support for FSA transactions is added similar to the functionality previously added to dsiPDCX. For an EMV Sale, if a card is swiped or hand-keyed and the leading six digits of the account number matches one of the BINs listed in the <FSABins>, the <FSATotalAmount> is copied to the <Purchase> amount and the <TranCode>; is changed from EMVSale to FSASale. The FSASale is sent to NETePay for processing. If the card presented does not match one of the BINs listed in the <FSABins>, the transaction is processed as a credit or debit EMVSale where the FSA amounts are ignored. The integrator is required to supply the following tags.
    • <FSABins> - list of 6-digit FSA card BINs separated by a comma.
    • <FSATotalAmount> - dollar amount of the transaction that is FSA eligible.
    • <FSAPrescription> - optional FSA prescription amount included in the transaction.
    • <FSAVision> - optional FSA vision amount included in the transaction.
    • <FSADental> - optional FSA dental amount included in the transaction.
    • <FSAClinical> - optional FSA clinical amount included in the transaction.
  • Heartland EMV receipts now include the Application Cryptogram with the value of tag 9F26. The Application Cryptogram is prefixed with "ARQC:" indicating the type of cryptogram.
Microsoft Windows 10 Pro / 8 Pro / 7 Pro / Vista Pro / XP Pro

OR

dsiPDCX® 1.53

Release date: 07/19/2018

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

  • Modernized dialogs including manual entry. The manual entry box appears on the PC screen when the SecureDevice value is “NONE” or the SecureDevice does not provide manual entry.
  • DisplayMessage event added to provide status updates so that a POS system can track the progress of the transaction from swipe to PIN to processing.
  • A number of changes are included for Ingenico devices to try to speed up transactions.
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: 06/12/2018

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

  • Declined/Error tab added. If supported by NETePay details about transactions which received a decline or error response will be displayed when local batch reporting is enabled.
Microsoft Windows 10 Pro / 8 Pro / 7 Pro / Vista Pro / XP Pro
Step 3 - Install NETePay Monetary - Host Server - MTR 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/10/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.
Microsoft Windows 10 Pro / 8 Pro / 7 Pro (Windows XP and Vista do not support TLS 1.2 which is now an industry requirement)