Insights · Keshio

How to Reconcile M-Pesa Payments for a Small Business in Kenya (2026)

Disclosure: this guide is published by the team behind Keshio, whose Business Ledger API is one of the options below. Where we describe other methods, we keep to what is publicly documented. Last reviewed: November 2026.

Reconciling M-Pesa means matching every payment that reached your till, paybill or phone against your sales records, so the numbers agree at the end of the day. If you run a shop, salon, clinic or small online business, you probably do this by scrolling through SMS and a statement. This guide covers the four common approaches, where each one breaks down, and when an API-based approach is worth the cost.

Quick answer

  • A few payments a day: a daily check against your M-Pesa statement is enough.
  • Steady volume and a till or paybill: use Safaricom's own business tools and, if you have a developer, their API.
  • Gaps that those miss (SACCO messages, bank alerts, missed callbacks): consider a phone-based ledger such as Keshio's Business Ledger API.

Why reconciliation goes wrong

  • Many payment channels. Customers pay by till, paybill, send money, bank transfer and SACCO deposit. Each produces a different message or record.
  • Missed notifications. An integration can miss a payment callback, and then your system and your M-Pesa balance disagree.
  • Manual work. Copying amounts from SMS into a spreadsheet takes time and invites typing errors.
  • Month-end surprises. A mismatch found 30 days later is far harder to trace than one found the same day.

Four ways to reconcile

Approach Good for Where it falls short
Manual check against your M-Pesa statement Very low volume Slow, error-prone, found late
Safaricom's M-PESA for Business app and portal Tracking till collections and payouts Not integrated with your sales system by default
Safaricom Daraja API integration Businesses with a developer Does not cover every case; needs development and maintenance
Phone-based ledger with an API (Keshio Business Ledger API) Filling gaps for SACCO, bank and missed-callback payments Android phone with Keshio Pro required; paid

1. Manual checks

Download or view your statement each day, tick off each payment against your sales book, and note anything unmatched. This is free and fine at low volume. The risk is timing: if you only do it monthly, a single missing payment is very hard to find.

2. Safaricom's M-PESA for Business

Safaricom publishes an M-PESA for Business app described as a way for merchants to transact and track M-PESA collections and disbursements. It is the right first stop for most till and paybill owners. Check what exports and reports it offers for your account type.

3. Daraja API integration

Daraja is Safaricom's developer API. Developers use it to receive payment notifications in their own systems. It covers many merchant flows, but gaps remain: payments that arrive as SACCO or bank SMS, and callbacks that fail to reach your server, can leave your records short. If you already have an integration, keep it and consider a second source to cross-check it.

4. A phone-based ledger with an API

Keshio already structures M-Pesa, SACCO and bank messages on the phone. Its Business Ledger API shares only the events the phone's owner has agreed to share, with systems you control, so you can reconcile automatically.

How the Keshio Business Ledger API works

  1. Opt in on the phone. Use Keshio Pro on Android, enable Business Ledger sharing in the app, and choose which wallets and scopes to share.
  2. Create an API key. You can do this from the developer console (sign in with the same Google account as the app) or from the app. The key's plaintext is shown once.
  3. Pull or receive events. Pull structured credits and debits with a simple request, or register an HTTPS webhook that Keshio calls with signed payloads.
curl -sS "https://api.keshio.app/v1/events?limit=50" \
  -H "Authorization: Bearer keshio_live_YOUR_KEY"

Results are paginated with a cursor. Webhook deliveries carry a timestamp and an HMAC signature header so your server can verify they are genuine.

Privacy: you get structured event fields, not SMS text. Raw messages stay on the phone, no inbox access is given, and phones that have not opted in share nothing. If sharing is switched off, an old key stops working.

What it costs

  • Business Ledger API: KES 1,000 per month.
  • Keshio Pro: KES 500 per month. The phone sharing the events must be on Pro.

For a business, the useful comparison is the cost of a few hours of manual reconciliation each month, plus the cost of a missed payment going unnoticed.

When this is not the right fit

  • You have very few payments. A daily statement check is cheaper.
  • You need iPhone support. Keshio's ledger relies on SMS access, which is available on Android only.
  • The phone is unreliable. Events come from messages that reach the opted-in phone, so a phone that is off, out of network or missing the SIM cannot report them. Pair the API with a regular statement check.
  • You want a full accounting system. The API provides payment events. You still need to match them to invoices and sales in your own software.

A simple daily routine

  1. Pull the day's events at closing time.
  2. Match each one to a sale or invoice.
  3. Flag anything with no match and investigate the same day.
  4. Once a week, compare your event total with the M-Pesa statement total.
  5. Keep the statement as the final record for audits and tax.

Frequently asked questions

Does the API give me my customers' SMS messages? No. It returns structured payment events for the scopes the phone's owner approved. SMS bodies and inbox access are not shared.

Do I need a developer? To use the API directly, yes: someone has to call the endpoint or receive webhooks. If you don't have a developer, start with Safaricom's business tools and a daily statement check.

Can I stop sharing? Yes. Turning sharing off in the app stops new events, and any machine holding an old key is refused once the connection is disabled.

Does this replace Daraja? Not necessarily. It is designed to fill gaps that other methods can leave, such as SACCO messages, bank alerts and missed callbacks.

Does it work on iPhone? No. It requires Keshio Pro on Android.

Get started

See how the API works at keshio.app/blog/business-ledger-api-consented-events, or open the developer console at api.keshio.app. To try the app first, search for Keshio: Mpesa Ledger & Budget on Google Play.

Questions or corrections? Email [email protected] and we'll update this guide.

Image