SHOW! Safaricom Has Fixed One Kenyan Absurdity. Unfortunately, We Have a List.

The room was called Kaptagat.

Nobody outside Safaricom quite knew why.

Those who knew the CEO knew.

Peter Ndegwa runs. Properly. The kind of running where a man voluntarily wakes up before sunrise and covers kilometres for no apparent reason, then arrives at the office refreshed. A suspicious personality trait, certainly, but useful when you are responsible for a company whose customers can generate a national emergency before breakfast.

So somewhere inside Safaricom headquarters, let us place our brightest minds in Kaptagat.

Engineers.

Product managers.

UX people.

Data people.

Cybersecurity people.

One lawyer, because innovation without a lawyer is simply evidence being prepared for court.

And at the head of the table, the CEO.

On the screen behind him is the problem they have finally solved.

For years, Kenyans have been paying through one of the most sophisticated mobile-money systems on earth only to finish the transaction with a primitive ceremony.

You pay.

The money travels electronically through advanced telecommunications infrastructure.

Servers authenticate it.

Systems process it.

Databases record it.

Cryptographic things happen that ordinary citizens wisely do not ask about.

Milliseconds later, the merchant has the money.

Then the cashier looks at you and says:

“Show Confirmation Message.”

And apparently all that technology becomes irrelevant.

You must now produce the phone.

The engineers in Kaptagat have fixed this.

The new feature separates what the cashier actually needs from what the cashier has absolutely no business knowing.

Transaction confirmed?

Yes.

Amount?

Yes.

Merchant?

Yes.

Transaction code?

Yes.

Customer's remaining M-PESA balance?

Mind your business.

The CEO looks around the room.

“Team, this is good.”

Everybody sits slightly taller.

Engineers do not receive enough praise. Mostly because when everything works nobody notices them, and when anything fails thirty million people suddenly know where they work.

Today, however, they have earned it.

“You've solved a real customer problem,” the CEO continues. “Simple. Practical. Privacy-conscious. Well done.”

Small smiles.

One engineer allows himself the dangerous luxury of leaning back.

The lawyer nods in that careful legal way that technically commits him to nothing.

There is satisfaction in the room.

One final item remains.

The product needs a name.

And this is where highly intelligent people become dangerous.

“Suggestions?”

A hand rises.

“M-PESA Privacy Shield.”

The room considers it.

It sounds less like a payment feature and more like something sold by an insurance agent standing outside Naivas.

Another hand.

“SecureView.”

Silence.

Very international.

Could be cybersecurity.

Could be CCTV.

Could be prescription glasses.

Next.

“M-PESA SafeReceipt.”

Technically accurate.

Emotionally deceased.

Someone from Brand adjusts their glasses.

“What if we call it PrivPay?”

The CEO looks towards the ceiling briefly.

Not dramatically.

Just enough to check whether assistance is available from a higher authority.

Another engineer joins in.

“Hakikisha Private.”

“No.”

“Hakikisha Plus?”

“No.”

“Hakikisha X?”

“Why is everything X now?”

Nobody answers because nobody actually knows.

At technology companies, adding X to a product name means either artificial intelligence is involved or the naming meeting has gone on too long.

Someone near the back has been thinking very hard.

“M-PESA Whisper.”

Now there is movement in the room.

Not approval.

Physical discomfort.

“Whisper?”

“Yes. Because the information is discreet.”

“So the customer's money is whispering?”

“Sort of.”

“What exactly is it whispering?”

The idea dies peacefully.

Another hand shoots up.

“ShowSafe.”

Brand writes it down.

Then immediately crosses it out.

“Ficha Balance.”

A few people laugh.

Actually...

No.

Imagine the advertising campaign.

FICHA BALANCE. LIVE YOUR TRUTH.

Half the country would assume Safaricom had launched a feature specifically for married people.

More names come.

M-PESA Confirm.

Too obvious.

SmartReceipt.

