T-Gate offers integrators a range of options to integrate into our Payment Server. These include:

 

Web Methods

T-Gate has a thorough web service software development kit for developers seeking to integrate into T-Gate from any independent platform. Integrators can implement web service integration through the following technologies:

• .NET Web Services
• SOAP
• HTTP GET
• HTTP POST

 

Web-based integration offers a number of key benefits:

• Transaction Processing
• Credit Card Utilities
• Reporting
• Recurring Billing
• Administrative
• No additional licensing or software costs to the Merchant
• OS Platform/ Programming Language independence
• Integration is completely indifferent to the peripherals Integrators use with their POS
• Examples can be provided in VB.NET and VB6 and Java

 

SmartPayments Client Integration

The SmartPayments Client application can work as a standalone terminal, integrate with the POS system, RMS and Quickbooks via plugins, or act as a PC Charge Emulator. It has interfaces directly to major processors, as well as an interface directly into the T-Gate Payment Server. The client supports all major transaction types and can invoke all major industry peripherals from card readers, pin pads, check readers, and signature capture peripherals. Integrators can implement the SmartPayments client POS integration through the following technologies:

• File Drop Method - A common integration method that uses an XML industry standard file format. The required fields will be formatted in XML tags as an “input file” that will be dropped or sent to a specified location.
• CP Socket Integration - This method utilizes the same XML tags as the XML file drop but the difference is that this is not dropped as a file but requested by the POS application as a data stream using the winsock OCX component.
• Smartpayments OCX* - This method utilizes a visual Active X component installed by the SmartPayments Admin Client installer in the Hypercom directory. The OCX gives integrators built in hardware support to use with their third party POS integrations saving time and resources. *Note. Only Integrators who develop in Windows environments can use SmartPayments Client since it is a windows service that runs on the local machine.
• IP COM - This method allows integrators to develop POS applications to call specific SmartPayments Admin Client forms to process transaction requests. Since the POS application can call the existing forms to handle transaction requests and response, this approach saves time and resources over internal development efforts.

 

RMS and Quickbooks Plug-ins

The RMS and Quickbooks Plug-ins provide Resellers of those products with a SmartPayments Client enabling integration from POS applications to the T-Gate’s Payment Server.

 

PC Charge Emulation

Integrators who currently utilize PC Charge can switch over to SmartPayment Client with no additional development if they interfaced into PC Charge using the File Drop Method. The Smartpayments Client utilizes the same directory as PC Charge and translates those files into a format that can be resent to any of its processors, including TPI Payment Server. This approach does not require any additional development effort. Integrators simply install the client, configure PC Charge emulation and point the client to the T-Gate Payment Server. The result is a significant cost-savings for Merchants using PC Charge with Smartpayments client

 

PayLink*

PayLink allows integrators to easily outsource payment handling from their POS application to a thin client browser-based virtual terminal (VT) that drives devices and handles payment processing. This thin client VT collects the cardholder data, drives the POS peripherals (such as card readers and PIN-Pads) and submits the transaction information to T-Gate’s Payment Server which returns the transaction result data back in a token format to the POS system.

Integrators can implement integration into Paylink by:

• Accessing the Windows Paylink Object via COM
• Accessing the Windows Paylink Object via .NET
  *Note. Only Integrators who develop in Windows environments can use PayLink Client since it is a windows service that runs on the local machine.

Integration through PayLink offers a number of distinct advantages:

• PayLink is PA-DSS certified, easing the burden of compliance on behalf of the Integrator.
• Thin API document and sample code provided for easy integration.
• PayLink PA-DSS Implementation Guide to direct Integrators how to interface and stay free from the PA-DSS requirement mandate.
• Current Peripheral invoking include; MagTek Card Readers,Verifone 1000se,Verifone 5000,Ingenico 6xxx series
• The auto-upgrade feature on PayLink supports more peripherals as they get added.
• PayLink is more cost-effective than PC Charge or DataCap NETePay.

 

Shopping Cart API

The Shopping Cart Interface mimics the Authorize.NET version 3.0 system’s interface in order to simplify migration from an existing Shopping Cart or a custom application that is already integrated with Authorize.NET. Shopping Cart developers can integrate into the Payment Server using the below methods:

• WebLink
• ADC (Automated Direct Connect) Relay Response
• ADC Direct Response

Not all functionality of the Authorize.NET system has been implemented in this Shopping Cart Interface.