Open source
Read the code before you run it.
The fiskaltrust.Middleware is open source. The components signing your receipts sit on GitHub, version-controlled and documented. Audit the logic, fork the repositories, follow every release.
$ git clone https://github.com/fiskaltrust/middleware.git# the signing, chaining and journaling logic$ git clone https://github.com/fiskaltrust/middleware-launcher.git# hosts the Middleware on Windows, Linux, macOS$ dotnet add package fiskaltrust.interface# the data interface as a NuGet package- markets on the public code
- 7
- launcher targets
- 4
- demo languages
- 6
- release notes in the open
- All
GITHUB.COM/FISKALTRUST
The repositories, mapped.
Eight repositories carry the stack from specification to running installation. Each link goes straight to the source.
| Repository | What you find inside |
|---|---|
| middleware | The configurable components handling national fiscalisation laws: signing, chaining, journaling |
| middleware-launcher | Hosts the Middleware on Windows, Linux and macOS |
| middleware-launcher-android | Hosts the Middleware on Android devices |
| possystemapi-devkit | Development kit for building against the POS System API |
| middleware-demo | Working demo integrations in C, C++, VB6 and Rust |
| middleware-demo-android | Java and Xamarin demos calling the Middleware over gRPC on Android |
| interface-doc | The technical specification of the data interface, shipped as the fiskaltrust.Interface NuGet package |
| release-notes | Release notes for all products, auto-published to the documentation platform |
INSIDE THE MIDDLEWARE
Modular by design.
The Middleware is a set of configurable components. Each component has one job, and market differences live in configuration instead of code forks. Your integration talks to one interface.
Queue
Receives, processes and chains receipts in order. The transaction backbone of every CashBox.
SCU
The signature creation unit. Connects the signing device or service each market requires, behind one abstraction.
Helpers
Supporting components around the core, from data upload to housekeeping tasks.
fiskaltrust.Interface
The data interface as a NuGet package. Embed the contract directly in your .NET POS.
WHY THIS MATTERS
Compliance without a black box.
Fiscal law makes your receipts a legal artefact. Closed signing logic forces you to trust a vendor. Open code lets you verify instead.
Audit the signing logic
Read the exact code producing your signatures. Show an auditor the version running at your counters.
No lock-in by obscurity
Fork the repositories and run under your own conditions. The exit door stays open, so staying is a choice.
Version compliance with your code
Pin the Middleware version next to your application code. Every release is tagged, every change traceable.
Build fast, compliant & modular
BEYOND THE CODE
The documentation is open source too.
The documentation platform builds from a public repository. Spot a gap or an outdated sample, change the Markdown and send a pull request, the same way you work on code.
Edit this document
Every page on the docs platform links to its source file on GitHub.
Open a pull request
Change the Markdown, branch or fork, and submit against main.
Automated validation
Link checks and a full site build run on every pull request before merge.
Live on merge
Merged changes rebuild and deploy the documentation platform automatically.
GETTING STARTED
Source to signed receipt in three steps.
No sales contact, no registration wall. The path runs through GitHub, the docs and the sandbox.
- STEP 1
Clone or reference
Clonemiddlewarefrom GitHub, or add thefiskaltrust.interfaceNuGet package to your .NET project. - STEP 2
Read the Middleware docs
The documentation platform explains components, communication flows and market configuration. - STEP 3
Sign in the sandbox
Create a sandbox CashBox and send your first request. The quickstart on the developer page walks the path.
SELF-SERVE
Everything you need before a call.
Judge feasibility and fit on your own terms. The stack is documented, public and testable today.
Documentation
Read the docsFull API reference, integration guides and error semantics in English at docs.fiskaltrust.eu.
GitHub
Browse the reposThe Middleware source, launcher, devkit and demo implementations, in the open.
Sandbox
Get accessA near-full copy of the live system. Sign test receipts without legal obligation.
Academy
See the programStructured onboarding for your team, from first request to certified rollout.
FAQ
What developers ask about the open code.
Short answers, with the repositories as the reference.
Is the open-source Middleware the full compliance logic?
Yes. Signing, chaining and journaling live in the public middleware repository. Paid products add hosting, archiving, digital receipts and support around the open core.
Which licence applies?
Each repository carries its licence file on GitHub. Check the LICENSE file in the repository you plan to build on before you ship.
Do I have to self-host?
No. Run the Middleware yourself through the Launcher, or use the cloud-hosted option. The integration stays the same either way.
How do I follow changes?
The release-notes repository publishes every release and feeds the documentation platform automatically. Watch the repository on GitHub for notifications.
Are contributions accepted?
Yes. The docs repository takes pull requests with automated validation, and the code repositories are public on GitHub. Start with an issue for larger changes.
Where do I see working integration code?
The middleware-demo repository holds integrations in C, C++, VB6 and Rust. The Android repository adds Java and Xamarin demos over gRPC.
The code is public. Start reading.
Browse the repositories, read the Middleware docs, then sign your first sandbox receipt through the quickstart.