Cloud fiscalization
by PayMob

Core 1

Customer, point, user, and cash
register management module
Module for managing
personal customer accounts
Tariff management
Tax service queue
monitoring module
Fiscal document
review module

Core 2

legal entities
cash registers
Managing users
and roles
Making requests for
Connecting cash registers
Cash register
server node

API registration of
fiscal documents
API registration of
new cash registers
API reception of
operation queue status
API closing of the
fiscal memory devic
API receipt reception
and verification
The key user of the system is the
owner who has a certain number of
legal entities, e.g. companies, and a
certain number of users with
distributed roles.

Connecting customers to the system
requires a conclusion of an
agreement performed by filling out
the agreement details in the admin
dashboard. Once the agreement is
created, it is possible to set up cash
registers in the system.

The system can determine a cash
register upon the first request and
fill out the details without user
participation. Some cash register
details, such as the serial number,
the number of the fiscal memory
device, and the enterprise number
of the register can also be added
manually. Each cash register is first
linked to the point specified in the

This section includes the data transmitted from cash registers
and sent over to the tax authorities accordingly, such aseceipts/accountable forms, correction invoices created in case of a refund or a reissuance, shift opening and closing reports, reports on the current status of settlements, details of the cash register equipment registration and re-registration, and the fiscal memory device closure detail.
The monitoring section displays the queue of operations and fiscal documents that are sent over to the Tax Service. Documents are grouped by type, types of documents are grouped by status. The details can be provided for all operations or for the past six hours. Separate graphs display the number of operations performed over the past 7 days, the average operation time, the average number of active cash register equipment units, and the average number of documents processed at every point.

Fiscal module
production process

The setup of the functional software (applet) that
processes and transmits fiscal data
Assignment of a unique number, generation of a
public and a private key and transmission of the public
key to the memory device (during the pilot stage of the
project, to a database; during the later stages,
to a hardware security module). The private key is
only stored at the fiscal memory device
Application of the visual data, such as the
identification number of the module, a matching bar
code, logos, and other necessary visual data
A processed fiscal module features a unique ID. The
details of such an ID are stored in the Fiscal Data
Processing System and at the Tax Service.

Fiscal module

It is suggested that smart cards and USB keys are to be used as a fiscal module.

The fiscal module is equipped with the Infineon SLE77CLFX2400PM controller or with a controller compatible with a newer version. The card should support the T=0 and T=1 communication protocols and the following ryptographic algorithms: GOST 28147-89, 3DES, AES, RSA, SНA-1, SНA-224, SНA-256, ECC over GF(p), Random number generation, and encryption services

During the pilot stage of the project, Java Card industry standards will be used.

The fiscal module is factorysupplied, which guarantees that there will be
no inner or visible identification data. Depending on the arrangements made, the device may contain the software installed by the manufacturer.
The software can also be installed during the initialization of the fiscal module

Data stored
The volume and number of overall transactions performed for each transaction type over the whole activity period of a fiscal module
The number and total sum of transactions of each type performed within the scope of each Z Report
The limited number of the Z Reports that have not been sent. This parameter is configured depending on the corresponding requirements
Detailed information about every transaction should be stored at a fiscal module until the reception of a transaction confirmation from the Fiscal Data Processing System


Activate card

The second stage of fiscal module activation
implies the reception of the Fiscal Data
Processing System response by the cash
register and transmitting it to the fiscal module
applet where it is used as one of the parameters
of the ACTIVATE CARD command. As a result
of this command, the key received from the
server is compared to the key stored at the
fiscal module, and if they coincide, the fiscal
module obtains the Active status.

Deactivate card

This command is used when it is
necessary to deactivate the fiscal
module. The deactivation process
features a number of restrictions;
one of them implies that it is
necessary to send all the Z Reports
stored at the applet that have not
been sent yet to the Fiscal Data
Processing System.

Request card activate

This command matches the first stage of fiscal
module activation and implies the generation
of a cryptogram. Such a cryptogram should be
transmitted to the cash register that, in turn,
sends it to the Fiscal Data Processing System.

Get last transaction

This command displays the details
of the last transaction that has
been registered at the Fiscal Data
Processing System. This command
is used if it is not confirmed that the
transaction has been successful due
to technical reasons

Get module info

This command displays the status
of all variables at the time of request.

Get batch

This command displays the contents of a
particular Z Report.

Register transaction

The cash register software uses a
total sum. This parameter can be
configured and depends on the
requirements of the tax regulations.
The cash register summons the
Register transaction function
in the fiscal module and transmits
the type of transaction, its volume,
date, and time. If the transaction is
registered successfully, the fiscal
module displays its unique number,
the unique growing transaction
number (the number grows for any

transaction that induces a change in
the status of the fiscal module),
the growing transaction number of
this type, the number of the Z Report
within the scope of which the
transaction is performed, other
supplementary details, and the digital
signature. The possibility to configure
the list of parameters and their
indispensability depending on the
business organization type of the
taxpayer has been implemented.

Close batch

This command closes the Z Report in
the fiscal module applet. When a Z
report is closed, the fiscal module
records the information about all the
transactions that have been
performed over the corresponding
period. The information is confirmed
by a digital signature.

Get batch

This command is sent by the cash
register to the fiscal module applet to
obtain the Z Report details that have
been signed by a key to send them to
the Tax Service afterwards.

Register registered

Once a Z Report is sent to the Fiscal
Data Processing System, a message
displaying the result of the
registration is sent back to the cash
register. This message is transmitted
from the cash register to the fiscal
module applet as a parameter of the
command in question to verify that
the Z Report has been registered

The fiscal module
verifies the validity of the digital
signature and records that the data
has been transmitted to the central
security module successfully, deletes
this report from its memory, and
resets the counter of the reports that
have not been sent.

Hi there 👋

How can I help you?