Skip to main content

98 docs tagged with "Middleware"

View all tags

Android

Running the Italian Middleware on Android 7.0+ — preconfigured SQLite queue with Epson and Custom SCUs, distribution via Portal or Google Play.

Android

How the Android Launcher hosts the Middleware as a foreground service, where to download it (Portal or Google Play), and how updates work.

Android Intent Integration

How Android POS apps call the fiskaltrust.Middleware side-by-side via Android intents for offline fiscal operations, with endpoints and examples.

Architecture

The three-tier fiskaltrust setup of POS system, Middleware, and Portal, and the roles of CashBox, launcher, Queue, SCU, and helpers.

Backup & Restore

Which Middleware components to back up locally (database and data directory) and the steps to restore a Middleware setup on a new system.

Cash Register Integration

Recommended receipt creation workflow with fiskaltrust.Middleware — SecurityMechanism, special and closing receipts, receipt structure and journals.

Cash Register Integration

Placeholder for cash register integration in Belgium that links to the general cash register integration workflow.

Cash Register Integration

Cash register integration in accordance with Spanish law, extending the general integration workflow of the Middleware.

Cash Register Integration

Receipt creation, special receipts such as daily, monthly, annual and archive receipts, receipt structure and journals for France.

Cash Register Integration

Cash register integration in accordance with Greek law, extending the general integration workflow of the Middleware.

Cash Register Integration

Entry point for cash register integration under Italian law, linking to the general integration workflow of the Middleware.

Cash Register Integration

Placeholder chapter on cash register integration under Portuguese law, pointing to the general integration workflow.

Cashbox

What a CashBox configuration contains, how to find its CashBoxID and AccessToken, and how to create, configure, and rebuild CashBoxes in the portal.

CloudCashbox

What the hosted CloudCashbox is, how to order and create CloudCashboxes in the fiskaltrust.Portal, and how to migrate existing CashBoxes to it.

Communication

Communication protocols supported by fiskaltrust.Middleware — gRPC, REST, WCF and user-specific — and how to set them in the Portal.

Communication

Communication protocols supported by the German Middleware — REST, gRPC and WCF — with details on gRPC, proto files and the NuGet client.

Communication

REST communication with fiskaltrust.ChaineCloud for France — base URL, JSON/XML content types, headers and echo, sign and journal calls.

Communication

Communication protocols supported by the Italian Middleware — REST, gRPC and WCF — with details on gRPC proto files and the .NET client package.

Configuration

Core Middleware configuration in the fiskaltrust.Portal — Queues, journals, notifications — with links to scenarios for Austria, Germany, France and Italy.

Configuration

How to set runtime parameters of a locally deployed .NET Middleware in fiskaltrust.exe.config or through Launcher command-line parameters.

Custom data center

Bring your own Data Center for Germany — running the Middleware Launcher in Docker or Kubernetes in private or public clouds, compared to SaaS options.

Data Structures

Field reference for ReceiptRequest, cbCustomer, ReceiptResponse, ChargeItem, PayItem and SignatureItem used with fiskaltrust.Middleware.

Data Structures

Austria-specific fields of the receipt response, charge items, pay items and signature entries in the Middleware data structures.

Data Structures

Placeholder for Belgium-specific data structures that links to the general Middleware data structures chapter.

Data Structures

Spanish rules for cbCustomer — required fields for invoices, NIF validation and TicketBAI foreign customer identification.

Data Structures

French fields of the receipt request and response — bills and table changes, copies, training mode, charge items, pay items and signatures.

Data Structures

How cbCustomer fields are transmitted to myDATA as the document counterpart for Greece, and when the customer is required.

Data Structures

Placeholder chapter for Portugal-specific data structures, pointing to the Data Structures chapter of the General Part.

eInvoicing

How eInvoicing is layered onto the /sign and /issue calls, what varies by market, and availability for Austria, France, Germany, Italy and Poland.

Failure Scenario

How to handle an unreachable Middleware in France — degraded mode receipts, failed receipt flag and late signing mode.

Failure Scenarios

How to handle SCU failures, an unreachable Middleware and cash register outages, including failed mode and late-signing receipts.

