Tse connection error

Fiscalization in Germany requires the use of a "certified technical security device" (TSE or TSS in the english version of the ordinance). If hardware TSEs are used, the error message "Tse connection error." may be returned after createDocument.

Possible scenarios:

TSE not connected

TSE is not connected to the cash register (to the system on which the RetailForce Middleware is installed).

Troubleshooting:

Connect the TSE to the system.

TSE connected - test shows "OK

The error is returned, but the TSE is connected to the system, also a self-test

• POST /api/v1/management/germany/tse/{tseSerial}/selftest returns
• "200 - Success",

as does a connection test:

• PUT /api/v1/management/germany/{clientId}/tse/connectTest,
• "200 - Success".

Possible Cause:

The limit of open transactions has been reached! Due to a TSE requirement by the BSI (German Federal Office for Information Security), TSEs must limit the number of transactions that can be open at the same time.

• Swissbit hardware TSE can manage a maximum of 512,
• fiskaly Cloud TSE 2,000 open transactions.

These are transactions that were started with createDocument but were not completed correctly later (with storeDocument or cancelDocument). This can occur, for example, if the POS system crashes after a createDocument and has not "remembered" that there are still open transactions.

The number of open transactions can be read out with the following endpoint:

• GET /api/v1/management/germany/tse

Open transactions are displayed in the response in the field "startedTransactions":

[
   {
      ...
      "startedTransactions": 512,
      "maxStartedTransactions": 512,
      "createdSignatures": 2238,
      "maxSignatures": 20000000,
      ...
   }
]

Troubleshooting:

To rectify the error or to enable the TSE to accept documents ("receipts") for processing again, the open transactions must be closed.

To do this, proceed as follows.

Option 1:

Using the

• GET /api/v1/management/germany/{clientId}/tse/listTransactions,

endpoint, the fiscalDocumentNumbers of open transactions are returned in packets.

Example:

[
   45,
   1,
   2,
   3,
   4,
   5,
   6,
   7
]

The transactions retrieved via listTransactions (=fiscalDocumentNumber) must now, according to the real situation, be closed either with:

• POST /api/v1/transactions/storeDocument or
• POST /api/v1/transactions/cancelDocument

Use POST /api/v1/transactions/storeDocument (as usual) to complete the document when a sale has been made and POST /api/v1/transactions/cancelDocument to cancel the transaction (without a successful sale).

Option 2:

The

• DELETE /api/v1/management/germany/{clientId}/tse/listTransactions

endpoint can be used to close all open TSE transactions at once. Please be sure to follow the instructions above regarding document cancellations before using this endpoint! After closing all open transactions, the TSE will again accept and process documents.