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

Release date: 06/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.33

  • Support is added for the IDTech Augusta device for TSYS (SecureDevice values is "EMV_AUGUSTA_TSYS"). The IDTech device does not encrypt the card data for TSYS. IDTech does not support Voltage encryption that is required for TSYS card data encryption. The IDTech Augusta firmware required is V1.02.020.
  • Data fields required for Hotel integration are now supported and passed through dsiEMVUS. The EMV US Client Test app now includes a check box for “Hotel Fields”. When this box is checked, a dialog box will be displayed to enter supported Hotel fields. This will provide a way to enter these fields during EMV testing. Hotel support will be released with the next version of the Heartland Portico NETePay.
  • MSD contactless for Visa cards is now disabled for the Verifone Vx805 XPI 12 supporting Mercury and Elavon and for the Verifone P400 supporting Mercury.
  • For all Ingenico devices, Dynamic AID selection is enabled during an EMV ParamDownload if the corresponding NETePay has the “EMV Support” parameter set to “Credit and Debit”. With this release, Dynamic AID selection is disabled if the “EMV Support” parameter is set to “Credit and Debit – Prefer Debit”.
  • For Ingenico unattended devices, integrators use a ZeroAuth transaction and indicate <ReturnCustomerData>No Payment </ReturnCustomerData> to obtain a token for the card data collected. Support is added for Cardholder Name by sending the <CollectData>CardholderName</CollectData> tag as part of this same request.
  • Fix for MiniSmart II firmware version detection.
Microsoft Windows 10 Pro / 8 Pro / 7 Pro / Vista Pro / XP Pro

OR

dsiPDCX® 1.60

Release date: 05/15/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.60

  • Support is added for the following Ingenico Tetra devices for Monetary and Mercury using a TDES DUKPT PAN encryption key.
    • Lane/3000
    • Lane/5000
    • Lane/7000
    • Lane/8000
    • Move/3500
    • Move/5000
    • Link/2500
  • A new option for manual entry on the PC screen is added to allow an ISV to use the legacy entry screen. To select the legacy manual card entry screen when prompting for card data, the tag Allow should be included in the XML request.
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.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)