SpecificationServer in Digital Banking Platform is responsible
for providing personalized services to a Bank’s
customers. The set of basic services includes
banking services, geo-services, operation hub,
timeline service, notification service, currency
transactions service and others. It supports
transformation, data aggregation and caching.
DBP functionality can be extended by connecting
micro services to the platform. The functionality
of all services is available via the platform API
and can be used by all front-end applications.
Integration with all bank’s back-office systems
is performed by means of standardized internal
Banking service is responsible for providing
information about client’s banking products
– cards, accounts, loans, deposits, e-wallets
and so on. Each product has its own
expandable set of parameters. If necessary,
the product information can be requested in
several systems, and then the data can be
combined and sent to front-end applications.
Operation serviceOperation service is responsible for making
payments, transfers and performing
nonfinancial operations for authenticated
clients. Operation Hub is used as a transaction
core of the system. The settings of payment and
non-payment scenarios are performed in
Operation Studio (single configuration point).
Configured work scenarios are used by all
Geo servicesGeo services are non-personalized services
related to the determination of the address
by coordinates, the location of the bank’s
points, the search of various types of the
points, the definition of the home region,
the location of the client by its IP address
and other similar services.
TimelineThe service allows combining all client’s events
into one timeline. It shows debit and income
transactions, messages from the Bank (for
example, reminders about next payment),
personal offers, application statuses of
nonfinancial operations and other events
related to the client. Each event can be viewed
more detailed or obtained as a document (for
example, check for a transaction). Full-text
search and filtering by parameters are available.
Promo serviceThe DBP server allows you to include various content
into front-end applications. It can be a simple banner,
a clickable banner (which runs a customer script) or a
targeted offer. Information about the content viewing,
user actions and other related data can be logged for
analytic purposes. Functionality of the promo service
can be used for advertising and clients informing. Cloud
AdNet service or a back-office bank’s system (if
integrated into the system) can function as a source of
content and data.
Micro servicesDBP functionality can be extended by connecting
micro services to the platform. By adding micro-
services the additional functional of any complexity
level can be implemented. Thanks to this architecture
the specific services of particular clients are not
included the base set of the platform functions. This
approach simplifies the implementation and support
of additional custom functionality. Micro services can
be developed by clients themselves (we organize the
training courses). Using micro services architecture
considerably reduces the costs of testing while adding
a new functionality.
Caching dataThe DBP server is designed to work in highly loaded
systems with millions users. Caching is used to
support horizontal scaling of the system and to
optimize the requests to internal bank systems.
NoSQL databases are used for storing the cached data.
In addition, back-office systems can manage the data
in the platform cache using a special Cash Control
API (for example, update the cache data when the
account balance is changed). This results in optimizing
access time to almost all users’ data.
IntegrationIn addition to common external Platform API, which
is used by front-end applications, each service of DBP
server has internal SOAP integration API. It allows
you to integrate platform services with the bank’s back
-office system. This SOAP API is standardized. It can
be used for integration by both platform developers
and employees on the client side. To develop
integration adapters, you need to take a training course.
To extend basic functionality of the platform, you can
use micro services that can be integrated into back-
office systems in the similar way.
High load capacity
The DBP server is designed so it is able to support scaling within the scope of any projects.
Micro service architecture
Expanding base DBP functionality is available by adding micro services. Front-end applications work with integrated Platform APIm.
Platform API is developed in compliance with open API concepts. Any third-party application can be easily integrated.
The DBP server supports a standardized internal SOAP API that allows integration with a third-party developers as well.
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.