Skip to content
Mtaji TechnologiesMtaji Technologies

A deployment in production

A bank’s own supply chain finance operation, live.

Natbizz, National Bank of Kenya’s own supply chain finance platform, runs on the Ankara Platform, live in production. It is the bank’s brand, the bank’s customers and the bank’s credit decisions; Mtaji is the software underneath. This page walks through how it is structured: the part a bank planning its own deployment needs to see.

What was deployed

Three layers, and the boundaries between them are the case study: whose brand, whose customers, whose credit decisions, whose software.

The bank

Brand, customers, credit decisions.

The program is the bank’s product. The anchors are the bank’s corporate customers, the suppliers and distributors in those programs are the bank’s customers, and every credit decision is the bank’s, under its own policy and limits. The M-Score is an input to that decision and never a substitute for it.

The platform

The software underneath.

The Ankara Platform runs the programs (onboarding, instruments, pricing display, settlement workflow, the M-Score) configured to the bank’s product set and risk criteria, and operated by the bank’s people through the bank’s interface.

The footer

One fixed element.

Every white-label software surface carries a “Powered by Mtaji Technologies” line. It is a term of the model rather than a design choice.

On what timeline

Three workstreams are scoped before signature, and a shallower integration launches sooner than a deep one. The walkthrough covers the dates and durations.

  1. Brand applied

    Theming is configuration rather than a development project, and your customer sees your bank on every screen.

  2. Product set and criteria configured

    The product set a bank switches on is configuration: supply-side products, buy-side facilities, and the risk criteria that govern them.

  3. Integration at the depth you choose

    A full integration connects your core banking or loan management system; a lighter integration receives opportunities, returns decisions and confirms settlement through the rails you already have, and can deepen later.

The walkthrough sets out how each workstream ran in that deployment, and how it would run in yours.

Review the documents behind this case study

Banks and partners evaluating a deployment can ask for access to the data room. Someone at Mtaji reads each request and replies before the room is opened to you.

Evaluate the model this deployment runs on

The white-label page carries the four objections banks actually raise (timing, branding, core banking, data ownership) and the documented hosting position. The walkthrough covers what this page deliberately leaves out.