Built for regulators, not retrofitted for them
Every member's money moves directly between their own M-Pesa and their SACCO's own paybill — SaccoSphere never holds it. What we hold is the record, and we hold it the way a regulator would insist on.
A technology platform, not a financial institution
SaccoSphere provides software, workflow automation, audit trails, reporting tools, and payment integration infrastructure. The licensed SACCO remains the regulated financial institution and the holder of member funds — the same relationship as a SACCO using any core-banking software.
SaccoSphere does not hold member deposits, does not issue loans from its own balance sheet, and does not act as a payment intermediary in the regulated sense. A transaction-fee model requires a CBK Payment Service Provider licence — not a banking licence, SASRA registration, or deposit insurance.
Five controls, none of them optional
No balance column anywhere can be edited directly. Every movement posts through one audited entrypoint — balances are always calculated, never stored.
The officer who approves a loan cannot be the officer who disburses it. The admin who declares dividends cannot approve them. Four eyes, enforced in the model, not the manual.
Every sensitive change is hashed to the entry before it. Tamper with one row outside the application and the chain breaks on the next verification.
Daily exports to object-locked storage for legal non-repudiation — built toward the multi-year transaction retention regulators expect.
Credit-bureau responses and payment credentials are encrypted at rest. PII never persists in plaintext.
Consent, retention and erasure, by design
Kenya’s Data Protection Act 2019 right-to-erasure requirement is handled through managed retention-policy rules and documented erasure workflows — every erasure is logged, audited, and reversible within its retention window, not a manual database delete. Each SACCO is treated as its own data controller; one SACCO’s member data is never used for another tenant without that member’s own consent.
Where we stand, stated plainly
| Licence / registration | Regulator | Why | Status |
|---|---|---|---|
| Company incorporation | BRS | Required to sign contracts and open bank accounts. | In progress |
| KRA PIN + VAT registration | KRA | Required to invoice SACCOs and remit taxes. | In progress |
| ODPC Data Controller registration | ODPC | Mandatory before handling real member personal data. | To be filed |
| CBK PSP licence (Electronic Retail) | CBK | Required before charging transaction-percentage fees. | Preliminary meeting requested |
| SASRA licence | SASRA | Not required — SaccoSphere is not a SACCO. | Not applicable |
| Banking licence | CBK | Not required — SaccoSphere holds no deposits. | Not applicable |
We’re a young company — so instead of big promises
This page tells you what we’ve built, what we’re doing before we go live, and what we don’t claim yet.
Doing diligence on us? Request our full security and compliance overview — we’ll send it directly, not gate it behind a form.
Questions a diligence team would actually ask
We'd rather answer them directly than have you infer the answer from a marketing page.