Skip to content
SiopKA is awaiting cash register type approval by the President of the Central Office of Measures (GUM). Until then it runs as a pilot on the Ministry of Finance test environment. Details

Security

Who can reach the register, the documents and your company data

Security in SiopKA is a few simple rules applied everywhere: keys never leave the device, every connection has an identity, and only the register itself ever issues a document.

The register

How is the register protected on the phone?

Documents are signed, connections to the MF are encrypted with the register's certificate, and the program changes only through a controlled update.

  • Connections to the MF use mutual TLS authentication with the register's certificate; the MF addresses are fixed in the program and cannot be changed from outside.
  • KSeF certificate keys live in the Android Keystore. The panel and the API show only the certificate status, never the secret material.
  • Program updates come only from the producer, are verified before installation, installed after the daily report and recorded as a register event, with a rollback on failure.
  • The cashier PIN is entered only in the register. Cooperating apps ask for a cashier session but never see the PIN.
Apps and stations

Who can issue a document in your register?

Only someone you have explicitly allowed, with their own key and their own scope of permissions.

  • An app on the same phone is identified by Android itself: package, identifier and signing certificate, not by data in the request.
  • A remote station has its own key and signs every request. The server checks it first, then the register itself, which can block it.
  • A SiopTAK installation gets its own key when registered with a code from the panel; the owner can revoke it with one click.
  • The local register API works only within the phone, over an encrypted connection, with no network access.
Panel and website

How do we protect the panel and this website?

The panel keeps tokens on the server, and the website loads no third-party scripts.

  • Tokens stay on the server: the browser never receives the panel access token.
  • Company isolation: every query is limited to the signed-in user's company, and actions are recorded in the audit log.
  • The content security policy allows only scripts from our own domain; payment runs in the payment operator's frame.
  • Forms are protected against submission from another site, and resending the same attempt does not create a second request.
Reporting

Found a vulnerability?

Write through the contact form with the topic "Technical support". Do not include passwords, keys or other people's data; we will get back to you to agree the details.

Start with your first receipt

Buy a licence in the shop and we will agree the installation of the pilot version with you after the purchase. You can also book a free demo: we will show the register, the taxi app and the panel on your own case.

Necessary cookies remember your appearance and language choice, protect forms and keep the panel session. They do not need consent, because without them the site cannot work the way you ask it to.

Necessary

Always on: appearance, language, cookie choice, form protection, panel session.

This site uses no analytics or advertising cookies and loads no third-party tracking tools.

Read the cookie policy