Too generic.

PayProof.

Sounds like litigation.

SafeShow.

Sounds like a children's programme.

ConfirmMe.

Sounds needy.

Receipt360.

Now we are just naming consulting firms.

Thirty minutes pass.

The greatest mobile-money minds in East Africa have defeated data exposure but are being defeated by a noun.

Whiteboards fill.

Coffee disappears.

The head of Brand has written three columns:

TRUST. PRIVACY. SIMPLICITY.

Underneath them are twenty-seven words nobody trusts, nobody understands and none of which are simple.

The CEO looks at his watch.

Somebody suggests M-PESA Clear.

Another suggests M-PESA ClearView.

The lawyer points out there may already be a company called ClearView.

The cybersecurity man says something about trademarks.

Someone googles something.

The meeting begins entering that stage where perfectly decent people start suggesting names like PesaNova.

This is how products end up sounding like medication.

Then the door opens.

The CEO's personal assistant appears.

She is moving quickly.

Not running. This is Kaptagat; running here would create expectations.

She has a phone in her hand.

There is urgency on her face.

The room turns.

“Boss...”

Ndegwa looks up.

“Uko na ujumbe kutoka State House.”

Silence.

One second.

Perhaps two.

Then something happens.

You can almost hear it.

Not the State House message.

The other message.

The one that has just travelled simultaneously through the heads of thirty people who have spent half an hour murdering the English language on a whiteboard.

Ujumbe.

The Head of Product turns slowly towards Brand.

Brand looks at UX.

UX looks at the engineers.

An engineer reaches for the marker.

The CEO raises one finger.

“Wait.”

Everyone waits.

He repeats it.

“Ujumbe.”

Someone says:

“Message.”

“Yes.”

Another voice:

“Jumbe.”

Now the room changes.

You know when a name is wrong because everybody wants to improve it.

You know when a name is right because suddenly nobody has anything useful to add.

Jumbe.

Short.

Kenyan.

Familiar.

It says precisely what the thing is.

A message.

Not a platform.

Not an ecosystem.

Not an omnichannel privacy enablement solution.

A message.

The CEO looks at the screen.

Then at the whiteboard full of SecureView, PrivPay, Receipt360, M-PESA Whisper and several other crimes against language.

He looks back at his assistant.

“What did you say?”

She is slightly confused now.

“Boss, nimesema uko na ujumbe kutoka State House.”

“No, no. That part.”

“Ujumbe?”

There it is again.

Somewhere, a branding budget quietly returns to shareholders.

“Jumbe,” the CEO says.

The Head of Product smiles.

The engineers smile.

Even Legal smiles, which should tell you how serious the moment is.

And just like that, after weeks of engineering, privacy architecture, transaction logic and what we shall assume were several thousand lines of code, one of Safaricom's newest payment features acquires its identity because somebody from State House wanted to speak to the boss.

The assistant is still standing at the door.

She has no idea she has just completed the product-development cycle.

“Boss... State House?”

“Yes, yes. One minute.”

Because innovation is important.

But State House is State House.

And so Jumbe was born.

At least that is how it happened in our version of events.

But the name is almost beside the point.

The interesting thing is what Safaricom had finally decided to kill.

A small Kenyan humiliation.

A ritual so common that we stopped noticing how absurd it was.

For years, there was one word capable of turning a private financial transaction into a public exhibition.

You could hear it at supermarkets.

Petrol stations.

Restaurants.

Pharmacies.

Hardware shops.

Anywhere M-PESA and suspicion met across a counter.

You paid.

You waited.

Then came the command.

Not “thank you”.

Not “payment received”.

Not even “could I please verify the transaction?”

Just:

SHOW MPESA MESSAGE.

Kenya is a country where privacy is very important.

We know this because we have a Data Protection Act.

We have a Data Commissioner.

We have privacy policies.

We have cookie notices.

