Development

SDK
SDK Version 4.8.5.2.zip Full Release CD in zip format

CloudTunnelSetup
CloudTunnelSetup.zip

For any development questions please email [email protected]

Start developing with Linkly

A POS can communicate with Linkly using one of several different interfaces. The most appropriate interface to implement will depend on the POS architecture.

Please note some connectivity options are only available for specific banks and/or PIN pads.

POS architecture

Local

The EFT-Client and POS are running on the same computer. The PIN pad is either connected to the same computer using USB or serial, or somewhere else on the LAN using an Ethernet-enabled PIN pad.

Available Linkly interface options:

LAN/WAN

The EFT-Client and POS are running on different computers.  The PIN pad is either connected to the same computer as the EFT-Client using USB or serial, or somewhere else on the LAN using an Ethernet-enabled PIN pad.

Available Linkly interface options:

Internet

The EFT-Client is hosted by the Linkly Cloud. Both POS and PIN pad connect to the Linkly Cloud over the Internet.

Available Linkly interface options:

Linkly interfaces

TCP/IP

The TCP/IP interface is implemented using a proprietary message format. The POS connects to the EFT-Client on port 2011.

When using this interface the EFT-Client can be running on Windows XP SP2, Windows Vista, Windows 7, Windows 10, Linux or Android.

Getting started with the TCP/IP interface:

TCP/IP via TLS

The TCP/IP interface is implemented using a proprietary message format (the message format is the same as the standard Linkly TCP/IP interface, with the addition of TLS and an authorisation logon).

Since the EFT-Client is hosted by the Linkly Cloud, this option is supported on any platform which can support TLS over TCP/IP.

Getting started with the Linkly Cloud TCP/IP interface:

Active-X

The ActiveX interface utilises the Linkly ActiveX control (CsdEft.ocx) which is included in the standard Windows Linkly installation.

When using this interface the EFT-Client can be running on Windows XP SP2, Windows Vista, Windows 7 or Windows 10.

Getting started with the ActiveX interface:

HTTP

The HTTP interface is implemented using a proprietary message format (the message format is the same as the standard Linkly TCP/IP interface) wrapped in HTTP and can be used by POS systems with a local EFT-Client and which can’t implement either the ActiveX or TCP/IP interface.

When using this interface the EFT-Client can be running on Windows XP SP2, Windows Vista, Windows 7 or Windows 10.

Getting started with the HTTP interface:

File based

The file interface is implemented using a separate application (DosToActiveX) which is included in the SDK.

When using this interface the EFT-Client and DosToActiveX can be running on Windows XP SP2, Windows Vista, Windows 7 or Windows 10.

Getting started with the file based interface:

  • Download the SDK
  • Specification and setup instructions are available under the \Software\File Interface folder in the SDK