RetailForce provides a so-called "Fiscal Middleware". The integration of this Fiscal Middleware into an electronic recording system via the standardised, country-independent interface enables the legally compliant operation of electronic recording systems ("cash registers", POS systems, etc.) in many countries.
An overview on supported operating systems can be found in the linked article.
The integration of the Fiscal Middleware into an electronic recording system can be done in several ways:
The connection via the REST interface of the middleware is used most frequently. For this purpose we provide:
- a Windows service (REST web service). We publish the current version of the REST web service in the download area of our website: https://www.retailforce.cloud/downloads/.
- For Linux systems, we provide a Docker container, which you can find on Docker Hub at: https://hub.docker.com/r/retailforce/trusted-fiscal-service finden.
In addition to the web service connection, it is possible to integrate the middleware as dynamic link libraries (DLLs) into the electronic recording system (method call).
For this variant, we provide nuget packages at https://www.nuget.org/profiles/RetailForceDevelopment.
This integration variant is also used for android and iOS POS systems, provided they were developed in .NET.
All information for the implementation of RetailForce Fiskal Middleware in your POS system can be found here in our Solution Center (https://support.retailforce.cloud).
A full description of the RetailForce Document Object Model (DOM) can be found in the Downloads directory of the RetailForce website in the respective version directory.
Special characteristics REST integration
Information on first steps with the REST web service can be found in the linked article
After installing the Fiskal Middleware (as a REST web service) on a computer, you can access the API description via http://localhost:7678/swagger.
Instructions on how to start up the Docker Container under Linux can be found in the linked article.
Special characteristics DLL-Integration
For information on nuget implementation, see the linked article.
To be able to start the Fiscal Service, a so-called "client" must be initialised in the middleware.
A client is always connected / assigned to one cash register (to an independent electronic recording system). One instance of the Fiscal Middleware can contain several clients. The different variants of the use of the fiscal middleware are described below:
|Single Client||Middleware is installed directly on the hardware of the electronic recording system and has 1 client assigned to 1 cash register.||Offline-capable cash register in the supermarket (cash register can work independently, without connection to a central system)|
|Multi Client I||Middleware is installed on a central system (e.g. server in store, in the company's data centre). Several cash registers of one company report transaction data to the middleware. The middleware has one client per cash register.||Store server with several cash registers in the local network|
|Multi Client II||Middleware is installed on a central system (e.g. cloud, in a data centre). Several cash registers from different companies report transaction data to the middleware. This has one client per cash register.||Cloud cash register system which is used by many companies|
The general steps for initializing the middleware are described in the linked article.