We have conferences about personal data where serious people sit under blue lighting and explain consent.

Then you go downstairs, buy a bottle of water with M-PESA and a cashier says:

“SHOW MPESA CONFIRMATION MESSAGE.”

That's it.

SHOW.

Not, “Excuse me, may I confirm that your payment went through?”

No.

We are not doing diplomacy.

SHOW. NIONYESHE!

It is a magnificent Kenyan word because in this context it is not even a request.

It is a command.

The cashier doesn't need to identify what you should show because both of you understand the ceremony.

You pull out the phone.

Unlock it.

Find the message.

Increase brightness.

Tilt screen towards officer commanding transaction verification.

And now a person you met approximately nine seconds ago is reading your financial correspondence.

Transaction code.

KSh4,280.

Merchant name.

Time.

And, depending on the message, there it is.

Your balance.

Wonderful.

You wanted toothpaste and cooking oil.

You received a means test.

There is something beautifully irrational about this.

We built digital money so that we would not have to physically exchange things.

No notes.

No coins.

No cheques.

No envelopes.

Money became invisible.

It flew through telecommunications infrastructure, bounced through secure systems and arrived at the merchant almost instantaneously.

Then, at the final stage of this astonishing technological achievement, we said:

“Now give me your phone OR show me the confirmation code.”

What was the point?

We digitised the payment and analogue-ised the proof.

And “show Mpesa Confirmation” could be a dangerous moment.

Suppose you are on a date.

You have spent the evening explaining that things are going very well.

Not boasting.

Just communicating momentum.

You have mentioned “portfolio”.

You have casually referred to “the market dynamics”.

You have complained about Treasury Bills & bonds yielding less than expected.

You have used the sentence:

“I’m looking at a few opportunities.”

Bill arrives.

KSh6,750.

You pay.

The waiter approaches.

“Show Mpesa Confirmation code.”

The screen says your balance is KSh83.40.

Now everybody is looking at you differently.

Your date is suddenly very interested in dessert prices.

The waiter starts calling you “bro, uko sawa?"

Even the restaurant music sounds judgemental.

The opportunities, apparently, are still being looked at.

And God forbid the balance goes the other direction.

Maybe you have KSh313,842 sitting there.

Now the cashier knows.

The waiter knows.

The gentleman collecting empty bottles is passing slowly.

A complete stranger has discovered that perhaps you can, in fact, “help kidogo”.

You walked in to purchase lunch.

You accidentally published unaudited financial results.

Safaricom has now intervened.

And credit where credit is due, this is clever.

Its Split Notifications feature gives customers at participating merchants a second notification called Jumbe. That message is designed to prove that the payment happened without showing the customer's M-PESA balance, full name or full phone number.

It gives the transaction details that matter: amount, merchant, transaction code, date and time. Instead of your entire identity, it includes a JumbeID made from initials and the final two digits of the phone number.

In other words, Safaricom appears to have asked the question we should probably have asked fifteen years ago:

What exactly does the cashier need to know?

Did KSh4,280 arrive?

Yes?

Good.

Transaction complete.

The cashier does not need your biography.

The cashier does not need your balance.

The cashier does not need enough information to begin estimating whether you qualify for a chama loan.

This sounds obvious now.

Most good ideas do.

Before somebody invents the umbrella, everyone is wet for 4,000 years saying, “This is just what happens when it rains.”

Then one fellow says:

“What if we put something over our heads?”

Genius.

Safaricom has gone further.

A business can nominate employees to receive their own payment notifications, showing the amount, transaction reference and JumbeID. That means staff can confirm payments without needing access to the business owner's wider M-PESA information. The owner still receives the normal message.

This is the interesting part.

The customer needs one piece of information.

The cashier needs another.

The business owner needs another.

Finance needs another.

For some reason, technology spent years behaving like an African family WhatsApp group.

Everybody gets everything.

Wedding announcement?

Everybody.

Funeral contribution?

