German KassenSichV TSS from fiskaly.
Test the technical security system fiskaly SIGN DE and implement the KassenSichV easily. Our API is available to you free of charge!
fiskaly SiGN DE
The fiskaly TSS for the KassenSichV.
fiskaly is your partner for fiskalization in Germany and Europe. Our team consists of experts from IT and finance. Together we developed a software solution, that solves the KassenSichV and the required TSS (certified Technical Security System) simply via cloud.
Benefits of the Cloud TSS.
Up-to-date implementation of the KassenSichV TSS in the cloud — without complicated hardware connections and expensive investments.
Safe & Compliant
Our team of experts has many years of experience in the field of fiscalization of cash registers and recording systems. Together we implement all the requirements safely & law-compliant.
Test it for free
Test our interface for the TSS for free and start to prepare the integration into your existing systems.
Try the fiskaly TSS for free
Test the API of our technical security system and secure your advantage in the implementation of the german Kassensicherungsverordnung.Test API
API & Data model offered by fiskaly
The operational implementation of the German KassenSichV primarily affects developers. We make it easy: Our API and documentation is available free of charge on our developer website.
Learn more on developer.fiskaly.com
Frequently asked questions about the fiskaly TSS
Here we answer frequent questions about our cloud-based TSS.
Is the GoBD-compliant storage of data done via the fiskaly cloud?
We store the data transmitted to us in a legally compliant manner. fiskaly takes over the storage of the data for the duration of the contract period.
Archiving independent of the fiskaly system can be optionally implemented by connecting to various archiving partners.
Does this result in additional costs?
The storage of data in the fiskaly Cloud is already included in the monthly costs. There are no additional costs.
Where is the data stored in the first place?
Your data is stored exclusively in German data centers. Currently, the server location for this is in Frankfurt am Main. The data centers used by fiskaly have been carefully selected and they have the following certifications:
Cloud Environment, Runtime Environment
- ISO 27001 - Managing information risks
- ISO 27017 - Controlling cloud-based information security
- ISO 27018 - Protecting personal data
- SOC 1 - Controls over financial reporting
- SOC 2 - Controls over security, availability, and confidentiality
- SOC 3 - Public report of controls over security, availability, and confidentiality
Datacenter for CSP operation
- ISO 14001:2015
- ISO 27001
- ISO 50001
- ISO 9001:2015
- OHSAS 18001
- PCI DSS
- SOC 1 Type II
- SOC 2 Type II
What happens if the fiskaly Cloud is unavailable for signing?
It can happen that the Internet goes down once. We will inform you about how you can continue to work in a relaxed and legally compliant manner, even if the fiskaly Cloud is unavailable.
The case when the cloud is not accessible is addressed in the June 2019 application decree on Section 146a AO. It must be logged that there has been an outage. The logging is done according to the current logging regulations (GoBD). Our SDK takes care of the logging.
How does the fiskaly SDK handle a network outage or failure?
Transactions are temporarily stored locally on the POS in the event of an offline failure, so that they can be subsequently recorded and signed once the online connection is restored. The requirements according to the AEAO to § 146a of June 2019 only define the logging of the failure. This logging is to be carried out by the recording system and stored in accordance with the approaches of the GoBD (i.e. also with protection against manipulation).
It is recommended to sign the data voluntarily afterwards via the TSS to ensure that all records are also visible in the TSS. However, according to the AEAO, this is not explicitly required.
If you use our SDK, a log of the outage will be created in the event that the fiskaly Cloud is unavailable. As soon as the system is available again, this log is also secured via the TSS. The AEAO does not currently specify a transaction or time limit for offline mode. The only requirement is that the fault must be rectified promptly and in a traceable manner.