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

Integrations and API

Connect your system to the register

SiopKA has a general register API. Your sales app, booking system or dispatch centre issues documents through the customer's register, without building its own fiscal register.

Two routes

How does your system connect to the register?

On the same phone or as a remote station. Both routes end in the same register queue.

Local register API 1.3

An app on the same Android phone. The request goes through Android (package, identifier, signing certificate), the cashier session is approved on the register screen, and the encrypted connection stays within the phone.

Remote stations 1.0

A POS, tablet or partner server sends signed requests through our backend to the company register. Pairing in the panel with a code or QR code, two-step authorisation.

Permissions

What does an integrator get access to?

To what the register administrator approves, split into scopes. A selection of the most used ones:

Selected scopes of the local register API 1.3
ScopeWhat it allows
status.readReading the register's readiness, licence and capabilities.
session.requestRequesting a cashier session, approved with a PIN on the register screen.
catalog.readReading VAT rates and the goods catalogue.
receipts.createIssuing a receipt in one request.
sales.openTwo-step sales: open, operate, approve or cancel.
sales.taxiStarting and ending a taxi ride, only for apps declared in the register.
operations.readThe state of your own operations and sales by request id.
documents.readPages of the preserved documents of your own sales as images.
output.printPrinting a document or sending it to Siop Printer.
reports.daily.generateThe daily report on demand.
invoices.requestAn invoice for your own receipt.
payments.terminalPayment on the register's payment terminal; terminal integration is outside the pilot and the register reports it as unavailable.
Rules

Which rules apply to every integration?

The same ones that protect the register from duplicate receipts and lost documents.

  • Idempotency: every request has its own id. Repeating the same request returns the same result, not a second receipt.
  • Unknown result: when the answer does not arrive, read the operation state by its id first, then decide whether to retry.
  • Clear refusals: known refusals have their own codes, such as a changed VAT rate or a missing catalogue, before anything is recorded.
  • Cashier from the session: the cashier comes from the approved register session, never from the request body.
  • One central register cannot replace many: a register serves the cashiers of one taxpayer, not many independent payment points or many taxis.
Getting started

How do I start an integration?

With a conversation about your scenario. We share the contract description after the conversation and run the trials together in the MF TEST environment.

  1. Describe the scenarioIndustry, integration type (local or remote station), documents and behaviour after a lost connection.
  2. You receive the contractA description of routes, scopes, refusal codes and examples, with the contract version.
  3. We test together in the MF TEST environmentThe full document path without real sales, including failure and resume scenarios.

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