Everybody.

Political conspiracy forwarded at 4.13am?

Everybody.

Good systems eventually learn boundaries.

The cashier needs confirmation.

Finance needs reconciliation.

The owner needs control.

The customer needs a receipt.

Nobody needs to know whether Mwangi has KSh327.50 remaining until payday.

That is between Duncun, Safaricom and the Almighty.

Now, I have one complaint.

Safaricom has solved the problem of the M-PESA message by giving us...

another message.

You have to admire telecommunications companies.

Only a telecom operator can hear:

“There are too many messages.”

And respond:

“We understand completely.

Here is another message.”

At participating merchants the customer can receive the normal M-PESA confirmation and the Jumbe receipt.

Some customers may also have a bank alert.

So one purchase of bread can now receive more media coverage than a county budget.

M-PESA: You paid.

Jumbe: You definitely paid.

Bank: Something has happened.

Cashier: Show.

Wait.

Wasn’t the entire point to kill that last fellow?

Because that is where Safaricom should eventually take this.

Jumbe makes SHOW safer.

Excellent.

Now kill SHOW.

With kindness.

Thank it for its service.

Give it a retirement package.

Hold a small ceremony.

Because if the merchant has received the money, why should I be the merchant's payment-verification infrastructure?

Think about this.

The supermarket has a till.

It has a computer.

It has internet.

It has an ERP system.

It has cameras watching me from seventeen angles in case I steal chewing gum.

But when money arrives through one of the world's most celebrated mobile-money networks, suddenly the supermarket becomes technologically shy.

“Can we see your phone?”

No.

You see your system.

That is why you bought it.

And this is where Safaricom has made a strategic mistake.

They solved one everyday Kenyan irritation.

Never do that.

Because once Kenyans discover that something irritating is not actually ordained by God, we begin asking questions.

So yes, Safaricom deserves credit.

Jumbe fixes a small indignity that millions of Kenyans had quietly accepted as part of paying for things. That matters. Good fintech is often not about inventing a new universe. Sometimes it is simply noticing that the current universe contains something ridiculous.

And now that Safaricom has demonstrated it is watching how Kenyans actually use M-PESA, wananchi would like to leave a few items on the engineers’ desk.

1. Solve “Boss, Usitume Kwa Hii Number. Iko na Fuliza.”

Safaricom knows this sentence.

Every Kenyan knows this sentence.

You ask somebody:

“Number?”

They send one.

You prepare to transfer.

Then, with the urgency of somebody stopping a surgical procedure:

“Boss! Boss! Usitume kwa hiyo!”

Why?

“Iko na Fuliza.”

Ah.

The money has creditors waiting at the border.

A second number arrives.

“Use hii.”

Sometimes it belongs to the recipient.

Sometimes the wife.

Sometimes a brother.

Sometimes somebody called Moraa Shop whom you have never met and are now expected to entrust with KSh7,500 on the strength of one WhatsApp message.

Surely Safaricom's engineers can at least study this uniquely Kenyan payment choreography.

Could a customer, subject to all the necessary safeguards, nominate another verified receiving line or preferred destination before money is sent?

Something elegant.

Mwangi has requested that this payment be received on his alternate verified M-PESA number ending 42. Continue?

Done.

No deleting numbers.

No “ignore ile ya kwanza”.

No discovering three minutes later that you sent the money to the Fuliza line anyway.

We appreciate, of course, that Fuliza may have a different opinion.

Fuliza has been standing at the gate patiently.

Fuliza has calculations.

Fuliza would also like to eat.

So perhaps Safaricom cannot solve this one without starting an internal civil war between the innovation department and the lending department.

Still.

We raise it on behalf of the people. - Anyway, hamjui jokes!

2. Kill “SHOW” Completely

Jumbe makes showing safer.

Excellent.

The better destination is needing to show nothing.

If the merchant’s system received KSh3,450, the merchant’s system should know it received KSh3,450.

