Skip to content

fix links #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
volllly merged 2 commits into from
Feb 24, 2026
Merged

fix links #6

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
21ab524
fix links
volllly Feb 24, 2026
68c12c3
fix
volllly Feb 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .github/workflows/build.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ jobs:
contents: read
steps:
- uses: actions/checkout@v5
with:
ref: ${{ github.event.pull_request.head.sha }}

- uses: lycheeverse/lychee-action@v2
id: lychee_markets
Expand Down
4 changes: 2 additions & 2 deletions poscreators/middleware-doc/digital-receipt/General/compliance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ For consumers, there is an obligation to take the receipt with them (Belegmitnah

Each receipt is related to a "Queue" identified via "QueueID", which identifies the specific POS system within an PosOperator/merchant. Also, this "Queue" is assigned to a single outlet within the PosOperator/merchant, which provides configuration elements like location and logo for the digital receipt header and other metadata for receipt generation.

Each receipt is identified via "QueueItemID", which is generated by the middleware driving the security mechanism within the pos-system. This is also the unique identifier within the temper proof fiskaltrust cloud storage for the receipt. Each receipt is processed and stored according to the fiskaltrust-security-mechanism, therefore it is temper proof and mirrored into fiskaltrust cloud. You can visit following link for further details: https://docs.fiskaltrust.cloud/de/docs/posdealers/buy-resell/products/middleware#security-mechanism.
Each receipt is identified via "QueueItemID", which is generated by the middleware driving the security mechanism within the pos-system. This is also the unique identifier within the temper proof fiskaltrust cloud storage for the receipt. Each receipt is processed and stored according to the fiskaltrust-security-mechanism, therefore it is temper proof and mirrored into fiskaltrust cloud. You can visit following link for further details: [fiskaltrust-security-mechanism](../../../../posdealers/buy-resell/products/middleware.md#security-mechanism).

fiskaltrust appointed Dr. Markus Knasmüller to create an external assessment about the conformity of the various methods of digital receipt creation correspond to the technical requirements of RKSV. The assessment can be requested here: https://forms.office.com/e/0PcMDYWC2B

Expand All @@ -33,7 +33,7 @@ It is required in Austria to implement the POS-API with the /print endpoint or u

For an evaluation of receipt retrieval, it is possible to verify in an audit case (or in general), which receipts were transmitted, retrieved, or printed through the fiskaltrust.Portal using the export function.

You can visit following link in the POS Dealer section for further details: https://docs.fiskaltrust.cloud/de/docs/posdealers/buy-resell/products/digital-receipt#evaluation-of-retrievals-of-digital-receipts
You can visit following link in the POS Dealer section for further details: [evaluation of retrievals of digital receipts](../../../../posdealers/buy-resell/products/digital-receipt.md#evaluation-of-retrievals-of-digital-receipts)

# Germany requirements

Expand Down
80 changes: 40 additions & 40 deletions ...ators/middleware-doc/digital-receipt/Instore-App/digital-receipt-instore-app.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,12 +60,12 @@ In store, the merchant collects items and processes the payment or checkout. The

![InStore_App_show_receipt](./images/InStore_App_show_receipt.png)

| Number | Description |
| ------------- | ------------- |
| 1 | Receipt number (ft5C43F#357749), date and receipt amount |
| 2 | QR-Code to https digital receipt document |
| 3 | `Accept button` |
| 4 | `Print button` |
| Number | Description |
|--------|----------------------------------------------------------|
| 1 | Receipt number (ft5C43F#357749), date and receipt amount |
| 2 | QR-Code to https digital receipt document |
| 3 | `Accept button` |
| 4 | `Print button` |

## Download the InStore App

Expand All @@ -91,7 +91,7 @@ This high level overview shows you the steps on how to implement and configure t

Please visit following link to see the configuration steps for the master data:

https://docs.fiskaltrust.cloud/de/docs/posdealers/buy-resell/products/digital-receipt#introduction
[Digital Receipt Introduction](../../../../posdealers/buy-resell/products/digital-receipt.md#introduction)

# Implementation

Expand Down Expand Up @@ -414,40 +414,40 @@ To proceed with the configuration, login to your fiskaltrust.Portal account firs

### Queue

| Step | Description |
| ------------- | ------------- |
| 1 | Navigate to the configuration section and go to Queue |
| 2 | Configure Queue |
| 3 | Copy the URLs to your local machine (Required for CashBox configuration later) |
| 4 | For all countries: Change port to the next free port (+1) and <br/> a. if no suffix exists after the port: add the suffix "/name_queue" to the URL ("name" can be freely chosen) <br/> b. if suffix already exists: add the suffix "_queue" to the URL |
| 5 | Germany & France only: Change grpc port to the next free port (if port is free no need to go up to the next free port) and add the suffix "/name_queue" to the URL ("name" can be freely chosen) |
| 6 | Save changes |
| Step | Description |
|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 1 | Navigate to the configuration section and go to Queue |
| 2 | Configure Queue |
| 3 | Copy the URLs to your local machine (Required for CashBox configuration later) |
| 4 | For all countries: Change port to the next free port (+1) and <br/> a. if no suffix exists after the port: add the suffix "/name_queue" to the URL ("name" can be freely chosen) <br/> b. if suffix already exists: add the suffix "_queue" to the URL |
| 5 | Germany & France only: Change grpc port to the next free port (if port is free no need to go up to the next free port) and add the suffix "/name_queue" to the URL ("name" can be freely chosen) |
| 6 | Save changes |

### Helper

| Step | Description |
| ------------- | ------------- |
| 1 | Navigate to Helper |
| 2 | Create new helper |
| 3 | Add description |
| 4 | Select package name "fiskaltrust.service.helper.posapi" |
| 5 | Select latest package version |
| 6 | Select the outlet of CashBox |
| 7 | Save configuration |
| 8 | Klick configure helper |
| 9 | All Counties: Insert the previously saved Queue URLs to the Helper URLs and add the suffix "/name" to the URL (analogue to the naming in queue configuration). Germany & France only: Add also GRPC URL with next free port and add the suffix "/name" to the URL (analogue to the naming in queue configuration). |
| 10 | Save configuration and close |
| Step | Description |
|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 1 | Navigate to Helper |
| 2 | Create new helper |
| 3 | Add description |
| 4 | Select package name "fiskaltrust.service.helper.posapi" |
| 5 | Select latest package version |
| 6 | Select the outlet of CashBox |
| 7 | Save configuration |
| 8 | Klick configure helper |
| 9 | All Counties: Insert the previously saved Queue URLs to the Helper URLs and add the suffix "/name" to the URL (analogue to the naming in queue configuration). Germany & France only: Add also GRPC URL with next free port and add the suffix "/name" to the URL (analogue to the naming in queue configuration). |
| 10 | Save configuration and close |

### CashBox

| Step | Description |
| ------------- | ------------- |
| 1 | Navigate to CashBox |
| 2 | Select your CashBox and click edit by list |
| 3 | Navigate to Helpers |
| 4 | Activate the POS API Helper |
| 5 | Save configuration |
| 6 | Klick rebuild configuration |
| Step | Description |
|------|--------------------------------------------|
| 1 | Navigate to CashBox |
| 2 | Select your CashBox and click edit by list |
| 3 | Navigate to Helpers |
| 4 | Activate the POS API Helper |
| 5 | Save configuration |
| 6 | Klick rebuild configuration |

### Restart

Expand All @@ -457,8 +457,8 @@ Restart the fiskaltrust.Middleware to apply the changes.

After installing the InStore App on your Android device, establishing a connection with your preferred CashBox is essential. Here's how:

| Step | Description |
| ------------- | ------------- |
| 1 | Log in to your fiskaltrust.Portal account and proceed to the CashBox you want to pair with the InStore App. |
| 2 | Extend the overview of the CashBox. Klick `unhide` to generate a new, temporary pairing pin.<br/>![fiskaltrust.Portal_pairing_pin](./images/fiskaltrust.Portal_pairing_pin.png) The pairing pin is valid for five minutes. After the pin expired, you need to generate a new pin, by clicking `unhide` to generate a new pin. |
| 3 | ![InStore_App_pairing_pin](./images/InStore_App_pair_device.jpg) <br/> Enter the four-digit pin into your InStore App, confirm the connection by clicking `Pair`. You can pair multiple InStore App installations with one CashBox. To open the paring to CashBox mask or to pair with a different CashBox, press the touchscreen one second. |
| Step | Description |
|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 1 | Log in to your fiskaltrust.Portal account and proceed to the CashBox you want to pair with the InStore App. |
| 2 | Extend the overview of the CashBox. Klick `unhide` to generate a new, temporary pairing pin.<br/>![fiskaltrust.Portal_pairing_pin](./images/fiskaltrust.Portal_pairing_pin.png) The pairing pin is valid for five minutes. After the pin expired, you need to generate a new pin, by clicking `unhide` to generate a new pin. |
| 3 | ![InStore_App_pairing_pin](./images/InStore_App_pair_device.jpg) <br/> Enter the four-digit pin into your InStore App, confirm the connection by clicking `Pair`. You can pair multiple InStore App installations with one CashBox. To open the paring to CashBox mask or to pair with a different CashBox, press the touchscreen one second. |
Loading
Loading