The Chama Dispute That Starts With One Missing M-Pesa Code

Your chama meets every Friday. Eight members, KSh 5,000 each month, rotating through a house or a café. By the third year, you have saved enough to think about a plot, maybe a retail stall. Then Sarah claims she paid her contribution last month but it never made it in. The treasurer says there's no evidence. Nobody saved the M-Pesa code. Now you have a full argument on your hands, the group's records are muddled, and friendships are in the balance.

This is not a rare problem. It is the chama dispute that could have been avoided if someone had written down one number: the unique M-Pesa transaction reference code.

Why the code matters more than the SMS

Every M-Pesa transaction generates a confirmation message with a unique transaction code, usually a 10-character string like QGH45JK9LM or SLK4H7R2T1. Safaricom says the transaction reference is the unique part, so that is the number staff should match. This is the proof that stays the same no matter whose phone the SMS lands on.

Many chama treasurers keep a WhatsApp spreadsheet or a handwritten ledger. They write down who paid, the amount, and maybe the date. But they often skip the transaction code. Why? Because it feels like too much detail, or the SMS arrived on someone else's phone, or everyone was in a hurry. Then three months later, when the numbers do not add up, nobody can prove which payment was which.

A unique 10-character alphanumeric reference ID (such as QGH45JK9LM) generated by Safaricom for tracking purposes is what makes a payment traceable. Always request an M-Pesa confirmation SMS and save it. Include the reference number in your sale agreement as proof of payment. This is true for chamas too.

What actually happens when the code is missing

A treasurer receives a payment to the chama's Paybill or group till number. An SMS arrives on someone's phone. The money lands in the account. But by the time the next meeting rolls around, nobody can remember whose payment it was, or the member who sent it has misplaced the SMS, or—worst of all—the SMS was sent to the group owner's phone, not the member's, so the member has no proof at all.

Now comes the version problem. Sarah says she sent 5,000. The treasurer says they only counted 4,800 last week. Did 200 get lost in M-Pesa fees? Did Sarah send a partial amount first and forget the rest? Or did the payment go to the wrong till? Most chamas operate on good faith and in the event of a dispute recovery becomes difficult.

Paper ledgers, handwritten counter books, physical cash collections and WhatsApp spreadsheets remain common, creating room for bookkeeping errors, delayed reconciliations, financial disputes and, in some cases, the collapse of groups. A single missing code turns a simple payment into a question mark that eats up trust.

How to keep a chama code record that actually works

Fix this on paper first. Your chama constitution—the written rules that govern the group—should say exactly what each member needs to record. The amount. The date. The phone number it was sent from. And the transaction reference code. That is four pieces of information, not forty.

The payment channel (the group account, paybill or till) and the reference each member uses should be named in your written rules. If the chama uses a Paybill, the constitution should say which one, and each member should use the same account reference so payments do not scatter across Till numbers or random accounts.

When someone pays, they send you a screenshot of the M-Pesa SMS—not because it is proof on its own, but because it contains the code you need to write down. They text the code to the treasurer or post it in the group chat. The treasurer records it against Sarah's name, the amount, and the date. That is the document that settles disputes later.

Through self-service channels (USSD *334# or mobile apps), you can request transaction histories going back up to 2 years (24 months). If a code ever goes missing, a member can dial *334# on their registered Safaricom line, select My Account, then M-PESA Statement and pull their own history. Then both of you can match the code against your records.

For groups with bigger pools or regular loans, Chamabora, the chama record-keeping app, handles this automatically. The app stores every payment reference, syncs with M-Pesa, and gives every member and the treasurer a clear view of who has paid and who has not. No spreadsheet. No missing codes. No argument that cannot be settled by checking the phone.

When the code is the only rope left

If your group ever needs to prove a payment to a bank, to a landlord, or to settle a serious dispute, a certified M-Pesa statement showing the unique transaction ID and recipient name provides conclusive proof of payment. The code is what Safaricom looks for when they investigate a claim that money was lost or misdirected. Without it, you have a story. With it, you have a fact.

Kenya's financial resilience is anchored by more than 300,000 grassroots savings groups that collectively manage an estimated KSh 300 billion. These chamas, many led by women, are some of the most influential, yet understated drivers of the informal economy. Most of these groups run on handshake agreements and trust. But trust dissolves the first time money goes missing and no one can prove where it was. A single code keeps that from happening.

Save the code. Write it down. Keep it. Do not treat it as an optional detail. It is the thread that holds the group together when everything else starts to fray.

Frequently Asked Questions

What if a member paid but the SMS went to someone else's phone?

They can still retrieve their own transaction history by dialling *334# on their registered Safaricom line, selecting My Account, and requesting their M-Pesa Statement. This shows all their outgoing payments with the codes. They can give the code to the treasurer as proof, and the treasurer can match it against the money that landed in the group account.

Do I need to keep the actual M-Pesa SMS, or just the code?

Just the code. The SMS is dense with personal information. Your chama constitution should require members to report the transaction code to the treasurer—a 10-character string—not to share their full SMS. This keeps the record clear and protects privacy. The code is your proof; the SMS is just how you get it.

What if the chama operates only in cash and does not use M-Pesa?

Your rules become even more important. Use a receipt book or a ledger where the treasurer writes down who paid, the amount, the date, and their signature (or thumbprint). Read it aloud at every meeting so everyone hears their name and balance. No digital code can replace a simple paper record read out loud in front of witnesses.

Can we use a verified Kenyan expert on Kaziiko to help us set up our chama constitution?

Yes. Business setup experts can help you draft a written constitution that names payment channels, codes, and dispute steps. This costs far less than fixing the mess when the chama falls apart.