Help to stop the war! Stand with Ukraine!
Contact Us

Designed to make your neobank outstanding

Our neobank core banking solution is built on the stack of technologies that facilitate your neobank and make it successful.


Find out about the technologies and architecture of the project


We designed a robust, reliable system you can scale and update. Our neobank core is predesigned by its modular architecture to have a long SDLC (Software Development Life Cycle) and allow you to update one of its components while other API-connected modules are functioning as always.

The high-level structure of our core:

banking core infrastructure

Current version of neobank core runs on this stack

Check the languages and frameworks we use to create software solutions for your neobank product.

Frameworks and environments
  • PostgreSQL 13
    We use it to create our Operational DB.
  • MongoDB 4
    Used for Transaction Viewer DB.
  • Java SE 16
    Core of your neobank is developed on it.
  • Spring 5.3.9
  • Spring Boot 2
  • Hibernate ORM 5
  • VUE.JS

What approaches do we apply for these products

  • Gitlab as core repository
  • SonarQube, Spotbugs, OWASP, JUnit tests, PMD, and CheckStyle for Code QC
  • DB agnostic
  • Cloud-based or on-premises software
  • API architecture style: REST, gRPC
  • Mapping: Mapstruct
  • Timer: Quartz TImer

Deployment and Data Migration

Core banking software is a complex solution that requires a certain procedure of core deployment and data migration. We recommend some routine that will minimize the risks for the infrastructure functioning. Follow our tech requirements for software and hardware to conduct it successfully.

This scheme represents the deployment and migration process:

core banking deployment and migration

The core banking infrastructure consists of 3 servers: developers instance (for development and testing of the software), production instance (live operation server with end-users and real operations), and pre-production or Sandbox (infrastructure with the same specs as the production instance. Used for debugs of integrations with third-party components).

Hardware requirements designs reliable and high-load solutions. They allow you to scale up and out the core banking system. To do this, your hardware should meet the requirements, so the performance of the whole infrastructure does not fail.

To run the system and secure its stable performance, you will need two instances of the infrastructure. Your team will use one for system compilation and development, while the second one is your working neobank instance. You will need two sets of hardware architecture. Here are the minimum requirements of the instance for both Production and Test environments:

Load Balancer
Application server
Postgres Database
Transaction Viewer Database

CPU – 1
RAM – 1 GB
SSD – 20 GB
OS: Ubuntu 16.04 LTS
Software: NGINX 1.14.0

CPU – 1
RAM – 2 GB
SSD – 40 GB
OS: Ubuntu 16.04 LTS
Software: NGINX 1.14.0

CPU – 4
RAM – 8 GB
SSD – 160 GB
OS: Ubuntu 16.04 LTS
Software: Wildfly 10.1.0.Final

CPU – 4
RAM – 16 GB
SSD – 160 GB
OS: Ubuntu 16.04 LTS
DB: PostgreSQL – 10.6

CPU – 2
RAM – 4 GB
SSD – 80 GB
OS: Ubuntu 16.04 LTS
DB: MongoDB – 3.0.4

Cisco ASA 5508

Scaling up and scaling out your neobank core offers neobank solutions for fintech companies with diverse business models. This difference shapes the load of traffic and operations for the core banking system we provide. For example, a successful neobank for individuals seeks for 30-70 operations a second for 5-7 active profiles in the system. The merchant neobank is more operations-heavy while focusing on fewer clients in the system.

You can plan your scaling process both up and out with our solution. The API-oriented architecture will allow you to execute a realistic and balanced architecture scaling that will supply your business growth. Designing the neobank core the way we do it, allows us to limit the number of potential bottlenecks in business flow.

Security: code, architecture,interface and transactions develops products that should not have any loopholes in their security on any level. We check the code, design the system where you manage the excess of the employees, and log the changes they do in the neobank core.

Security of the source code

We develop code on the Java SE 16. The code is tested with JUnit, Arquillian and checked with OWASP security scanner. We check the code quality with SonarQube, UpSource and FindBugs.

System Architecture Security

Neobank core is developed according to the PCI DSS standard. This one is specifically designed to secure cardholders from fraud and private data loss. We also follow the ISO standards in code development, meeting the requirements of the ISO 27001, ISO 12812, ISO 12812-5.
The interaction between clients and server components in the system is protected by a variety of traffic encryption methods (TLS with a 256 or 512 bit encryption), data hashing algorithms (SHA-256 or SHA-512), data packets signature, checksums verification, IP filtering and brute force attacks protection.

We implement firewalls, IDS (Intrusion Detection System), WAF (Web Application Firewalls) and load-balancing into the system. also uses software and hardware solutions from the market leaders (Oracle, IBM, Amazon, Microsoft, Google).
We can also use additional methods of encryption on the application or database level to protect cardholder data, personal account number, etc.

Clients’ and back office interface security

To protect your neobank system on the high-level infrastructure, we apply OTP and ​​HMAC authorisation for back office access. On a basic level, we use two-factor authorisation and OAuth (Open Authorization) to log in the neobank account. Back office also allows you to define the exact sections of the core your employees can use. There you can define the list of trusted domains too.

API solutions for core banking software uses a RESTful application program interface to connect the functional blocks of the core banking system as well as third-party solutions. The neobank product requires many integrations that should be flexible, manageable, and reliable.
We use Swagger, an industry-leading framework, to design, build, and document our flexible APIs. The framework allows us to automatically create and update our interactive API documentation to keep our users up to date. works on the list of the APIs compatible for the integration with the neobank core solution. The number of compatible APIs is exceeding 400 in the latest release.

api software for core banking solution