Children and school context
See authorized learner relationships without exposing unrelated school records.
School fee payment app Kenya
Authorized parents and guardians can review the school-fee record connected to their child, open invoices, see balances and payment history, start eligible M-Pesa payments, and revisit receipts.
The operational problem
SchoolPey connects the parent experience to the same school-owned invoices, canonical payments, allocations, balances, learner credit, and receipts used by the finance team.
See authorized learner relationships without exposing unrelated school records.
Open the learner invoice and review what remains outstanding.
Review canonical payments already attributed to the learner.
Start an eligible payment from the learner invoice through the integrated provider flow.
Observe the server-side collection state instead of relying only on local app state.
Open supported payment or settlement receipts after the canonical financial event exists.
How SchoolPey handles the workflow
The parent sees only children and school-student relationships they are authorized to access.
See the current invoice/balance and start an eligible M-Pesa payment when needed.
After provider confirmation and SchoolPey reconciliation, the canonical payment and receipt remain available.
Frequently asked questions
No. Family access is relationship-based. Parents and guardians can only access the school-student records SchoolPey authorizes for their account.
No. The parent app never becomes a second financial ledger. Payment truth remains backend-owned and depends on canonical payment/reconciliation records.
No. The parent approves payment through the normal M-Pesa flow; SchoolPey never receives or stores the PIN.
Try the real workflow
Evaluate the fee operation with actual billing, payment, reconciliation, balance, receipt, statement, and reporting workflows before standard billing.
Request a 1-month pilot