Kowry Overview
We are building cross-border settlement orchestration for fragmented African mobile money and banking rails, beginning with a corridor-first operating model.
Open overviewWe have prepared this page for investors, banks, operators, and strategic partners reviewing our corridor-first settlement work.
These materials explain how we are approaching corridor settlement infrastructure, while keeping API design, partner strategy, licensing work, and corridor economics for qualified discussions.
We are building cross-border settlement orchestration for fragmented African mobile money and banking rails, beginning with a corridor-first operating model.
Open overviewThe public investor page explains the pre-seed case, Tanzania-Zambia focus, regulatory workstreams, and partner routes.
Open investor pagePublic compliance posture covering AML/CTF principles, sanctions screening, operational risk, and pre-commercial regulatory status.
Open AML policyCore public legal pages for data handling, platform terms, partner dependencies, and cross-border settlement risk disclosure.
Short notes on the market problem, our infrastructure approach, and the regulatory posture behind the work.
Africa already has high-trust domestic rails: mobile money, banks, and local payment processors. The weak point is cross-border coordination between those rails. We are starting with one corridor so licensing, operator engagement, liquidity, FX handling, and reconciliation can be proven before expansion.
We treat cross-border money movement as stateful infrastructure, not a clean API call. Every transaction should have explicit lifecycle state, idempotent retry behavior, route health checks, liquidity controls, and reconciliation evidence.
Kowry is pre-commercial and is not currently authorised by the UK Financial Conduct Authority as a regulated financial institution. Planned services remain subject to licensing, partner agreements, jurisdictional permissions, and further legal review.
We can share deeper materials with VCs, banks, operators, and regulated partners where there is a clear diligence or partnership purpose.
High-level architecture, investment narrative, corridor rationale, and operating assumptions. We share this selectively for qualified diligence.
Settlement lifecycle, idempotency, ledger principles, route health, liquidity controls, reconciliation, and manual review design.
Inspectable scenarios for duplicate callbacks, delayed confirmations, liquidity shortfall, FX variance, reconciliation breaks, and treasury review.
Corridor readiness, licensing gates, banking and operator model, compliance expectations, and controlled beta requirements.
Some materials are better reviewed in context with investors, banks, operators, counsel, or regulated partners.
Request our investor diligence pack, corridor rationale, architecture summary, and controlled simulation walkthrough.
investors@kowry.ioRequest a partner conversation with us around corridor readiness, settlement controls, reconciliation, liquidity, and compliance dependencies.
partners@kowry.ioReview the public AML position first, then request additional policy and control detail where there is a specific review need.
compliance@kowry.io