Terminals APIs


Integration Strategies


Integration Strategies Overview 

With many terminal solutions and terminal integration approaches available, it is often difficult to choose the one appropriate for your integration.

Below you will find high-level overview of all of the available options, as well as different evaluation criteria, which you can use while making your integration decision. One of the key characteristics of our terminal solution, which differentiates it from many other solutions existing on the market, is that it requires no middleware (such as DLL libraries, ActiveX components or Java applets) installed on the client machine operating POS. While DLLs are available for desktop-based applications, they are provided for respective developers’ convenience, and not as a requirement to use the solution. This characteristic of our solution makes it particularly appealing for web-based POS systems.

The Cloud integration strategy, which is available through this terminal solution, is explained below.

Payment Page Integration 

This integration strategy is similar to the previous one. It also eliminates the need for POS to interact with the terminal directly; the terminal integration is accomplished using a customizable payment page, which has a built-in integration with a terminal. The approach is particularly convenient for those who already use payment page solution for their online payments or for swiper based retail processing. This integration strategy suits those who do not need very elaborate POS functionality (handling items, discounts, points, etc) and who want to deal with on-line payments and retail payments through the same unified page.

The integration is accomplished using classical payment page approach and the outcome of the transaction (similarly to the Gateway Integration strategy) is posted back to the POS server via callback (notification) URL provided as part of the initial transaction request (issued by POS). This integration strategy has the same two limitations as the Gateway Integration strategy, and is not appropriate for system with no centralized application server. Despite its limitations, this strategy can satisfy 100% of the processing needs of an average POS system. For more information on this strategy, please see the gateway integration specification and integration notes as well as sale operation using payment page.

See this diagram to review the structure of the payment page integration strategy.