Customers should not be unpaid members of the reconciliation department.

3. Give the Payment a Memory

M-PESA can tell me I paid KSh8,400.

Three months later it cannot tell me whether that KSh8,400 bought groceries, a microwave or a television my household has mysteriously denied ever purchasing.

Attach proper digital receipts where merchants support them.

Items. VAT. Warranty. Merchant. Transaction.

We digitised the money. Let us digitise remembering what the money bought.

4. Refund the Transaction, Not My Phone Number

A merchant receives money from a known transaction.

You return the product.

Suddenly:

“Nipe number.”

Why?

The transaction already knows where it came from.

Subject to the right controls, let merchants refund the original payment directly instead of turning every refund into an oral examination in telephone-number accuracy.

5. Build “Pay for Someone” Properly

Kenya mastered:

Send money to a person.

The next frontier may be:

Pay for something for a person.

Mother at pharmacy. Child at bookshop. Driver at petrol station. Employee at hardware.

Let the merchant request the exact amount and let the person at home approve it.

Because once you send KSh5,000 for medicine and the medicine costs KSh3,800, the remaining KSh1,200 occasionally develops constitutional independence.

6. Split the Restaurant Bill Before Friendships Collapse

Six people eat.

One had coffee.

One ate steak.

Three insist they only “tasted” the fries.

Nobody ordered the sparkling water.

Someone has already sent Carol KSh2,000 for reasons unrelated to dinner.

Give us a proper merchant-linked split-bill function.

This may save more relationships than couples therapy.

7. Make Reversals Less Like Reporting a Missing Person

Sending money to the wrong number produces a special Kenyan cold sweat.

You stare at the confirmation message.

You reread the number.

You briefly consider relocating.

There are fraud and settlement risks that mean reversal can never be completely casual, but the safest possible guided process should be obvious, fast and visible inside the transaction itself.

Panic is not a user interface.

8. Fix Merchant Names That Require Faith

You are paying a business you know as Mama Njeri Hardware.

Hakikisha displays:

KAMITHI GENERAL ENTERPRISES 2014 LTD.

Now the customer must decide whether to trust capitalism.

Merchant identity needs to be as recognisable as possible at the point of payment.

Because “Hakikisha” works better when there is actually something to hakikisha.

9. Help Small Businesses Reconcile Without Becoming Accountants

Many small merchants do not need another dashboard containing nineteen charts.

They need:

What came in?

From whom?

For what?

What is missing?

What was refunded?

What did I make today?

Turn transaction data into simple business information ordinary merchants can actually use.

10. And Then There Are Problems Safaricom Cannot Code Away

Someone will still reach the front of a supermarket queue before opening M-PESA.

Someone will still ask:

“Till ni gani?”

despite the Till number being printed in letters large enough to be visible from Uganda.

Someone will still send KSh8,000 to a relative for one specific purpose and discover that the money has developed a broader development agenda.

Someone will still insist on forwarding a screenshot instead of waiting three seconds for confirmation.

And somebody, somewhere, will receive:

“Please send me 2k. Emergency.”

then discover the emergency was nyama choma.

These are not software bugs.

These are Kenyans.

Safaricom can build better rails.

It cannot control all the passengers.

And perhaps that is the useful lesson in Jumbe.

Some payment frictions are technological.

Some are institutional.

Some are behavioural.

The best fintech companies learn to tell the difference.

Safaricom looked at one very ordinary Kenyan ritual and asked a very useful question:

Why are we still doing this?

Jumbe is a good answer.

More questions like that, please.

The country has a list.

Disclaimer: The opening scene set inside Safaricom’s fictional “Kaptagat” think-tank room, including the dialogue, naming discussion and the imagined State House message, is entirely a work of satire and creative imagination. It is not intended to describe an actual meeting, conversation or account of how Jumbe was named. The product details and broader observations in the feature are discussed separately from that fictional scene.