Now on WhatsApp Pay
Collection is not revenue.Ujumbe Pay keeps the difference straight.
A payment orchestration and collection platform that sits above payment providers. It collects money through APIs, hosted links, invoices, recurring billing and now WhatsApp Pay, applies your fee rules, records both sides in a double-entry ledger, settles merchants and reconciles against the provider.
Collected
TZS 50,000
What the payer paid
Ujumbe fee
TZS 1,500
Platform revenue
Merchant payable
TZS 48,500
Owed, then settled
Kili Freight
online
Payment request
Freight 25kg Dar → Arusha
TZS 45,000
TZS 45,000 · M-Pesa 0712 345 678
Receipt RCPT-2026-000181 · settles on your next payout
9:41WhatsApp Pay powered by Ujumbe Pay
The four engines
Provider-agnostic by design. Selcom is the first adapter behind the interface, never the architecture itself.
Fee engine
Fixed, percentage, percentage + fixed, tiered, capped or zero — per merchant, per product, payer-aware.
Double-entry ledger
Every collection splits into Ujumbe revenue, merchant payable and gateway cost. Debits always equal credits.
Settlement engine
Batch what a merchant is owed, net of fees and refunds, on their own settlement cycle.
Reconciliation
Daily provider-versus-ledger comparison that flags mismatches instead of hiding them.
Modules on one platform
Pay API
Create a payment, poll it, receive the webhook.
Payment links
Hosted checkout with no integration at all.
Invoice collection
Bill references, invoices and control numbers.
Collections for third parties
Collect on behalf, keep your cut, settle the rest.