Identity protection
Mobile numbers and encrypted national ID records support a consistent member identity while masking sensitive values from ordinary group users.
Security is a continuous operating responsibility.
Pamoja Chama combines application controls with clear human responsibilities. These measures reduce risk, but secure hosting, monitoring, backups, updates and independent testing remain necessary.
Password and OTP security
The authentication architecture supports short-lived, single-use codes with hashing, attempt limits, resend controls and browser-session binding. OTP is activated only after delivery testing.
Role-based access
Members, officials and platform staff receive different permissions. Sensitive actions require explicit server-side authorisation.
Financial integrity
Double-entry journals, duplicate-reference prevention, immutable reversals and trial-balance checks help identify accounting errors.
Approval separation
High-risk actions can be initiated, reviewed and approved by different authorised people, including mandatory executive review where configured.
Audit evidence
Important actions are recorded with the responsible account, time and context, with tamper-evident integrity checks for enterprise controls.
Locked provider APIs
M-PESA, bank, USSD, SMS and email provider APIs require contracts, certification, security review, clearances and a controlled activation. They are disabled by default.
Kenya-first controls
Kenyan currency, phone and identity rules are active. Other East African country profiles are reserved but disabled until local requirements are completed.
Never send a password, OTP, USSD PIN, national ID image or database credential through ordinary email or WhatsApp. Pamoja Chama staff should never request your password or OTP.