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

Release date: 04/19/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.31

  • For Ingenico devices (except the iSC250 and iSC480), during an EMV ParamDownload, the delay time for a Contactless event is set to 2.5 seconds. This is used to prevent a Contactless read from occurring when attempting an MSR swipe with a Contactless card.
  • For Ingenico devices, if EMV Contactless is enabled, MSD Contactless is disabled for Visa and Mastercard. This applies only to configurations where the NETePay supports EMV Contactless processing and “Contactless Support” is set to “EMV”. For configurations where only MSD Contactless is supported, MSD Contactless is still enabled for all card types.
  • For Ingenico Telium devices, if a PadReset is performed with a card inserted, the device automatically displays “Please remove card” and beeps. Tetra devices do not automatically display “Please remove card” and beep. For this reason, dsiEMVUS now sends the “Please remove card” message and beep message to Tetra devices during a PadReset if a card is inserted. The PadReset command will not wait forever for the card to be removed. If the PadReset times out with the card still inserted, the pad will be reset again which will display “Welcome”.
  • For Ingenico Telium devices, support is added for Ingenico’s “Terms and Conditions” form. This does not currently work on Tetra devices.
  • For Ingenico devices, support is added for Parking IN/OUT using customer data provided on the way IN and the way OUT to allow a Parking system to determine the parking rate and charge the customer.
  • Support is added for Ingenico Telium and Tetra devices for Datacap to be used with a Datacap TDES DUKPT key processing through Datacap’s hosted NETePays. Devices include the iSC250, iPP350, iPP320, iCMP, iUC285, iSC480, iUP250, iSMP4, iWL258, Lane/3000, Lane/5000, Lane/7000, Lane/8000, Link/2500, Move/3500 and Move/5000. Support is also added for Telium devices for Datacap for validated P2PE. These devices use Ingenico OnGuard encryption where the PAN data is decrypted via Bluefin when processing through Datacap’s hosted NETePays. Devices include the iSC250, iPP320, iUC285 and iSMP4. New SecureDevice IDs are as follows.
  • All XML fields required for Admin functions BatchReportQuery and BatchReportTransaction now pass through dsiEMVUS to a NETePay.
Microsoft Windows 10 Pro / 8 Pro / 7 Pro / Vista Pro / XP Pro


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


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.34 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: 01/10/2019

This version supports a new Local Batch Inquiry feature. This allows an ISV to programmatically retrieve transaction data from the Local Batch Reporting tables. When using Store and Forward, it provides an easy way to review transaction data for declines which translate directly to merchant losses. The Local Batch Inquiry feature include two new TranCodes – BatchReportQuery and BatchReportTransaction. These are both <Admin> functions. The Local Batch database contains two tables, BATCH and DECLINE. The BATCH table contains all approved transactions. The DECLINE table contains all declines and errors.

  • The following are optional XML fields for BatchReportQuery
    • <TransDateTimeBegin>
    • <TransDateTimeEnd>
    • <CmdStatus>
    • <SAFOnly>

For <TransDateTimeBegin> and <TransDateTimeEnd>, a date range may be supplied with or without times. Valid formats are “YYYY-MM-DD” or “YYYY-MM-DD HH:MM:SS”. If these tags are not supplied, today’s date is assumed.

For <CmdStatus>, valid values are “Approve”, “Decline” or “All”. Use “Approve” to retrieve data from the BATCH table. Use “Decline” to retrieve data from the DECLINE table. Use “All” to retrieve data from both tables. If this tag is not supplied, “Decline” is the default.

For <SAFOnly>, valid values are “Yes”, “No”, or “All”. Use “Yes” to retrieve data only for transactions that were stored and forwarded. Use “No” to retrieve data only for transactions that were not stored. Use “All” to retrieve data for all transactions whether stored or not. If this tag is not supplied, “Yes” is the default.

Using all defaults, the BatchReportQuery will return transaction IDs for today’s stored transactions that were declined when forwarded. Transaction data returned for BatchReportQuery include <IdNo#> to uniquely identify each transaction, where # is a numeric value. Other response fields include …

  • <InvoiceNo#>
  • <Status#> - Approved, Declined, or Error
  • <TransDateTime#>
  • <IsSAF#> - Yes or No

Using the <IdNo#> value, the BatchReportTransaction can be used to retrieve the detail information for the specific transaction. The value is sent in the <IdNo> tag. Transaction data returned for BatchReportTransaction include values from the BATCH or DECLINE table …

  • <IsSAF> - Yes or No
  • <Status> - A, X, V, Declined, Error
  • <TranCode>
  • <CardType>
  • <AcctNo> - truncated showing last 4 digits
  • <ExpDate> - truncated
  • <AccountSource> Swiped, Keyed, etc.
  • <Purchase> - Purchase amount
  • <Authorize> - Authorized amount
  • <AuthCode>
  • <RefNo>
  • <TransDateTime>
  • <InvoiceNo>

Integration documentation will be updated in the near future to include full examples with all XML fields. These new Admin functions can be implemented via DSIClientX or dsiPDCX. No cardholder data is collected since these are Admin functions.

New build released 1/29/19 - Change to store and forward logic which will allow PreAuth/EMVPreAuth transactions to be captured even if stored records exceed the maximum time length. This prevents a situation where PreAuth/EMVPreAuth transactions must be captured prior to forwarding but can't be

Microsoft Windows 10 Pro / 8 Pro / 7 Pro (Windows XP and Vista do not support TLS 1.2 which is now an industry requirement)