Skip to content
In developmentFintech

Kreb — Open Banking (upcoming)

An upcoming open-banking app for businesses and consumers, built to fintech-grade engineering rules — and the product I represent as brand ambassador.

PresentationDomainDataAPI gateway / BFFMicroservicesEventsData storesInfrastructureSecurity & observability
Role
Brand ambassador
Team
XEOO team
Timeline
Jul 2026 – Ongoing
Organisation
Kreb (XEOO)
Code
Proprietary (employer)
Reading time
1 min

Kreb brings banking, payments, billing and financial management into mobile apps for merchants and consumers. The XEOO team is building it with Flutter on Clean Architecture over a microservice backend; I am its brand ambassador.

Overview

Kreb is an upcoming open-banking app from the XEOO team. Kreb Business, the merchant app, is in active development, with a consumer app to follow. As brand ambassador I represent Kreb ahead of its launch.

The problem

Moving money is the one place where "move fast and break things" is unacceptable: a crash mid-transfer must never lose or duplicate funds, every action must be auditable, and customer data must never leak.

Context & constraints

Kreb is designed for launch under strict regulatory thresholds, including PCI-DSS and Bangladesh Bank's cyber-security guidelines.

Approach

The team works to a written engineering charter. Highlights:

  • Zero financial drift — an append-only ledger: monetary entries are never edited or deleted, only offset.
  • Sagas for distributed transfers — every multi-step transfer has a compensating path that reverts state if a step fails.
  • Strict idempotency — every payment carries a client-generated key, so network retries can't double-charge.
  • One microservice, one responsibility, one database — failures stay isolated, with circuit breakers between services.
  • Security in depth — encryption at rest and in transit with certificate pinning, hardware-backed biometrics with secure storage, and audit logs of who did what, and when.
  • Day-zero disaster recovery — backups and failover exist before production, not after.

Key capabilities

  • Mobile banking and payments for merchants
  • Billing and financial management
  • Biometric sign-in with secure storage
  • Append-only ledger with idempotent payments
  • Consumer app to follow

Architecture

  1. Mobile app

  2. Backend

  3. Platform

A Clean-Architecture Flutter app talks through a backend-for-frontend to isolated microservices, each with its own database. Select a component to trace its connections.

Quality & delivery

Testing

Every feature is tested on small and medium phone emulators in portrait and both landscape orientations before a pull request is opened.

Outcome

In development ahead of launch.

Building something similar?

Tell me what you’re working on — I reply to every serious message.

Related work

React 19 SPAIdentity providerAPI routers18 domain modulesCapability matrixJob workerTransactional outb…PostgreSQL 16RedisObject storage
Case study
In production2026Green Compare Ltd (XEOO team)

Green Compare CRM

A FastAPI modular monolith with a React 19 front end, where Postgres row-level security backs every permission check. I started the repository, then shipped features across finance, telesales, renewals, dashboards and access control.

  • TypeScript
  • Python
  • React
  • Ant Design
  • TanStack Query
  • FastAPI
  • +9