As we are part of the logical cash register by providing the DEP7, turnover counter, receipt numbers, etc. for you this can be viewed as an outage of the cash register itself. Therefore the following scenario applies:
- Try to fiscalize the receipt
- Fiscalization failed (e.g. 5xx returned, unreachable, ...)
- Store the request payload including the UUID of the receipt (!)
- Create a receipt for your customer that omits the fiscal receipt number and fiscal cash register identifier. Instead, print
Sicherheitseinrichtung ausgefallenon the receipt. In addition to that, a QR code containing this information should be printed. - Make sure you keep a copy of that receipt.
Once you can reach the SIGN AT solution again, replay the failed requests ("Nacherfassung") with the receipt UUID of the original request. This assures that you do not fiscalize receipts twice by accident.
As it is not unlikely in such a scenario that a lot of receipts queue up while there are new transactions happening, you can replay the requests at the end of a shift for example.