Linkly APIs

Linkly has created several flexible interfaces for use by our partners.

Our interfaces provide support for a variety of connection methods and store architectures, ensuring there is a Linkly interface that will suit your needs. 

Linkly Cloud

The Linkly Cloud solution houses our proven middleware components within Linkly’s own environment, removing the need to install anything locally. This allows the solution to be used by any combination of hardware and software. 

Linkly strongly recommends supporting this interface for new integrations as it’s the fastest and simplest way to integrate Linkly's payment solution. Using the Linkly Cloud means there is no need for a direct connection between the PINpad and the POS.


View API Docs


ActiveX

Use Linkly’s Windows based components to complete payment integration

The Linkly ActiveX allows clients to integrate Windows based POS to the Linkly payment solution. This is the natural choice for POS’ that are already based upon the Windows platform. Connect PINpad and POS systems easily via USB, RS-232 or Ethernet (WIFI or cabled) and you’re ready to go. 


View API Docs


TCP/IP

Seamlessly run Linkly’s components locally, while communicating with them from anywhere in the store.

The Linkly TCP/IP interface offers a flexible way to integrate a Linux based POS to the Linkly payment solution.Connect PINpad and POS systems easily via USB, RS-232 or Ethernet (WIFI or cabled) and you’re ready to go.


View API Docs


Linkly Online API


Part of our MerchantSuite collection of solutions, Linkly’s Online API offers a REST interface using HTTP over SSL. Requests are submitted to process transactions, create and update entities including tokens, and perform searches.

Requests to the API are categorised by the different areas of functionality of the platform. The API supports transaction processing, token processing and more. Each area has its own URL endpoint and different HTTP methods to imply different operations, for example retrieval of information from the database is handled by the GET operation, while updates are handled by either POST or PUT requests.

For nearly all operations, requests and responses are defined within a JavaScript Object Notation (JSON). Where appropriate the API also supports WebForm (HTTP POST) requests for operations, allowing seamless integration with web applications.

Errors from the API are handled by both HTTP Status Codes and API specific response codes. HTTP Status Code errors handle generic scenarios, such as using incorrect HTTP verbs or incorrect URLs. API response codes handle specific validation, system errors and invalid authentication details.



View API Docs

Protecting Your Business

As important as your business is to you, so too is protecting your data to us. The Payment Card Industry Data Security Standard (PCI DSS) is a set of regulations ensuring entities and agents that transmit, receive, handle or process credit card information are required to comply with stringent data regulations - operating in a secure environment to protec both the customer and the merchant against fraud.

Our middleware solutions connect over 200,000 terminals that comply with PCI-PED security requirements and PIN cryptography standards, securely handling more than 2b transaction annually. Linkly does not have access to cardholder details, PINs, or any other sensitive information as defined by the PCI organisation.

We’re committed to ensuring best practice and compliance when it comes to sensitive data and work closely with governing bodies ensuring our solutions are continuously updated to the highest industry standards.


Read More