Please follow the steps below to complete your installation of NETePay FDMS Rapid Connect Host EMV - 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.30

Release date: 03/21/2019

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

  • For all Ingenico devices, Dynamic AID selection is enabled during an EMV ParamDownload if the corresponding NETePay has "EMV Support" parameter set to "Credit and Debit". With this configuration, both Credit and Debit AIDs will be loaded into the PIN pad. When a card is inserted that supports both a Credit AID and a Debit AID, the cardholder will be prompted "Select Debit?". The cardholder should press "Yes" for Debit or "No" for Credit. For earlier versions of dsiEMVUS, the cardholder was shown a list of AIDs and was required to select one of the AIDs presented. Only if the card inserted includes both a Credit AID and a Debit AID will the cardholder be prompted "Select Debit?".
  • The EMVParamDownload function now supports the <PinPadRebootTime> for the Verifone P400. An integrator can send a time (HHMM) on the EMVParamDownload which will override the default value in the P400. If no PinPadRebootTime is specified on the EMVParamDownload, dsiEMVUS will use a value of "0500". The <PinPadRebootTime> was previously supported for Ingenico devices.
  • For Verifone Vx805 devices (XPI 8 and 12), the transaction type in the C30 command is now set to a value of 0x20 for Return transactions. The transaction type value is sent along in EMV transactions in the 9C tag. Now that payment services are sending Credit Return transactions on for authorization, it’s important that the 9C tag indicates a Return for EMV Credit Return transactions. Other dsiEMVUS devices already send the correct 9C tag for EMV Credit Return transactions.
  • Worldpay IP (Mercury) now supports an optional <RecurringData> tag. This tag is now passed through dsiEMVUS.
Microsoft Windows 10 Pro / 8 Pro / 7 Pro / Vista Pro / XP Pro

OR

dsiPDCX® 1.59

Release date: 02/20/2019

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

  • Support is added for the following Ingenico Telium and Tetra devices for Datacap using a Datacap TDES DUKPT PAN encryption key.
    • iSC250
    • iPP320
    • iPP350
    • iCMP
    • iSC480
    • iSMP4
    • Lane/3000
    • Lane/5000
    • Lane/7000
    • Lane/8000
    • Move/3500
    • Move/5000
    • Link/2500
  • Support is added for the following Ingenico Telium devices for Datacap when using OnGuard Validated P2PE via Bluefin.
    • iSC250
    • iPP320
    • iPP350
    • iCMP
  • Support is completed for the Verifone Vx805 running XPI 12 for Worldpay IP (Mercury). The version of XPI is 12.11.38. This XPI version supports TDES DUKPT data variant E2EE. There is no new SecureDevice value for this device. The same value is used whether using XPI 8.42b or XPI 12.11.38 (VX805XPI_MERCURY_E2E). dsiPDCX automatically determines the XPI version and adjusts accordingly.
  • Support is added for Worldpay IP VAS gift card on the Verifone P400. This includes support for a new EncryptedFormat with a value of MercuryAppleGift. The Mercury MM GIFTePay requires changes to support this new Encrypted Format.
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 FDMS Rapid Connect Host EMV - 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 10 Pro / 8 Pro / 7 Pro (Windows XP and Vista do not support TLS 1.2 which is now an industry requirement)