Industry · Kenya

Fintech & payments.

Fintech product development for Kenyan operators — M-Pesa and bank integrations, KYC flows, double-entry ledgers, regulatory compliance, and apps that survive a 2am Daraja callback storm.

Built by a Nairobi studio that's shipped payment infrastructure in production for five different Kenyan fintechs.

Start a project See our work

Fintech in Kenya has genuinely-hard integration work hiding behind a deceptively simple UI. M-Pesa Daraja has callbacks that never arrive. Bank Open Banking APIs in Kenya are effectively KCB Buni and Equity Jenga Pay, and each has edge cases. A 'send money' screen that looks 10 minutes of work is 3 weeks when you account for idempotency, retries, reconciliation, compliance logging and edge-case recovery.

We've shipped savings apps, lending originations, remittance flows, B2B payments and subscription-billing infrastructure. The common pattern: a small, senior team pairing with the founder, sprints that include observability and compliance from day one, and a handoff with a runbook rather than a pile of undocumented code.

Common pains

What we fix.

  • 01
    Daraja callbacks that never arrive
    M-Pesa confirmation never hits your webhook. User sees 'Payment pending' forever. Support ticket storm. We wrap Daraja in idempotent retry + reconciliation so 0.5% stranded payments become 0%.
  • 02
    KYC flow that losing 40% of sign-ups
    Photo of ID, selfie, KRA PIN, next of kin, 12 checkboxes — all on one page. Users bail at step 3. We split, save-progress, and drop abandonment to under 15%.
  • 03
    A ledger that breaks at 10K transactions
    Balances computed on demand, no double-entry, reconciliation by spreadsheet. Works until it doesn't. We rebuild as proper double-entry with audit trail.
  • 04
    Compliance docs scattered across 4 Google Drives
    CBK audit coming in 6 weeks. No one can find the terms-of-service version that was live in April. We wire compliance logs into the data model.
What's included

Everything you walk away with.

  • Mobile app (React Native or Flutter) + web dashboard (Next.js)
  • M-Pesa Daraja integration (STK, C2B, B2C) with retry + reconciliation
  • KCB Buni / Equity Jenga Pay integrations
  • Card payments (Stripe, Pesapal, DPO)
  • KYC flow with document OCR, selfie match, KRA PIN verification
  • Double-entry ledger with audit trail
  • Transaction dashboard + reports for ops team
  • Observability (Sentry, PostHog, Datadog)
  • Compliance-ready audit logging (CBK, Data Protection Act)
Who we build for

Typical clients.

  • Savings / investment app
  • Lending origination platform
  • Remittance / cross-border payments
  • B2B payments + invoicing
  • Subscription billing infrastructure
  • Neobank / digital wallet
FAQ

Fintech & payments-specific questions.

Do you have CBK-compliance experience?
Yes — we've supported clients through CBK PSP licensing audits and Data Protection Act 2019 compliance. We build the technical evidence (audit logs, consent records, data-retention tooling) that auditors ask for.
Can you do KYC with document OCR?
Yes — we integrate with Smile Identity, iProov or Jumio for ID verification + liveness + KRA PIN lookup. We've shipped all three in Kenyan production environments.
How do you handle Daraja unreliability?
Idempotent request IDs on every call, retries with exponential backoff, polling fallback if callback never arrives, daily reconciliation cron against Safaricom's reporting API, and alerting for stranded payments.
Can you help us get a PSP licence?
We don't do the legal or capital-requirement work, but we build the technical infrastructure the CBK auditors require and work alongside your compliance lawyer. We've seen the process three times.
Related services

How we help.

Let's build
something quiet.

Tell us about the problem. We'll write back within one business day.

Chat on WhatsApp