Function Structures

The iPOS interface functions echo, sign and journal, with synchronous v0 and asynchronous v1 call examples.

Function Structures

Echo, sign and journal functions of the iPOS interface for France, including the ChaineCloud empty echo queue reinitialization.

Helper

What Middleware Helpers do, examples such as the POS-API Helper and HelipadHelper, and how to add, configure, and assign a Helper to a CashBox.

Installation

Launcher call parameters for fiskaltrust.exe on Windows, Linux and Mac for the German Middleware, plus Mono and .NET prerequisites.

Installation

French specifics for installing the Middleware, including debug launchers for Windows and Linux (Mono).

Installation

Installing the Italian Middleware on Windows, Linux and macOS with the self-contained fiskaltrust Launcher 2.0.

Integration Checklist

Checklist of required steps per market for PosCreators — sandbox and production accounts, API implementation, certification and dealer connection.

Introduction

Overview of the stages a PosCreator goes through to integrate fiskaltrust.Middleware, with a tutorial video and presentation slides.

Introduction

Overview of the Experience Middleware components — Payment, Digital Receipt and InStore App — and who the documentation is for.

Introduction

Entry point to the fiskaltrust.Middleware interface specification — access, workflow, data and function structures, communication and operation modes.

Introduction

What the Austrian RKSV requires of a POS system — signing, DEP-7 exports, FinanzOnline — and where to start in the Austrian Middleware docs.

Introduction

Entry point to the Belgium-specific Middleware pages, which extend the General Part only where the Belgian market needs it.

Introduction

Entry point for the German KassenSichV appendix, which adds Germany-specific details to the General Part of the Middleware docs.

Introduction

Entry point to the Spanish market appendix of the Compliance Middleware, to be read together with the General Part.

Introduction

Entry point to the French market appendix of the Middleware for secured cash desk software under BOI-TVA-DECLA 30-10-30.

Introduction

How fiscalization works in Greece via AADE myDATA and the MARK, and where to start in the Greek market appendix.

Introduction

Introduction to the Italian Registratore Telematico appendix, which adds Italy-specific details to the general Middleware documentation.

Introduction

Introduction to the Polish Middleware appendix (preview) — certified cash register model, CRK reporting and differences from other markets.

Introduction

Entry point to the Portuguese appendix of the Middleware docs, including the AT-certified invoicing program under certificate 3535.

Introduction

Overview of the process-driven, idempotent POS System API — authentication, headers, core endpoints, request flow, and versioning.

Logging

Middleware log levels, how to configure the log level and log file, the log format, and how to provide logs to fiskaltrust.Support.

Middleware

The fiskaltrust.Middleware as a product for PosDealers — its security mechanism, deployment options and country-specific variants.

Middleware Components

Logical components of fiskaltrust.Middleware — iPOS interface, Queue, SCU, Helipad helper, launcher — plus hardware and platform requirements.

My First Cashbox

Creating a first CashBox as a PosDealer with a Business Rollout plan or manual configuration, then running a test request.

Network Requirements

Inbound and outbound network access the Middleware needs, including required hostnames and ports, plus how to set up and edit proxy configurations.

Network troubleshooting

How to diagnose Middleware network issues — verifying online mode, the fiskaltrust firewall script, and common DNS, network, SSL, and Queue/SCU errors.

Operation Modes

On-premise, off-premise and private cloud environments for fiskaltrust.Middleware and their availability by market.

Operation Modes

Middleware components and configuration for France, managed via the French fiskaltrust.Portal at portal.fiskaltrust.fr.

Overview

Core features of the fiskaltrust.Middleware and its main components — CashBox, Launcher, Queue, and SCU — with on- and off-premise deployment options.

Overview - Business Basics

Introduction to the PosDealer business basics section — supported countries, services, the Portal, the Middleware and prerequisites.

Overview - Technical Operations

Overview of the Technical Operations section for PosDealers — rollout scenarios, Middleware integration, monitoring, troubleshooting, and maintenance.

Proactive actions

Overview of proactive actions that keep Middleware installations reliable — backups, updates, receipt archive, monitoring, and logging.

Product overview

