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.

dsiPDCX® 1.56

Release date: 10/15/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.55

For Ingenico devices, Telium RBA 23 or above and Tetra UPP, a new GetPaymentType function is added. This function displays the Ingenico PAY1.K3Z form to prompt the patron for a Payment Type. On Ingenico iSC250 and iSC480 devices, the form can display up to 5 payment types. For other Ingenico devices the form can display up to 4 payment types. The integrator passes in a list of payment descriptions which are displayed on payment buttons. Depending on the button pressed, the corresponding description is returned. This will allow a patron to select EBT EWIC by pressing an appropriate button. Based on the button pressed, the POS can then initiate the corresponding payment using dsiPDCX or dsiEMVUS.

The integrator sends in a prompt message (SELECT PAYMENT TYPE), the payment button descriptions (CREDIT,DEBIT,EBT CASH, EBT FOOD, EBT EWIC) , and a time out value in seconds.

An endless set of selections are possible by using “OTHER” on one of the payment buttons and then moving to an additional set of buttons with an additional GetPaymentType call. It’s also useful to display EBT as a choice initially and then if EBT is pressed, display the form again prompting “SELECT EBT TYPE” displaying buttons for CASH, FOOD and EWIC.

For encrypted IDTech devices, GetPrePaidStripe will now return clear card data for more cards where the account data is not a major credit card. The test for a major credit card is conservative because we never want to return clear credit card data. If an integrator finds dsiPDCX returning the error “Invalid Card Data - Major Credit Card not Allowed” and believes the card is not a major credit card, given the card data is returned clear from the device, dsiPDCX can be further adjusted to allow the card data to be returned.

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

OR

dsiEMVUS® 1.26

Release date: 09/12/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.26

Support added for the Verifone P400 w/ Mercury encryption (Worldpay IP/Vantiv IP)

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)