WhatsApp Flows and M-Pesa: How Kenyan Businesses Are Getting Customers to Pay Without Leaving the Chat
WhatsApp Flows and M-Pesa: How Kenyan Businesses Are Getting Customers to Pay Without Leaving the Chat
A customer in Nairobi messages a shop on WhatsApp, picks a product, fills in their delivery details, and pays with M-Pesa — all inside the same conversation. No website, no app download, no switching screens. This is what WhatsApp Flows for payments looks like in practice, and it's quietly becoming one of the most useful WhatsApp business automation tools available to Kenyan companies in 2026.
If you run a business in Kenya and most of your customers already reach you on WhatsApp, this is worth understanding properly. It changes how you collect payments, confirm orders, and follow up — and it removes a lot of the back-and-forth that usually eats up a support team's day.
What a WhatsApp Flow Actually Is
A WhatsApp Flow is a structured, multi-step form that opens inside a chat. Instead of a customer typing "I want to order 2 bags of rice" and an agent typing back a list of questions one at a time, a Flow presents a clean screen: product selection, quantity, delivery address, and a payment step, all in one guided sequence.
For payments specifically, a Flow can end with an embedded M-Pesa prompt. The customer confirms the amount, gets an STK push on their phone, enters their PIN, and the payment is done — without ever leaving WhatsApp. For a business, that means the order and the payment land in the same place, at the same time, with no manual reconciliation.
Why This Fits Kenya So Well
Kenya has a fairly unique combination: M-Pesa handles the large majority of everyday non-cash transactions, and WhatsApp is where most people already spend their time chatting with businesses. Put those two together and a payment-enabled WhatsApp Flow isn't a novelty — it's just closing the gap between "I want to buy this" and "I've paid for this" in the channel customers already prefer.
Where it's showing up
A few realistic examples of how Kenyan businesses are starting to use this:
- A Nairobi-based insurance broker uses a Flow to collect basic risk information — vehicle details, cover type, dates — and lets the customer pay their premium via M-Pesa inside the same chat, cutting a process that used to involve phone calls and paperwork down to a few minutes.
- A supermarket taking WhatsApp orders lets customers build a basket through a Flow, confirm their delivery slot, and pay on the spot, instead of sending a photo of a handwritten list and waiting for someone to calculate the total.
- A private school sends termly fee invoices as a Flow with an embedded pay button, so parents can settle balances directly from the reminder message rather than visiting the school's accounts office.
None of these require the customer to install anything new. That's the appeal — the friction that usually kills conversion (a redirect to a payment page, a slow-loading site, a form that doesn't work well on a small screen) mostly disappears.
What This Means for Your WhatsApp Customer Support
Flows are a payments feature first, but they change support workload too. A lot of WhatsApp customer support in Kenya today is really just manual data collection dressed up as conversation — agents asking the same five questions before a sale can even happen. When a Flow handles that step automatically, your team is left with the messages that actually need a human: complaints, exceptions, and questions that don't fit a template.
That's also where AI comes in. Businesses that get a high volume of WhatsApp inquiries — order status, delivery timelines, "did my payment go through" — often pair Flows with an AI WhatsApp agent that can answer these automatically, day or night, and only hand off to a person when something genuinely needs judgment. Platforms like Supportal are built for exactly this kind of setup: they sit alongside your WhatsApp Business number, answer the repetitive questions instantly, and loop in a human agent when a conversation gets complicated.
Setting Up Flows: What to Know Before You Start
A few practical points for businesses considering this:
- You need the WhatsApp Business Platform (Cloud API), not the regular WhatsApp Business app. Flows aren't available on the free app.
- M-Pesa integration isn't automatic. You'll need to connect a payment provider that supports M-Pesa STK push into your Flow, either directly or through a WhatsApp business solution provider.
- Templates need approval. Like other WhatsApp business messaging, the Flow's structure typically goes through Meta's review before it can be sent to customers.
- Design for a small screen. Keep each step short. A Flow with too many fields on one screen defeats the purpose of reducing friction.
| Feature | Traditional Payment Link | WhatsApp Flow with M-Pesa |
|---|---|---|
| Where the customer pays | External website or payment page | Inside the WhatsApp chat |
| Steps to complete | Click link, load page, enter details, confirm | Answer a few in-chat prompts, confirm M-Pesa PIN |
| Drop-off risk | Higher — link may load slowly or feel untrustworthy | Lower — customer never leaves a familiar app |
| Order and payment records | Often need manual matching | Captured together in the same conversation |
| Best suited for | One-off invoices, simple links | Repeat orders, bookings, fee collection |
Neither approach is wrong — a simple payment link is still fine for a one-time invoice. Flows earn their setup cost when you're collecting payments repeatedly, from the same base of WhatsApp customers, week after week.
Where AI Customer Support Fits In
The businesses getting the most out of this aren't just adding a payment button — they're rethinking the whole WhatsApp conversation as a system. A Flow handles the structured part (order details, payment). An AI WhatsApp agent handles the conversational part (questions before and after the sale). A human agent handles the exceptions. Supportal is one of the tools businesses use to cover that middle layer — answering routine WhatsApp questions automatically so a Flow-based payment process doesn't stall on "how much is delivery" or "is this still in stock" while a customer waits for a reply.
Frequently Asked Questions
What is a WhatsApp Flow?
It's a structured, multi-screen form that opens inside a WhatsApp conversation, used for things like bookings, orders, applications, and payments — without sending the customer to an outside website.
Can I accept M-Pesa payments directly through WhatsApp?
Yes, if you're on the WhatsApp Business Platform (Cloud API) and have a payment provider connected that supports M-Pesa STK push inside a Flow.
Do I need the WhatsApp Business app or the API to use Flows?
Flows require the WhatsApp Business Platform (Cloud API). They are not available through the standard WhatsApp Business app used by most small shops.
Is this only useful for large businesses?
No. Small businesses that take repeat orders or recurring payments — schools, clinics, subscription sellers, service providers — often benefit the most, since Flows remove manual steps that otherwise fall on one or two staff members.
Can AI handle the questions customers ask before they reach a payment Flow?
Yes. An AI WhatsApp agent can answer common pre-sale questions — pricing, availability, delivery time — automatically, so customers reach the payment step faster and human agents only step in when needed.
Conclusion
WhatsApp Flows paired with M-Pesa are a genuinely useful fit for how Kenyan businesses and customers already operate — chatting on WhatsApp, paying with M-Pesa, and expecting both to happen without friction. For businesses receiving a steady volume of orders, bookings, or fee payments through WhatsApp, this is worth setting up properly rather than continuing to manage payments and conversations as separate, manual steps. Combine it with automated WhatsApp replies for the questions that come before and after a payment, and the whole customer journey — from "how much is this" to "paid, thank you" — happens in one place.