Categories of fiskaltrust products for PosDealers — bundles, the free Middleware, signing devices and services, and add-on subscriptions.

Receipt Case Definitions

Definitions of business cases such as POS sales receipt, invoice, single and multi-use vouchers, agency business, delivery note and tips.

Receipt Case Definitions

Placeholder for Belgium-specific receipt case definitions that links to the general receipt case definitions.

Receipt Case Definitions

Stub for German receipt case definitions that points to the Receipt Case Definitions chapter of the General Part.

Receipt Case Definitions

Placeholder for Spanish receipt case definitions that extend the general receipt case definitions of the Middleware.

Receipt Case Definitions

French business cases — service and value vouchers, agency business, tips, duplicates and advance deposit invoices.

Receipt Case Definitions

Placeholder for Greek receipt case definitions that extend the general receipt case definitions of the Middleware.

Receipt Case Definitions

Entry point for Italy-specific receipt case definitions, linking to the general receipt case definitions of the Middleware.

Receipt Case Definitions

How the Middleware processes each receipt case in Poland — register interaction, KSeF invoices, closings, and the constraints the queue enforces.

Receipt Case Definitions

Placeholder chapter for Portugal-specific receipt case definitions, pointing to the Receipt Case Definitions of the General Part.

Reference tables

The hex-based tagging format used for Austrian ftReceiptCase, ftChargeItemCase and other case values, with links to each table.

Reference Tables

The v2 hex tagging system and values for ftReceiptCase, ftChargeItemCase, ftPayItemCase and related flags, including local flags per market.

Reference Tables

The hex-based tagging format for Belgian case values and links to the Belgium-specific reference tables.

Reference Tables

Overview of the German reference tables that map receipts, charge items and pay items to the Middleware tagging system.

Reference Tables

Overview of the hex-based tagging format behind the Spanish reference tables for receipt, charge item and pay item cases.

Reference Tables

Overview of the hex-based tagging format behind the Greek reference tables for receipt, charge item and pay item cases.

Reference Tables

Overview of the Polish reference tables that map the POSSystem API v2 tagging structure to the Polish market.

Reference Tables

Overview of the Portuguese reference tables that map the POSSystem API v2 tagging structure to the Portuguese market.

Rollout Scenarios

Rollout scenarios for placing SCUs, Queues, and POS Systems, from one SCU per POS System to shared signature services and hosted Middleware, with pros and cons.

Service Status: ftState

ftState values for Spain — global and local flags signalling queue, SCU and late signing status in receipt responses.

Service Status: ftState

ftState values for Greece — ready status, global and local flags, and how they combine with general states via OR.

Services

fiskaltrust product portfolio for PosDealers — Middleware, Portal, revision-safe receipt archive, exports, hosted Middleware and signing.

Setup

Structure of a locally deployed .NET Middleware — the files in the installation directory and the contents of the data directory.

Supported Environments

Operating systems, databases, hardware, CPU architectures, and storage the Middleware requires on Windows, Linux, macOS, and Android.

Terminology

Definitions of general terms and abbreviations used in the fiskaltrust.Middleware interface documentation, such as SecurityMechanism and iPOS.

Terminology

Placeholder for the terminology of the Belgian fiskaltrust.Middleware — content is still under development.

Terminology

Placeholder for Spanish market terminology of the Compliance Middleware, currently under development.

Terminology

French market terms for the Middleware, such as fiskaltrust.Queue period totals and DGFiP, extending the general terminology.

Terminology

Polish fiscal terms such as kasa rejestrująca, kasa wirtualna, and CRK with English glosses and descriptions.

Troubleshooting Guide

Step-by-step approach to narrowing down Middleware problems before contacting the fiskaltrust Customer Success Team, with country-specific resources.

Updating

How to bulk update CashBox packages and configurations in the fiskaltrust.Portal, control updates, and restart the Middleware afterwards.

Windows

Windows versions supported by the Italian Middleware, which runs as a service on 32-bit and 64-bit Windows 7 and later.

Windows, Linux & macOS

How to download the Middleware Launcher for Windows, Linux, and macOS, install it as a service, run it in test mode, and use command-line parameters.