Skip to main content

Service Status: ftState

These are the supported statuses for the ftState field returned in the response of the middleware. The ftState can be combined through the logic operator "OR". For example 0x4154_2000_0000_0200 (MonthlyClosing due) and 0x4154_2000_0000_0002 combined through OR results in 0x4154_2000_0000_0202 being returned by the middleware.

Format

CCCC_vlll_gggg_gggg

v - version

version 2

gggg_gggg - global tagging/flag

ValueDescriptionMiddleware Version
0000_0001Security Mechanism is out of Operation
Implementation mandatory: Queue is not started or already stopped.
1.3.45
0000_0002SCU (Signature Creation Unit) temporary out of service
Implementation mandatory: For at least one receipt, it was not possible to receive the signature from an allocated SCU, therefore the security mechanism has been put into "signature creation device out of service" mode. Regardless of whether an allocated SCU is available again or not, the mode remains in place until a ZeroReceipt cleans up the state and takes the market specific action required.
1.3.45
0000_0004SCU (Signature Creation Unit) permanently out of service
Implementation mandatory: The status "SSCD temporary out of service" was activated more than 48h ago. Thus a FinanzOnline notification has been generated. For conduct and termination of this mode, see "SSCD temporary out of service".
1.3.45
0000_0008Deferred Queue Mode / Late Signing Mode is active
Implementation mandatory: When the cash register doesn’t reach the queue, it queues up the receipt requests while continuing to do business. Also, with a major failure of the cash register or a power outage, handwritten paper receipts are queued up while continuing to do business. After getting back to a full functional state, these queued-up ReceiptRequests are sent to the queue, having the original cbReceiptMoment of the business case and ReceiptCase tagged/flagged with 0001 (Deferred Queue / Late Signing) or 0008 (Handwritten).
A result of this is a marker within the ftState, which can be resolved via ZeroReceipt. The reason for the marker is a mismatch between processed time along the receipt chain and a manual event to clean up the state and maybe notify 3rd parties of an outage.
1.3.45
0000_0200MonthlyClosing due
Optional: If the latest monthly has not been performed, the service will signal this. This status does not impact the signature conduct of the service; it is merely an indicative notification.
1.3.45
0000_0400AnnualClosing due
Optional: If the latest annual closing has not been performed, the service will signal this. This status does not impact the signature conduct of the service; it is merely an indicative notification.
1.3.45
0000_0040Message Pending
Optional: Middleware/Queue is a headless background service, but there are situations where communication with the cashier/operator or the cash register is necessary. For example, if the last daily closing was missed or if a special condition related to the signature creation unit or service happened. This is the moment when the message pending flag is set by the middleware, which should be signalled to the cashier by the POS system. By executing a ZeroReceipt, the cashier can read the message or instruction on the printed or displayed receipt.
Related to local regulations, this receipt may be stored/archived with/for bookkeeping purposes; if this is the case, this is also visualized.
1.3.45
0000_0080Backup SSCD in use
Optional: The receipt was signed by a signature creation unit configured for backup use.
1.3.45
EEEE_EEEEError
Implementation mandatory: Something went wrong while processing the last request. QueueItem exists but didn’t reach the state of a ReceiptItem and didn’t consume a ftReceiptNumber within the chain. Error reason is shown within the responded ftSignatureItems.
This happens, for example, if the ReceiptCase is not recognized or is wrong.
1.3.45
FFFF_FFFFFail
Implementation mandatory: Something went wrong while processing the last request, and nothing persisted within the Queue. Fail reason is shown within the responded ftSignatureItems.
This happens, for example, when the flag ReceiptRequest is used after a communication outage, and no properly processed item is found.
1.3.45

llll -local flags

cba c=reserved; b=reporting; a=scu related

ValueDescriptionMiddleware Version