Initiate phone-based payment workflows where the relevant commerce module is enabled.
M-Pesa commerce
Use M-Pesa for school commerce without fragile callback logic.
ShuleMatrix includes M-Pesa payment gateways for digital resources and SMS-credit commerce, with server-side callbacks, payment events and idempotent order handling.
Payment events that can be retried safely.
WHY IT MATTERS
Designed around the work schools actually need to finish.
Process provider callbacks server-to-server.
Record payment events and protect order processing from duplicate callbacks.
Grant the purchased entitlement only after payment state is confirmed.
HOW IT WORKS
A clear workflow from first action to accountable outcome.
1Choose item / package
→ 2Enter M-Pesa number
→ 3STK request
→ 4Callback verified
→ 5Payment recorded
→ 6Entitlement / credits granted
BUILT INTO THE PLATFORM
Depth without creating another disconnected system.
Each capability sits on the same school, learner, role and audit foundations used by the wider ShuleMatrix platform.
Resource payments
Marketplace purchases can use an M-Pesa resource payment gateway and secure purchase recovery.
SMS commerce
SMS packages can be purchased through a separate M-Pesa commerce service where configured.
Idempotent processing
Payment workflows are designed to tolerate duplicate callback delivery without repeatedly granting value.
QUESTIONS
What schools usually want to know.
Does every school automatically receive M-Pesa integration?
Payment credentials and commercial configuration remain deployment-specific. The application provides the payment workflow; production credentials must be configured securely.
What if a callback is sent twice?
The implemented commerce flows are designed around idempotent order/payment handling so repeated callbacks do not repeatedly grant the same purchase.
SEE IT WITH YOUR SCHOOL DATA