What is Kariz?
- A Banking channel management tool that allows you to control the channel’s access to services and resources.
- Connected to various banking and non-banking services such as core banking services, payment switches, registries and etc.
- New services can be added quickly and Kariz can provide the previous and current versions of a service to different channels at the same time.
- Kariz Provides a variety of reports in terms of channels, sources and services.
- Kariz is implemented using light and scalable micro-service standards.
Kariz Benefits for Banks and credit institutes
Facilitating provision of banking services to the bank’s development teams and business partners
Kariz facilitates providing service to bank’s various development teams and bank’s business partners, such as stock exchanges, insurance companies, etc. banks can benefit from the commercial advantages of connecting to other systems. The development of a new service due to the special architecture of Kariz, is conducted quickly and without dependency on other services.
Shrinking change requests in the banking core or old banking systems
Sometimes launching a project requires some older legacy systems to provide data or services, but making changes to those systems may not be easy or fast. In this situation, Kariz can connect to that system quickly and provide a well-defined service to the client systems.
Easy to change different banking systems
Kariz helps the bank to change a system like banking core or facility systems without making any changes to other systems such as Internet Banking or Mobile Banking.
launching open banking API
Providing private APIs from all major bank systems to various bank development teams and business partners performed by Kariz is a prerequisite for banks to provide Open APIs and grant access to customer data (with their consent) to third parties.
Kariz main features
Determining and controlling the access of channels to banking services
The services that each channel is allowed to call are specified, and before sending the channel request to other systems, Kariz controls the channel’s access to the called service.
Ability to restrict channels’ access to banking resources (deposits, cards, and specific customers)A channel that can only work with a specific list of customers, deposits, nights and cards can be restricted using Kariz.
Registration of service call logs by different channels and reporting them
The service call logs and their parameters and the result of the service calls are stored in the kariz database. in Kariz management panel, it is possible to report those logs according to chosen filters.
Channel authentication and controlling message integrity received from different channels
When each channel is defined in the kariz system, a security token (composed of a string of characters) is assigned to it. The channel in the service call must sign the service parameters with that token. this way, besides channel authentication, the integrity and non-repudiation of the called service is guaranteed.
Asymmetrical channel authentication
In addition to the shared secret keys, channel authentication can be performed using asymmetric keys that provide higher security standards.
Integrated simple service APIs to use by channels
The services provided by different systems in Kariz are based on the same standard and their API can be modified and simplified if necessary.
Providing combined services from one or more banking subsystems
Kariz can provide two or more services provided by different systems as one service to the higher layers and hide the complexity of the lower layers from them.
Authenticating the user of Kariz management panel based on the active directory of the bank
Kariz management panel is used in the bank’s headquarters and Authentication of users can be done according to any standard method intended by the bank. Currently, authentication through the active directory of the bank has is possible.
Ability to provide two different versions of a service at the same time
Usually, by changing the service of one of the bank’s systems, it is not possible to change and synchronize all the related systems at once. Kariz microservice architecture makes it possible for two new and up-to-date versions of a service to be provided at the same time so that related systems can be gradually updated.
Operable with load balancer
In Kariz microservice architecture, each service is provided separately on a distinct port and address and, if necessary, an independent database. If the amount of requests for a service is high, several samples of it can be raised at the same time and the requests can be distributed among them through a load balancer.