Platforms

The fiskaltrust.Middleware runs either locally on the POS device or in a data center. On a local device, a Launcher starts the components of the fiskaltrust.Middleware (Queue, SCU, Helpers). In a data center, the fiskaltrust.Middleware runs in a container or is hosted by fiskaltrust as the fiskaltrust.Middleware for Cloud.

This page gives an overview of the available platforms, where to download the matching Launcher and how to install it. Which platforms are available depends on the market. For the platforms per market, see Availability by market.

Overview

Platform	Launcher	Runtime prerequisites	Download	Installation
Windows	Launcher 1.3 (fiskaltrust.exe)	.NET Framework 4.8 recommended	fiskaltrust.Portal	Windows
Windows	Launcher 2.0 (fiskaltrust.Launcher.exe)	None (self-contained)	fiskaltrust.Portal, GitHub	Windows
Linux, macOS	Launcher 1.3 (fiskaltrust.exe on Mono)	Mono 6.8.0 or higher	fiskaltrust.Portal	Linux and macOS
Linux, macOS	Launcher 2.0 (fiskaltrust.Launcher)	None (self-contained)	fiskaltrust.Portal, GitHub	Linux and macOS
Android	fiskaltrust.Middleware for Android (app)	Android 7 or higher	GitHub, v2.0.0 pre-release (APK)	Android
Docker, Kubernetes	Bring your own Data Center (Germany only)	Docker; Helm for Kubernetes	GitHub	Docker and Kubernetes
Any (hosted)	None	None	No download	fiskaltrust.Middleware for Cloud

Table 1. Platforms of the fiskaltrust.Middleware with Launcher, prerequisites, download and installation.

Launcher 1.3 and Launcher 2.0

Two generations of the Launcher for Windows, Linux and macOS exist:

• Launcher 1.3 (fiskaltrust.exe) runs on the .NET Framework on Windows and on Mono on Linux and macOS. On Linux and macOS, SOAP is not supported and the REST endpoints differ from Windows. For more information, see Supported Environments.
• Launcher 2.0 (fiskaltrust.Launcher) is self-contained and needs no third-party runtime on any of these platforms. It is used, for example, by the Italian Middleware and is required for the local POS System API. For more information, see Installation for Italy and POS System API platforms.

The fiskaltrust.Portal offers the Launcher that matches the configured CashBox. To migrate from Launcher 1.3 to Launcher 2.0, see the migration guide in the middleware-launcher repository.

Launcher 2.0 is built for the following operating systems and architectures:

Operating system	Architecture
Windows	x64, x86
Linux	x64, arm64, arm
macOS	x64, arm64

Table 2. Operating systems and architectures for which Launcher 2.0 is built.

Launcher 2.0 is built on .NET 10 (since v2.0.0-rc.36; earlier versions on .NET 8) and supports the operating system versions that .NET 10 supports.

Download from the fiskaltrust.Portal

For Windows, Linux and macOS, download the Launcher for a configured CashBox from the fiskaltrust.Portal:

1. Open the fiskaltrust.Portal in the environment you need (sandbox or production).
2. Select Configuration > CashBoxes.
3. Select Rebuild configuration for the CashBox, and wait for the success confirmation.
4. Select Download for the CashBox and choose the Launcher for the operating system and the processor architecture of the target device.

The download is a ZIP archive that already contains the configuration of the CashBox (CashBox ID and access token). Extract it into the folder from which the Middleware is to run.

For a description of the Launcher variants offered in the download dialog (.NET Launcher, Mono Launcher), see Download of the Launcher.

Windows

Requirements

• Launcher 1.3: Windows 7 or higher, 32 or 64 bit; .NET Framework 4.8 recommended.
• Launcher 2.0: a Windows version supported by .NET 10, x86 or x64; no additional software.

For the supported Windows versions per market, see Windows (Germany) and Windows (Italy).

Installation

