Payments should only move when outcomes are verified
ArosaPay builds conditional settlement infrastructure — the governance layer that ensures funds transfer only when contractual expectations are met.
The payment layer was built for trust between known parties. Commerce now operates between strangers.
ArosaPay exists because the payment layer should enforce accountability — not assume it.
From assumption to verification
ArosaPay doesn't fix payments. It replaces assumption with verification.
Conditional payment release. Deterministic outcomes.
Payment initiated
Buyer commits to purchase. Payment amount is locked.
Funds held securely
Funds are held by our licensed payment partner — neither party controls them.
Conditions tracked
Delivery, inspection window, or time-based triggers are monitored against defined rules.
Buyer confirms or system triggers
Release is initiated by buyer confirmation or automated policy completion.
Funds released to seller
Settlement executes. Seller receives payment. Transaction closes.
No ambiguity in when money moves.
How we build
Verification over assumption
Transactions should be validated, not trusted blindly. Every release requires confirmation.
Deterministic by design
Funds move based on rules, not interpretation. No ambiguity in settlement logic.
Universal protection
Every transaction gets the same governance framework, regardless of size or participant.
Radical transparency
Every fee disclosed. Every state visible. Every policy published. Open processes build institutional trust.
The infrastructure gap is widening
E-commerce in Africa growing 25%+ annually
Transaction volume is outpacing trust infrastructure
COD rejection rates averaging 30–40%
Cash on delivery is collapsing under its own inefficiency
Digital fraud losses increasing year over year
Irreversible payments create asymmetric risk for buyers
No conditional settlement layer exists for African payment rails
M-Pesa, bank transfer, and card networks lack outcome-based release
ArosaPay is building the missing layer.
Not just checkout — settlement architecture
API-first architecture
Programmatic access to every settlement primitive
Secure fund holding
Funds held in trust until conditions are met
Compliance-ready
Designed for regulatory requirements from day one
Payment rail integration
M-Pesa, bank transfer, card — unified settlement
Leadership team
The team building ArosaPay's protected checkout and conditional settlement infrastructure.
Victor O. Matoka
CEO & Founder
Leads ArosaPay's product and operating direction.
Doreen Gakii
Senior Product Development Manager
Leads strategic bank and fintech partnerships across multiple markets at Cellulant, translating client needs into payment solutions spanning collections, APIs and interoperability.
Mathew Okusimba
Senior Software Engineer
Built the Next Insurance motor underwriting and sales platform, integrated M-Pesa and card payments, and developed REST APIs and MySQL-backed systems.
Start transacting with conditional settlement
Funds are captured at checkout and held until buyer confirmation.