Please follow the steps below to complete your installation of NETePay BB&T NETePay Host - VRH 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.38

Release date: 11/15/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.38

  • Support is added for the IDTech VP3300 device for Monetary. Supports chip and swiped cards with Monetary PAN encryption. SecureDevice value is as follows.
    • EMV_VP3300_MONETARY
  • Support is added for Ingenico Tetra devices for Worldpay Core (Vantiv) supporting TDES DUKPT PAN encryption. Clear Ingenico Tetra Lane models are also supported for Vantiv. SecureDevice values are as follows.
    • EMV_LANE3000_VANTIV
    • EMV_LANE5000_VANTIV
    • EMV_LANE7000_VANTIV
    • EMV_LANE8000_VANTIV
    • EMV_LANE3000_VANTIV_E2E
    • EMV_LANE5000_VANTIV_E2E
    • EMV_LANE7000_VANTIV_E2E
    • EMV_LANE8000_VANTIV_E2E
    • EMV_LINK2500_VANTIV_E2E
    • EMV_MOVE3500_VANTIV_E2E
    • EMV_MOVE5000_VANTIV_E2E
  • A new TranCode is supported called “GetAnswer” to allow an ISV to ask a question on an Ingenico device. The ISV supplies the <TranCode> tag with a value of “GetAnswer”, a <Question> tag with the question to be displayed on the device, and optionally a <QuestionTimeout> tag with a value from 10 to 120 (seconds). The default timeout value is 30 seconds and the two buttons default to “Yes” and “No”. The ISV can override the "Yes"/"No" on the buttons by supplying the <AnswerYes> tag with a new value and the <AnswerNo> tag with a new value. The following is example XML that will wait 15 seconds for a reply and display "12-OZ" and "16-OZ" on the buttons. If the "Yes" button is pressed, the response includes a <CmdStatus> tag with a value of "Success". If the "No" or "Cancel" button is pressed, the response includes a <CmdStatus> tag with a value of "Error".
    • <TStream>
          <Transaction>
              <HostOrIP>127.0.0.1</HostOrIP>
              <IpPort>9000</IpPort>
              <MerchantID>000014715961</MerchantID>
              <TerminalID>002</TerminalID>
              <TranCode>GetAnswer</TranCode>
              <SecureDevice>EMV_LANE7000_VANTIV_E2E</SecureDevice>
              <ComPort>5</ComPort>
              <Question>WHAT SIZE COFFEE?</Question>
              <QuestionTimeout>15</QuestionTimeout>
              <AnswerYes>12-OZ</AnswerYes>
              <AnswerNo>16-OZ</AnswerNo>
          </Transaction>
      </TStream>
            
  • For Ingenico devices, Discover MSD contactless is now disabled. Soon we will be doing the same for Amex and then all four brands will have MSD contactless disabled.
Microsoft Windows 10 Pro / 8 Pro / 7 Pro / Vista Pro / XP Pro

OR

dsiPDCX® 1.64

Release date: 11/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.64

  • Support is added for the IDTech VP3300 device for Monetary. Supports swiped cards with TDES DUKPT PAN encryption loaded with a Monetary encryption key. Requires firmware version V1.01.049 or higher. SecureDevice value is as follows.
    • IDTVP3300_MONETARY_E2E
  • Support is added for Ingenico Tetra devices for Worldpay Core (Vantiv) supporting TDES DUKPT PAN encryption. SecureDevice values are as follows.
    • INGENICOLANE3000_VANTIV_E2E
    • INGENICOLANE5000_VANTIV_E2E
    • INGENICOLANE7000_VANTIV_E2E
    • INGENICOLANE8000_VANTIV_E2E
    • INGENICOMOVE3500_VANTIV_E2E
    • INGENICOMOVE5000_VANTIV_E2E
    • INGENICOLINK2500_VANTIV_E2E
  • For manually keyed EBT transactions using Ingenico PAN encryption (TDES and OnGuard), the expiration date field is now cleared allowing NETePay to provide any required default value to the payment service.
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 BB&T NETePay Host - VRH 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: 09/10/2019

  • Support is added for EMV PreAuth, PreAuth and PreAuthCaptureByRecordNo. For a PreAuth, TSYS is sent a purchase transaction with a “HOLD”. If a merchant is a “hold capture participant” then NETaPay can include a “HOLD” tag in the authorization request. Including this authorization tag prevents the transaction from being captured and settled. For PreAuthCaptureByRecordNo, an adjustment transaction with the Reference Number is sent to TSYS with a “CAPTURE”. This will cause the held authorization to be released and will be captured during the next batch close. Note: If a merchant is not a “hold capture participant” and a “HOLD” tag is sent to TSYS, the host will reject the transaction and respond with "Not Allowed”.

    If an Incremental Auth or Partial Reversal has been run following a PreAuth, then the amount captured must be exactly the final authorized amount. The final capture cannot have an additional TIP added or the purchase amount reduced.

    Following the initial PreAuth, a TIP can be added to the capture. Also, following the initial PreAuth, a lesser purchase amount can be captured as long the <OriginalAuthorized> amount is sent with the capture.

    The Batch Summary and Batch Close responses from TSYS reflect totals of transactions authorized, not settled. If a transaction is captured in a subsequent batch (the “HOLD” is removed), then the totals returned by the Batch Summary and Batch Close will not match the amount settled. If all transactions are captured prior to the Batch Close, then the totals returned by the Batch Summary and Batch Close will match the amount settled.

  • The latest Store and Forward library is released with this version. Version 5.0 library prevents storing a transaction offline while an SAF_ForwardAll is in progress.

New build released 9/18/19 - Updated to use SAF library 6.0 to fix a critical stop error which can occur while forwarding without IP connectivity.

New build released 10/29/19 - Update to SAF library 7.0. This fixes a critical stop error which can occur where a forward contains a voided transaction with more than 1 child. This also corrects an issue where transactions may go online even though ForceOffline is set to "Y".

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