fiskaly E-RECEIPT

Introduction

fiskaly E-RECEIPT (fiskaly RECEIPT BASIC) is a cloud-based digital receipt solution that enables POS providers (CUSTOMER) and their merchants to replace paper receipts with legally compliant, environmentally friendly digital receipts. The service facilitates the digitization of receipts and payment confirmations in order to comply with legal obligations related to the issuance of digital receipts. It is accessed via the fiskaly RECEIPT API and managed through the fiskaly HUB.

Service Description

fiskaly delivers a digital receipt solution to the CUSTOMER, including:

• Provision and use of the fiskaly RECEIPT API for digitizing receipts and payment confirmations.
• Digital receipts are generated and made accessible via a semi-anonymous URL.
• Delivery to the consumer via a QR code mechanism or partner apps such as mobile wallets.
• The issuance of up to 20,000 receipts per month per ORGANIZATION of type UNIT (previously type MANAGED).
• Access to a dashboard for configuring digital receipts per business location (language, logo integration, etc.).
• Compliance with the highest standards of data security and data protection in accordance with applicable laws.

📘Note

The CUSTOMER must create an ORGANIZATION of type UNIT (previously type MANAGED) for each individual business location (location) to ensure legal compliance and correct system use.

Functionalities

• Digital receipt generation: Receipts are generated via the API and made accessible through a semi-anonymous URL.
• QR code delivery: Consumers can access receipts by scanning a QR code at the point of sale.
• Partner app delivery: Receipts can also be delivered via partner apps such as mobile wallets.
• Dashboard configuration: Per-location configuration of digital receipts (language, logo, branding).
• Volume: Up to 20,000 receipts per month per ORGANIZATION of type UNIT (previously type MANAGED).
• GDPR-compliant: Data security and protection in accordance with applicable regulations.

System Requirements

• A valid contractual relationship with fiskaly.
• An internet connection for integration and operation.
• Integration of the fiskaly RECEIPT API into the CUSTOMER’s POS system.
• Compatibility of the POS system with the RECEIPT API (regular updates and maintenance may be required).
• Creation of an ORGANIZATION of type UNIT (previously type MANAGED) for each business location.

Maintenance and Support

fiskaly is committed to maintaining and updating the E-RECEIPT service. fiskaly undertakes to maintain and update the Service with a view to supporting its security, availability, and ongoing alignment with applicable technical 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 environment for the RECEIPT API. The CUSTOMER can validate its integration before going live. Free testing is available for developers. fiskaly is not responsible if real data is used in the TEST environment.

Service Limitations

• The issuance is capped at 20,000 receipts per month per ORGANIZATION of type UNIT (previously type MANAGED).
• The CUSTOMER is responsible for the accuracy of all data provided for document creation (company data, line items, transaction/payment details).
• fiskaly complies with data security and protection standards but the CUSTOMER is responsible for POS system compatibility and maintenance.

Customer Obligations

• Responsible for integrating the RECEIPT API into the POS system.
• Must ensure the compatibility of POS systems with the service and maintain them for full functionality.
• Must create an ORGANIZATION of type UNIT (previously type MANAGED) for each individual business location.
• Must ensure the accuracy of all data provided for document creation, including company data, line items, and transaction/payment details.
• Regular updates and maintenance of the POS system may be required for optimal RECEIPT API performance.

---

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