fiskaly SIGN AT

Introduction

fiskaly SIGN AT is a cloud-based fiscalization solution for the Austrian market, provided as Software as a Service (SaaS). It enables POS providers (CUSTOMER) and their merchants (END CUSTOMER) to comply with the Austrian Cash Register Security Regulation (Registrierkassensicherheitsverordnung, RKSV) by providing cryptographic signing of cash register transactions. The service is 100% cloud-based, requires no hardware, and is accessed via a RESTful API and managed through the fiskaly HUB.

Service Description

fiskaly makes SIGN AT available to the CUSTOMER as SaaS. The CUSTOMER obtains access to the functionality via the API and may sublicense its use to END CUSTOMERS through an authorisation system. Key aspects include:

• Provision of a cloud-based fiscalization solution in accordance with RKSV.
• Non-exclusive, non-transferable right of use, limited to the contract term and the territory of the Republic of Austria, sublicensable only to END CUSTOMERS.
• Data generated by the END CUSTOMER is held by fiskaly for a period of three (3) months.
• Provision of the current version of fiskaly SIGN AT, including updates at irregular intervals.
• Access to a TEST SYSTEM.
• Use of the fiskaly HUB for management and administration.

📘Note

fiskaly’s scope of services does not include: integration into recording systems; individual solutions or adaptations; training; internal documentation (except public integration instructions via workspace.fiskaly.com); data transfer services; storage beyond three (3) months; support not expressly specified; or other products of fiskaly.

Functionalities

• Cryptographic transaction signing: Transactions are signed in accordance with RKSV for inalterability and traceability.
• Authorisation system: The CUSTOMER manages END CUSTOMER access via user credentials or other approved procedures.
• Management via fiskaly HUB: Administration and configuration of fiskaly SIGN AT instances.
• Continuous monitoring: fiskaly monitors functionality up to the API and eliminates malfunctions.
• Malfunction management: Priority-based fault reporting and response as defined in the annex “service and malfunctions.”
• Update management: Updates are announced at least one week in advance and deployed during defined maintenance periods (except emergency updates).

System Requirements

• A valid contractual relationship with fiskaly.
• An internet connection for integration and operation.
• Integration of the fiskaly SIGN AT API into the CUSTOMER’s recording system, in accordance with the interface documentation and requirements.
• Non-blocking or asynchronous integration to ensure uninterrupted recording system operation.
• The CUSTOMER must ensure operation of the recording system is not limited in case of a potential outage of fiskaly SIGN AT.

Maintenance and Support

fiskaly is committed to maintaining and updating fiskaly SIGN AT. fiskaly undertakes to maintain and update the Service with a view to supporting its security, availability, and ongoing alignment with applicable technical and reporting requirements; however, the Customer remains responsible for implementing required updates, migrations, and integration changes on its side. The service is versioned according to semantic versioning; significant changes resulting in new major releases will be documented. Maintenance activities may result in the temporary outage of the service. As far as possible, these activities shall be announced at least two (2) weeks in advance; emergency maintenance activities may deviate from this. fiskaly provides assistance to customers via the fiskaly support portal (support.fiskaly.com).

Testing

fiskaly provides a TEST SYSTEM for fiskaly SIGN AT. The CUSTOMER can use the sandbox to validate its integration before going live. fiskaly is not responsible if real data is used in the TEST environment.

Service Limitations

• Functionality outside the API (particularly on recording systems) is not warranted.
• No warranty for proper integration into the CUSTOMER’s recording system.
• No warranty for fulfillment of individual recording obligations, document issuance requirements, or cash register obligations beyond the technical security device provision.
• No warranty for other requirements for proper recording system operation (e.g., correct offline-handling integration, documentation obligations, archiving).
• No binding resolution times for malfunctions.
• Fault reports from END CUSTOMERS directly are not accepted or processed.

Customer Obligations

• Responsible for integrating fiskaly SIGN AT into recording systems at own expense, meeting all framework criteria and system requirements per the interface documentation.
• Must ensure the recording system’s operation is not limited in case of a potential outage.
• Must support fiskaly to a reasonable extent and not engage in hindering conduct (e.g., abusive use of transaction volume, storage, or incorrectly categorised support tickets).
• Must ensure all information for implementing fiskaly SIGN AT is correct and available; faulty information may lead to inadmissible operation and extra costs.
• Must not misuse the service or negatively affect availability for other customers; data must be free of harmful components.
• Acknowledges that the END CUSTOMER is responsible for all statutory obligations pursuant to RKSV.
• Must notify fiskaly of any changes to company data in writing and in a timely manner.
• Must keep access credentials confidential and report unauthorised access immediately.
• Must provide END CUSTOMERS with all necessary information for legal compliance and service use.

---

Version: v.1 | Last updated: 2026/03/24