The Pay at Table API provides a common interface for the PIN pad to utilise the EFT-Client to retrieve available tables and orders so payment functions (e.g. tender, customer receipt etc.) can be performed by an operator on the PIN pad without using the main POS UI.
The Pay at Table client requires the POS to act a data source so that it can retrieve information about available tables, orders, payment options etc.
The Pay at Table client supports two data source options for the POS; a REST server or directly through the existing Linkly interface.
To start developing the Linkly Pay at Table solution, following the instructions on the Linkly API.
When in REST server mode the Pay at Table extension will connect directly to the POS REST Server.
An example REST server can be found in the PayAtTable.ServerCore folder.
- .NET Core 3.1
- ASP.NET Core
- Serilog
- Swashbuckle
- Visual Studio 2019
- Launch Visual Studio and open the PayAtTable.ServerCore solution
- Run the application. The default listen port is 5000. This can be configured in
appsettings.json - Logs are written to
%PROGRAMDATA%\Linkly\PayAtTable\Logs. This can be configured inappsettings.json - Define
SERVICEto compile as a Windows service. UndefineSERVICEif the application will be hosted behind - You can browse to http://localhost:5000 to see the UI and http://localhost:5000/swagger/ to see the API definition
If SSL is required, Linkly suggests hosting the application in reverse proxy-mode and offloading SSL handling to a front-end web server such as Nginx, Apache, or IIS.
v1.0.0.0
- Initial release.