Merge pull request #19 from fiskaltrust/sidebar-updated

Added Experience Middleware to sidebar

Author: deboragracio

poscreators/middleware-doc/appendix-me/appendix-me.md

@@ -6,7 +6,7 @@ title: Introduction
 # Fiscalization in Montenegro
 This chapter expands on the information provided in the _General_ chapter by adding details specific to the fiscalization for Montenegro. This additional information is provided only where applicable. The remaining chapters, for which there is no extra information required, were omitted.
 
-Legal regulations and further information can be found [on the website of the Montenegran tax authority](https://www.gov.me/upravaprihoda/elektronska-fiskalizacija).
+Legal regulations and further information can be found on the website of the Montenegran tax authority.
 
 
 <div class="alert alert--warning" role="alert">Please note that this information is only complete when combined with the <b>General</b> part. To implement the Middleware, users should get themselves familiar with the general information first and then refer to the country-specific details listed here.</div>

poscreators/middleware-doc/experience-middleware/introduction.md

@@ -0,0 +1,29 @@
+---
+title: Introduction
+slug: /poscreators/experience-middleware/introduction
+---
+
+# Introduction
+
+The **Experience Middleware** extends the fiskaltrust.Middleware with features that improve the checkout experience for merchants and consumers, without changing existing POS workflows.
+
+While the compliance stack focuses on fiscal requirements such as receipt signing, journaling, and reporting, the Experience Middleware builds on top of these core capabilities to enable modern, customer-facing features, such as **digital receipts**, **customer interaction**, and **integrated payment flows**.
+
+## Included Experience Components
+
+The Experience Middleware consists of the following components:
+
+- **Payment**: Integrates payment flows into the fiskaltrust platform using a unified payment endpoint, while keeping POS systems independent of specific payment providers.
+
+- **Digital Receipt**: Enables receipts to be delivered digitally via QR code, link, message, or other channels after a transaction has been fiscalized.
+
+- **InStore App**: A customer-facing application that displays receipts, QR codes, and receipt interaction options at the point of sale.
+
+Each component can be used independently or combined, depending on the business case and market requirements.
+
+## Intended Audience
+
+This documentation is primarily for **PosCreators** and integrators who want to:
+- Enhance checkout flows with digital receipts and customer interactions.
+- Integrate customer-facing devices or displays.
+- Combine fiscalization and payments through a single middleware layer.

poscreators/middleware-doc/experience-middleware/payment.md

@@ -0,0 +1,43 @@
+---
+title: Payment
+slug: /poscreators/experience-middleware/payment
+---
+
+# Payment
+
+The **Payment** component of the Experience Middleware allows POS systems to integrate payments through fiskaltrust without being tied to a single payment service provider.
+
+Rather than replacing existing POS payment logic, fiskaltrust provides a **unified payment endpoint** that can be used alongside fiscalization and digital receipt features. This keeps integrations flexible and avoids vendor lock-in.
+
+Payments are integrated through the **InStore App** and the POS System API, allowing transactions, fiscal receipts, and optional digital receipts to be handled in a coordinated flow.
+
+## Key Design Principles
+
+The payment solution follows these core principles:
+
+- **Single POS integration**: POS systems integrate once with the fiskaltrust payment endpoint and remain independent of specific payment providers.
+
+- **Optional usage**: Payments can be used with or without fiskaltrust fiscalization, depending on the market and setup.
+
+- **No mandatory lock-in**: Merchants and partners are not forced into a single PSP (Payment Service Provider) or hardware setup.
+
+- **Experience-driven**: Payment flows can be combined with digital receipts and InStore App interactions to create a smoother checkout experience.
+
+## Payment Integration Flow in the Experience Stack
+
+A typical payment-enabled flow consists of the following steps:
+
+1. The POS initiates a payment using the unified fiskaltrust payment endpoint.
+2. The selected payment provider processes the transaction.
+3. fiskaltrust links payment data with the fiscalized receipt.
+4. The receipt can optionally be displayed or handed over via InStore App, QR code, or Digital receipt channels.
+
+This approach ensures that fiscalization, receipts, and payments remain technically linked while staying modular.
+
+## Intended Audience for Payment Integration
+
+Payment integration is primarily relevant for:
+
+- **PosCreators** who want to support multiple payment providers with a single integration.
+- **PosDealers** managing merchant rollouts across markets.
+- **PosOperators** who want simpler setups, fewer devices, or hardware-free payment options where available.

poscreators/middleware-doc/experience-middleware/terminology.md

@@ -0,0 +1,27 @@
+---
+title: Terminology
+slug: /poscreators/experience-middleware/terminology
+---
+
+# 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*