Terminology
The following table contains descriptions and explanations of terms commonly used in the context of the Experience Middleware.
These terms relate to customer-facing features such as Digital Receipt, InStore App, and payment integrations.
| Term | Description |
|---|---|
| Bundle | A predefined configuration package that groups digital receipt features and behavior for simplified rollout and setup. |
| Digital Receipt | A receipt generated after fiscalization and delivered to the consumer in a digital format (for example via QR code or HTTPS link), while remaining linked to the fiscal receipt. |
| HTTPS Receipt | A digitally accessible receipt delivered via a secure HTTPS link, typically accessed through a QR code displayed at checkout. |
| InStore App | A customer-facing application provided by fiskaltrust that displays receipts and receipt interaction options on a device at the point of sale. |
| Multi-Terminal Setup | A configuration where multiple InStore App instances receive receipts from one or more CashBoxes, typically distinguished by terminal identification. |
| Payment Provider (PSP) | A third-party service responsible for processing payment transactions, which can be accessed through the fiskaltrust payment integration. |
| POS (Point of Sale) | The system used by merchants to process sales, initiate payments, and communicate with the fiskaltrust.Middleware. |
| QR Code | A machine-readable code displayed on a customer-facing device that allows consumers to access a digital receipt using a mobile device. |
| Receipt Identifier | A unique reference that allows a digital receipt to be securely resolved and accessed after fiscalization. |
| Receipt Link | A URL that points to a digital receipt hosted by the digital receipt backend, typically encoded as a QR code. |
| Terminal Identification | A configuration value used to associate receipts from a specific CashBox or terminal with an InStore App instance. |
| Unified Payment Endpoint | A standardized interface provided by fiskaltrust to initiate and process payments while remaining independent of specific payment service providers. |
Table 1: Experience Middleware Terminology