Four M-Pesa patterns businesses confuse
Kenyan merchants often say "we take M-Pesa" but run four different technical patterns. Mixing them creates reconciliation pain.
1. STK Push (Lipa na M-Pesa prompt)
The cashier enters the customer phone and amount. Safaricom prompts the buyer to enter PIN on their handset. Best for counter sales when the customer is present. A good POS completes the sale only when payment is confirmed, not when someone hopes the SMS arrived.
2. Buy Goods till
Customer pays to your till number. Useful when the buyer initiates from their phone. Strong POS software records the till channel and supports auto-detect (C2B) where configured, so the sale can close without retyping references.
3. Paybill
Common for invoiced amounts, rent, or account-style payments. Paybill automation matters for wholesalers who expect customers to pay against an account reference.
4. Manual "reference only"
The weakest pattern: cashier types an M-Pesa code into a notes field. It works until audit week. Avoid systems that stop here.
What to demand from ERP or POS
- Channel captured on the sale (till vs paybill vs STK).
- Payment reference stored on the checkout group.
- Split payments for part-cash, part-M-Pesa.
- On-account sales that still record partial M-Pesa settlement against customer ledger.
Biashara ERP wires M-Pesa into checkout, subscriptions, and reconciliation-oriented workflows. Details live on integrations.
Biashara support