Updated 11 October 2026

Integrations · Skoolway

Skoolway does not need a platform-wide key from Safaricom, Pesapal, or a bank. Each school pastes the keys for its own account. A school with no keys can still record fees by hand.

Fee accounts a school can connect

M-Pesa through Safaricom Daraja, for a paybill or till the school controls. Pesapal, for payments started from the family portal. Equity Jenga account alerts. KCB Buni payment notices. Co-operative Bank instant notifications.

A school can connect more than one account, including two accounts of the same type when the numbers differ. The account number in the notice is how Skoolway knows which school it belongs to.

When a payment is recorded

The provider must be able to reach the public Skoolway API. The school’s account must be saved and turned on. The payment reference must match exactly one learner, by roll number or NEMIS. If it does not, the notice is kept for the bursar to match. The same receipt is not recorded twice.

Until the school turns the account on, a matched notice is stored as a test and is not written onto the fee record. Cash, cheques, and any transfer that the provider does not notify Skoolway about stay manual.

Sign-in and school identity

Staff can sign in with email and password, or with Google. Google sign-in shares the verified name and email. Skoolway does not receive the Google password.

Primary and secondary schools can store a NEMIS code and a KNEC code. TVET can store a registration number and category. A university can store CUE status and an accreditation number. These are fields the school fills in. Skoolway does not submit them to those agencies.