Operation Server

Operation Server is the main server component of
Digital Bank Platform, the transactional core of
the platform. The main roles of the server are:
 • Operation fee calculation
 • Transaction limits management
 • Managing front-end applications scenarios
 • Transactions templates storage
 • Payments routing
 • Managing operations with the service providers
 • Platform resources localization
Operation Server

Managing accounts

For the operations processed by the Operation Server the
corresponding booking entries are created, which are
then uploaded into a Bank’s accounting system. The
special module of Operation Server BCIT (Bank Core
Integration Toolkit) is responsible for this action.
Booking entries can be created for payments and transfers,
for encashments, for payee rolls (aggregated transactions)
and for agent rolls. The booking entries are recorded in the
accounts, which need to be created when deploying the
system. For each account, a balance can be calculated.
Creating and uploading of booking entries is carried out
according to a chart of accounts, which can be set up or
customized on the bank side.
Managing accounts
Managing accounts

Managing points

Points of sales are key business objects of Operation Server.
Each operation can only be initiated on behalf of a registered
point. The points differ in their types: they may be registered
as cash desks, kiosks, ATMs, Internet bank points, mobile
bank points and other. The points are separated by ownership;
each point is either an own bank’s point, or belongs to a
certain agent’s network. The Server allows you to add, edit and
block the registered points of sale. You can group the points if
needed (for example, by region property). Different types of
points of sales can be processed in different ways.
Managing points
Managing points


The Operation Server is responsible for storing the transaction
templates. The service is available for all front-end applications
(the fronts may have their specificities).
The transaction templates can be stored in the Operation
Server database or in a third-party data source.
Transactions templates
Transactions templates

Transaction limits

The server allows you to set transaction limits depending
on currency, payment tool, type of a point, type of a
service and other parameters. Checking the limits is
performed online when processing the transaction.
Transaction limits
Transaction limits

Operation service

Transaction is the main business function of the Operation
Server. Payment and Operation Service supports the
transactions. The registration and execution of the operation,
search and cancelation of operations, re-execution or
adjustment of operations can be performed with the help of
this service. During the operation (depending on its parameters)
a chain of handlers can be started. Each handler can perform an
action, for example, debiting or crediting an account, checking
the data, sending a request to an external system and so on.
Based on the received response processing of the operation can
be continued or stopped with the status “rejected”.
The transaction handling mechanism allows you to customize
processing of any transaction types.
Operation service
Operation service

Fee service

Commissions for all types of transactions are calculated
online and can be shown to users before they confirm
the transaction. The calculation of fee can contain
complex formulas and depends on many parameters:
the amount of payment, the recipient of the transaction,
the payment instrument, the time of the transaction and
other factors. In certain cases, fee calculation can be
performed by specially developed plugin. The service also
allows you to manage fee calculation settings – for
example, specify the start date to put the new
fee calculation rules into effect.
Fee service
Fee service

Managing providers

For each transaction type a service, a payee and a gateway
should be specified in the system. Provider Management
Service operates with these business objects in the system.
You can create, edit or block the registered objects. Data
exchange with the final recipient of the operation is
performed via the gateway by specially designed protocol.
Managing providers
Managing providers


Payment to a service provider can follow the particular route
depending on a certain business requirements. Routing is
supported by the relevant plugins. The logic of payment routing
is built according to customer’s specifications in a particular
project. The standard routing cases are availability, amount
of commission charged by service provider and some other.


The service allows you to localize correctly the static interface
elements and front-end applications work scenarios, as well
as all parameters (including the dynamic ones) of business
objects in the system. All localization settings can be
specified in Operation Studio. Full localization of multi-state
scripts is supported. Therefore, language support in front-end
applications is limited only by the capabilities of the back
office applications.

Scripts management

The settings of the operations scenarios in front-end
applications (ATM, mobile applications, Internet bank,
payment front and others) are specified in Operation
Studio. The data for multi-state operation, which need
to be displayed in user interface, may be requested from
the end user operator. In this case Operation Server acts
as a proxy. The ability to configure complex nonlinear
scenarios (where branching is based on input parameters)
is supported. Such scenarios are required for composite
operations such as an opening of deposit or order a card.
Scripts management
Scripts management

Cash management

This functionality works in projects, where managing software
for ATMs is involved. Operation Server can control the recycler,
support the functions of defining the set of banknotes and ATM
cassettes for cash withdrawal and other. If necessary, an external
cash management system can be used.
Cash management
Cash management


High efficiency

High efficiency

All components of Operation Server can be scaled horizontally. Always On cluster can be applied to scale the database. Transaction processing for its most part occurs in RAM; database is only used for final recording. System characteristics have been tested in real projects with high load.



The Operation Server provides many extension points and a number of SDK. There are SDK for implementing gateways to service providers, preprocess handlers, routing plugins, ability to host third-party applications, customizing the unloading of booking entries into accounting systems, Operation Studio interface expanding plugins.

Multichannel and omnichannel platform

Multichannel and omnichannel platform

The Operation Server allows you to perform transactions via any service channel. Transaction stages are preserved and can be later continued in another service channel.

Any kind of transactions

Any kind of transactions

  • • Payments
  • • Transfers
  • • Nonfinancial operations

Demo access to back-office

Our employees usually demonstrate the work of back-office applications remotely. Demonstration the functionality of different system components can be performed when the agreement about technical terms and scenarios has been reached. Technical documentation can be provided as well. To grant access, please, fill in the form. Our manager will contact you.