intive logo

intive - 2018 All Rights Reserved.

In response to PSD2 regulatory and usage pattern changes of contemporary banking stack, intive developed the Okapi solution. It allows rapid deployment of banking APIs, facilitates integration with third parties as well as implements the highest level of security – all in line with the requirements of various financial markets. 

The solution was made specifically for hosting open banking APIs, which makes it also the ideal solution for several other use cases, especially for a mobile application middleware. The platform offers several benefits over more traditional approaches to internal banking APIs exposition, namely compared to serving the requests from the banking core with an Enterprise Service Bus class middleware in between.


What is _okapi?

Why _okapi?

Comply with new banking
regulations – 
easily and fast!

FLEXIBLE

Okapi solution gives you the possibility to implement different APIs - depending on the requirements of the specific markets. It guarantees a seamless experience for all customers accessing your banking products and services.

SCALABLE

The Okapi’s architecture is modeled after the largest API providers – social networks. Infinitely scalable, eventually consistent platform ensures real support and stability in cases of increased traffic between a bank and TPPs.

Multi-tenancy

The system is built with multitenancy in mind. The data models, identifiers, as well as permission systems, allow for seamless integration of data from multiple entities. The system is prepared to support large-scale deployments. Potentially these deployments could be cloud-based, and able to serve hundreds of co-existing entities from a single API.

Isolation of underlying systems from API

The system is designed to isolate the interface layer (APIs) and the core systems of the bank, in three dimensions:

_Load dimension – the API load is not linked to the core system load;

_Security dimension – separate compartments for API related permissions and API targeted security model based on authorization delegation;

_Information scope dimension – keeping data interfaces limited to required minimum.

Authority delegation model

The system of authorization needs to support delegation of authority to third parties by the customer. 
Thus, the users of the API are not the customers themselves. Registration, management, and control over permissions granted to third parties are supported using the tooling provided on the platform.


CUSTOMER ORIENTED

Okapi is unique in its ability to describe the permissions that can be delegated to a third party. No other API targeted solution on the market, especially the API management platforms, can match it in terms of configurability.

Architectural drivers

SEND

Make your Bank futureproof.

Let’s talk.

"

Okapi solution consists of 80% ready-made components, while the other 20% can be tailor-made for your organization. We will support them and always take your existing environment into consideration. This will protect your investment, lower the acceptance barrier, and make the transition comfortable.

Sebastian Łękawa, 
VP Sales, Financial Services

Let’s talk.


SECURE

Okapi is completely isolated from the central bank system, ensuring the highest level of safety. Regardless of the number of API clients – your underlying system will always remain under control. Security is based on the OAuth2 standard and optimized for the banking API use case. 


.

Fix the following errors:
Hide