Payments & fintech infrastructure

Money that moves correctly, every single time.

MoMo, Airtel Money, the banks and the card networks each speak a different language, fail in different ways, and none of them reconcile themselves. Most payment bugs in Rwanda are not payment bugs — they are missing ledgers, missing idempotency and silent retries. Money software is the least forgiving software there is.

HOW YOU KNOW

You have this problem if…

If none of these sound like your organisation, this is probably not the domain you need — and we will say so rather than sell you into it.

  • !Month-end reconciliation is a manual, human, error-prone ritual
  • !Customers find your failed or duplicated transactions before you do
  • !You are launching a product that will hold other people's money and cannot afford to learn on the job
  • !Your provider integration works until it doesn't, and nobody can say why
WHAT WE BUILD

Systems we have built in this domain.

WHO ARRIVES WITH THIS

Fintech founders. Lenders and savings products. Marketplaces and commerce platforms. Anyone holding, moving or reconciling other people's money.

  • MTN MoMo and Airtel Money collections and disbursements, wired properly
  • Card, bank and cross-border rails alongside mobile money
  • Double-entry ledgers and wallets that always balance
  • Automated reconciliation, settlement and exception reporting
  • Lending, savings, payroll and bulk-disbursement engines
  • Agent and merchant networks with float, commission and limits
  • USSD and SMS flows for the customers who don't have a smartphone
TYPICAL STACK
Node.jsPostgreSQLEvent ledgersMTN MoMo APIAirtel OpenAPIQueues & webhooksIdempotency

The stack is a consequence of the problem, not a preference. Where you already run something else, we work in what you have rather than forcing a rewrite you did not ask for.

HOW IT RUNS

Scoped before it is priced. Written down before it is built.

Every engagement in this domain starts the same way: a paid technical discovery that ends in an architecture, a fixed scope and a fixed price. You own that document either way.

01

Technical discovery

1–3 weeks · Fixed fee

Every engagement that involves building something new. This is where we start.

02

Fixed-scope build

Scoped in discovery · Milestone-based

A defined system with a clear boundary: a core platform, a payments engine, a mobile product.

03

Embedded engineering

Monthly, rolling · Per engineer, per month

Organisations with a technical team that needs depth, speed or a skill they do not have in-house.

04

Run & evolve

Ongoing · Monthly, under an SLA

Any system the organisation now depends on, whether we built it or inherited it.

Tell us what is breaking. We will tell you what it would take to fix it.

Bring us the problem