Step	Launcher 1.3	Launcher 2.0
Test in the console	Run test.cmd as administrator.	Run launcher-test.cmd.
Install as a Windows service	Run install-service.cmd as administrator.	Run launcher-install.cmd as administrator.
Uninstall the service	Run uninstall-service.cmd as administrator.	Run launcher-uninstall.cmd as administrator.
Start and stop the service	Windows Services dashboard, or net start [SERVICENAME] and net stop [SERVICENAME]	Windows Services dashboard, or net start [SERVICENAME] and net stop [SERVICENAME]

Table 3. Installation steps on Windows for Launcher 1.3 and Launcher 2.0.

For more information, see Launcher for Windows, Linux and macOS (Launcher 1.3) and Getting Started (Launcher 2.0).

Linux and macOS

Requirements

• Ubuntu or Debian recommended; most testing at fiskaltrust is done on these distributions.
• Launcher 1.3: Mono 6.8.0 or higher. The Mono versions in the default package repositories are usually outdated; install Mono following the official Mono guidelines.
• Launcher 2.0: no additional software.

Which distributions, data storages and SCUs are supported depends on the market, because each market uses its own signature devices (with their own drivers and certifications) and, depending on the market, Launcher 1.3 on Mono or the self-contained Launcher 2.0. For more information, see Linux and macOS (Germany) and Linux and macOS (Italy).

Installation

Step	Launcher 1.3 (Mono)	Launcher 2.0
Test in the console	Run test.sh, or sudo mono fiskaltrust.exe -test.	Run launcher-test.sh.
Install as a service	Run install-service.sh as root.	Linux only: run launcher-install.sh (requires systemd and sudo rights). Not available on macOS.
Uninstall the service	Run uninstall-service.sh as root.	Linux only: run launcher-uninstall.sh (requires sudo rights).
Start and stop the service	For example systemctl start [SERVICENAME] and systemctl stop [SERVICENAME]	Linux only: systemctl start [SERVICENAME] and systemctl stop [SERVICENAME]

Table 4. Installation steps on Linux and macOS for Launcher 1.3 and Launcher 2.0.

For more information, see Mono Service Installation (Launcher 1.3) and Getting Started (Launcher 2.0).

Android

Requirements

• Android 7 or higher.

The fiskaltrust.Middleware for Android (eu.fiskaltrust.androidlauncher) is a single app that runs the fiskaltrust.Middleware as a foreground service. The POS app calls it through the POS System API over Android IPC, so no network configuration is needed on the device. For more information, see Android IPC Transport.

The Queue and SCU packages are bundled with the app and cannot be downloaded at runtime, so updates are rolled out as app updates. We recommend a mobile device management (MDM) solution to control the rollout of updates.

Download

The app is released as Android Launcher 2.0, currently as a beta (pre-release) version. Download eu.fiskaltrust.androidlauncher-Signed.apk from the latest v2.0.0 pre-release on the releases page of the middleware-launcher-android repository.

caution

The releases marked as Latest (v1.3.x) contain the legacy HTTP and gRPC apps, which do not provide the POS System API over Android IPC.

Installation

1. Install the APK on the device, ideally through MDM.
2. Exempt the app from battery optimization, so that it can run in the background.
3. Call the POS System API from the POS app through the bound service (recommended) or the Activity Intent. For more information, see Choosing a transport.

An internet connection is required at least on the first start, to download the configuration.

Docker and Kubernetes

Germany only

Bring your own Data Center is only available in Germany.

For cloud POS systems in a private data center or a public cloud (for example Azure or AWS), the Middleware runs in a Docker container. For high-load installations, a Helm chart for Kubernetes clusters is provided. We recommend the fiskaltrust.Middleware for Cloud over a Bring your own Data Center setup for simpler installation and maintenance.

The installation guidelines are maintained in the product-de-bring-your-own-datacenter repository. For more information, see Custom data center.

fiskaltrust.Middleware for Cloud

The fiskaltrust.Middleware for Cloud is the fiskaltrust.Middleware hosted by fiskaltrust. Nothing is installed on the POS device, so any platform with an internet connection can use it, including iOS and web-based POS systems. The POS system connects with the CashBox ID, an access token and a URL.

For more information, see CloudCashbox.

Network requirements

The Launchers download their configuration and, except on Android, their packages from the fiskaltrust servers. Allow the outbound connections listed in Network requirements.