Germany TSE Integration – POS System Configuration
Wolvox 8 - TSE integration for Germany is provided through the Fiskaltrust Middleware solution. In order to use AKINSOFT - Fiskaltrust TSE integration, our users must have a 'Cash Register - Pos - Scale' license which is one of the modules of our Wolvox ERP program.
First of all, we register our company via this link on the fiskaltrust portal or via the invitation link to be sent by your dealer.
After the registration process, the cash register configuration in the portal basically consists of 6 steps.
1. Create the SCU configuration
Click Signature creation unit in the Configuration section of the Fiskaltrust portal. A list of previously created SCUs will appear in this field.
Press the "+ Create" button to add a new one. This will open the area where you can enter the SCU information.
- Enter the SCU name.
- Select the relevant module depending on TSE. (Swissbit in the example)
- The latest version is automatically displayed in the Package version section. Unless otherwise recommended by Akınsoft, it should be the most up-to-date version.
- Select the outlet. By default, your company's main address will be selected here. If you are installing for your branches, select the relevant branch.
- Click ''Save'' button.
Now the SCU has been created and a form will be opened where we can enter detailed information. This form may request different information depending on the module we have chosen. In our example, Device Path should be selected for Swissbit. Different information may be requested for another module.
- Enter the Device Path. (i.e. E: in our case.)
- Now specify how and where the SCU will be accessible for a Queue. First press the corresponding button for the communication type (i.e. grpc) and enter the path (i.e. Localhost:1401).
- Press "Save and close" to save the data and to return to the list.
In the list we can now see that our SCU configuration has been successfully created:
2. Create the Queue configuration
In this step we will create the Queue configuration. To do this, we go to the "Configuration → Queue" field.
Now press the "+ Create new" button.
In the new form;
- Enter the name of the Queue here (e.g. "TEST QUEUE").
- Select how the data should be persisted (e.g. SQLite database).
- The latest package version is automatically selected.
- Enter the serial number of your cash register in the "Cashbox Identification" field. This field can also be filled in automatically by the system if you wish. Please note that it must be a unique number with a maximum length of 20 characters. The cash register serial number registered here will then be recorded as ClientID in TSE to send signature to the cash register.
- Select the outlet. By default it will bring up the main outlet.
- Click ''Save'' button.
Queue has been created and we see the second configuration form. This form changes depending on the database we selected earlier. In the example we do not need to do anything for the SQLite database because it is automatically created by fiskaltrust.Middleware.
- Specify how to access the Queue from the POS System. First, click on the relevant option for the communication type (i.e, http(REST), after that specify the path (i.e, localhost:1200/fiskaltrust)
- Press "Save and close" to save the information and to return to the list.
In the list we can now see that our Queue configuration has been successfully created:
3. Create Cashbox
After creating SCU and Queue, the next step is to create Cashbox. To do this, go to the "Configuration → Cashbox" field. If any, previously created Cashboxes will be listed in this field.
Click the "+ Add" button to create a new one. A form will open for you to enter your cashbox information.
- Enter the name of the CashBox here (e.g. "TEST CASHBOX")
- Enter the outlet, by default the main outlet will be preselected automatically
- Press "Save" to save the data and to return to the list.
In the list we can now see that our new CashBox has been successfully created:
4. Fill the Cashbox
After creating the CashBox, it is to be filled next. In our example, we want to put the previously created Queue configuration and the SCU configuration into the CashBox. Here we can see that it is currently still empty.
Click on the "Edit by list" button to fill the Cashbox we just created. In this way, the configurations we have created before will be listed.
From this list we can select the configurations we want to add to Cashbox.
When we check again after making this selection and saving, we see that Queue and SCU are now included in Cashbox.
5. Connect the Queue with the SCU
As described above, we need to tell the Queue which SCU to use to sign the data. So we have to "connect" the Queue with the SCU. In our case, the Queue and SCU are in the same CashBox. Nevertheless, we have to create the connection. To do this, we press the "Connect" button in the expanded list entry of the CashBox, which is displayed to the right of the Queue:
A popup appears with the available SCUs. From this list we can now select our previously created SCU, save and close the popup.
The queue now knows with which SCU it has to communicate and where the SCU can be reached.
6. Publish the CashBox (rebuild configuration)
The last step is to publish the created CashBox. This is done with the "Rebuild configuration" button available in the list line of the CashBox.
This makes the CashBox available for download as a JSON file. This JSON configuration file can later be downloaded by a fiskaltrust.Middleware instance and used for initial initialization or for an update. In case of an update, for example update of the SCU package version due to a change in the law, the change is only made available in the CashBox after the "Rebuild configuration" button has been pressed. If the fiskaltrust.Middleware instance to which this CashBox is assigned is then restarted, it loads the new configuration and updates itself automatically, e.g. by downloading and using the new package.
Start and Test the Service
To test the service, meaning a fiskaltrust.Middleware instance, we download the so-called "Launcher". We can do this in the list entry of the previously created CashBox. To do this, press the "Download .NET Launcher" button. The point is if the system will work offline you must download Offline Launcher via the yellow button right next to the blue button. For online systems, please use the first blue ''Download .NET Launcher'' button.
You will receive a zip compressed folder that you can unzip on the cash register. Unzip the zip file.
We can use the test.cmd to test the service. Before starting this file, add the -verbosity=Debug parameter, leaving a space at the end of the second line. So we can see the log messages directly in the console and act accordingly.
Save and run as administrator:
A console appears in which the fiskaltrust.Middleware instance is started. We can see here what exactly happens at startup and make appropriate corrections (e.g. in the CashBox or in the connection of the TSE) in case of any errors.
Wolvox 8 POS Settings
In AKINSOFT Wolvox Market Automation program, select Fiskaltrust settings from the New Generation ÖKC (General) section. On the new screen enter the Cashbox ID, Base URL and Additional URL information according to the relevant Cashbox that we have created on the Fiskaltrust portal. When you click the ''Close'' button, the settings on Wolvox will be completed.
Initialization of the fiskaltrust.Middleware instance via an initial-operation receipt
Submit an "initial operation receipt" after test requests. You can do this through our Wolvox Barcode Sales or Restaurant program. The initial operation receipt enables fiskaltrust.Middleware to be started, registers the Queue as a client in TSE and starts the TSE if not yet started.
In the response and in the console we can now see that our Queue has been registered as a client in the TSE.
Send a pos-receipt
We can then send a receipt through our Wolvox program to process a purchase.
The fiskaltrust.Middleware processes the request and sends back a response containing important receipt data, including the required signatures. If successful, these signatures are printed on the receipt by the POS-System.
Check connection with the fiskaltrust.Cloud
In the fiskaltrust.Portal we can see the above submitted request and the resulting receipt, because they are uploaded via the Helipad Helper every 5 minutes. To do this, go to "Configuration->Queue" and press the "ReceiptJournal" button in the list entry of the Queue.
An overview of the processed receipt requests appears:
If the receipts do not appear here, it is possible that the communication of the fiskaltrust.Middleware with the server did not work. In this case, first check whether 5 minutes have already passed since the requests were sent. If this is the case, please check the log messages in the console. It may be that you have to release the corresponding firewall ports first.
Now press the button with the eye symbol in the line with the previously sent pos-receipt request (see above). You can now view an exemplary representation of the receipt. In addition, the concrete request and the answer to the POS-System are displayed: