How do I charge monthly subscriptions with M-Pesa?

By Bonaventure Ogeto, Founder and CEO, Mctaba Labs
Published

The short answer

M-Pesa does not let a business pull money every month the way a card does. You have four options: send a PIN prompt on each due date, have customers pay a Paybill with an account number, set up an M-Pesa Ratiba standing order the customer approves once, or bill a card through a gateway. Launch with prompts and reminders.

When a streaming service renews, nobody at the company asks you for anything. Your card is charged, you get an email, and the service carries on. Founders plan their revenue around that picture: sign a customer once, collect every month without lifting a finger.

M-Pesa was not built that way. Every ordinary M-Pesa payment needs the customer's PIN at the moment of payment. If your plan assumes money will arrive by itself each month, the plan has a hole in it. The good news is that the hole can be closed, with the right mix of prompts, reminders and, later, standing orders.

Can M-Pesa charge a customer automatically every month?

Not in the card sense. A business cannot store a customer's M-Pesa details and take money whenever a bill falls due.

What exists instead is a standing order that the customer approves. Safaricom calls it M-Pesa Ratiba. The customer agrees once to a fixed amount, a frequency and an end date, enters their PIN, and M-Pesa makes those payments on schedule. It is automatic after the first approval, but it is the customer's instruction, not your permission to pull.

That difference shapes everything below.

What are my options for monthly billing?

Four, and you will probably combine two of them.

Option What the customer does What you need Where it fails
Prompt on the due date Enters their PIN each period when a prompt appears A Till or Paybill connected to M-Pesa Express, directly or through a gateway Phone off, low balance, prompt ignored
Paybill with an account number Pays your Paybill themselves each period A Paybill and a clear account number for each subscriber Customer forgets, or types the wrong account
M-Pesa Ratiba standing order Approves once with their PIN The customer sets it up alone, or you create it through Daraja under a commercial agreement with Safaricom Low balance on the day. No automatic second attempt
Card through a gateway Enters card details once A gateway account that supports card subscriptions Many customers have no card, or do not trust it online

How does the prompt-and-reminder method work?

Your product keeps a due date for each subscriber. A few days before it, the product sends a reminder. On the day, it sends an M-Pesa prompt to the subscriber's phone and they enter their PIN. If the payment succeeds, the product extends their access by one period.

The prompt uses M-Pesa Express, the same service that an online shop uses at checkout. It needs no separate commercial agreement beyond the normal go-live for your Till or Paybill, which is why this is the right place for a new product to begin.

Send the prompt when the customer is likely to be holding the phone. A prompt that arrives at 3 am times out unanswered. Always pair it with a message that contains your Paybill or Till number and the account number, so a customer who misses the prompt can still pay.

How does M-Pesa Ratiba work for a business?

There are two routes into Ratiba, and they are very different amounts of work.

The customer sets it up. Any M-Pesa customer can create a standing order to a Paybill or a Till from *334# or the Ratiba mini app in the M-Pesa app. They choose the amount, the dates and the frequency. You need nothing new: you only have to tell subscribers this is possible and give them the exact details to enter. Safaricom's FAQ says the customer pays KSh 5 per Ratiba transaction on top of the normal M-Pesa charge, as of 19 November 2026.

Your product sets it up. Safaricom's Daraja platform lists an M-Pesa Ratiba interface for "programmatic creation and management of M-PESA standing orders for recurring collections", and names subscription billing as one of its uses. The subscriber enters the details inside your app or site, receives an M-Pesa prompt, and approves with their PIN. If they have never used Ratiba, they are opted in as part of that step.

The business route comes with conditions that Safaricom states on the same page:

  • It is a commercial service. You test first, then write to Safaricom's API support team, hold a commercial discussion and sign an agreement before it is switched on.
  • Any registered company can apply.
  • As of 19 November 2026, M-PESA Ratiba charges a flat KSh 5 per successful automated transaction, on top of the standard M-PESA transaction fee for that payment type. Check the current Ratiba tariff on the Daraja portal before you build pricing around it.
  • The available frequencies run from daily and weekly through monthly, quarterly and yearly.

What happens when a payment fails?

This is the question that decides whether your subscription revenue is real.

With a prompt, failure is immediate and visible: the result comes back as cancelled or timed out, and your product can react.

With Ratiba, Safaricom's FAQ is specific. If the wallet does not hold enough money, the transaction fails. Fuliza does not cover it. The customer is not penalised. And once the scheduled time has passed, the system does not try again by itself. The customer can still pay manually.

So a standing order reduces forgetting, but it does not remove chasing. Around the end of the month, when balances are low, some orders will fail. Your product needs the same safety net either way: detect the missed payment, message the customer, and offer a one-tap way to pay now.

Two smaller limits are worth knowing. A Ratiba standing order cannot be edited after it is created, so a price change means deleting it and creating a new one. And Ratiba does not support payments to Pochi la Biashara, which is one more reason to collect into a Paybill or Till.

Should I offer card billing as well?

Yes, as a second option, if any of your customers hold cards or live outside Kenya.

Cards do what founders imagine subscriptions doing. After a first successful payment, a gateway can charge the same card again without the customer being present. Paystack's documentation says this works for cards in all its markets, and that its Subscriptions feature, which manages the billing cycle for you, supports cards. The same company's help page says recurring payments are not currently possible on its Pay with M-Pesa channel.

Do not make cards the only option for a Kenyan audience. Offer "pay monthly by M-Pesa" and "pay by card and renew automatically" side by side, and let customers pick. If your developer is building this on a gateway, the walkthrough on building a Kenyan subscription billing system shows how the pieces fit.

How should the product treat a subscription?

As prepaid access, not as a debt.

A card subscription assumes the customer owes you each month and you collect. An M-Pesa subscription works better the way airtime does: the customer has paid up to a date, and when that date passes without a payment, access pauses until they pay again. Nobody is in arrears and nobody needs to be chased for old months.

Ask your developer for these five things:

  1. A paid-until date for every subscriber, extended by each confirmed payment.
  2. A short grace period, such as three days, before access pauses.
  3. Clear statuses: active, due, in grace, paused. Staff should see them on one screen.
  4. Payments matched by account number or by the prompt's reference, never by name.
  5. Plans longer than a month. A three or twelve month option at a small discount means fewer collections to get wrong.

What should the reminders say?

Keep them short, specific and easy to act on. Here is a sequence you can copy. The plan and the numbers are examples.

Three days before

Hi Achieng, your bookkeeping plan (KES 1,000) renews on 5 June. We will send an M-Pesa prompt to this number at 10 am that day. Nothing to do until then.

On the day, sent with the prompt

Hi Achieng, we have just sent an M-Pesa prompt for KES 1,000. Enter your PIN to renew to 5 July. Missed it? Pay to Paybill 000000, account DB1042.

One day after a missed payment

Hi Achieng, we did not receive your renewal yesterday. Your account stays open until 8 June. Reply PAY and we will send the prompt again, or use Paybill 000000, account DB1042.

When access pauses

Hi Achieng, your bookkeeping plan is paused. Your records are safe. Pay KES 1,000 any time to pick up where you left off: Paybill 000000, account DB1042.

The messages leave out three things on purpose: threats, late fees and guilt. A paused customer who feels respected comes back.

What would I do for a new product?

Launch with prompts, reminders and a Paybill account number as the fallback. Sell a longer plan next to the monthly one. Tell subscribers they can create their own Ratiba standing order if they prefer not to think about it.

Then watch one number for three months: of the subscribers due each month, how many pay within the grace period. If that share is high, you may never need more. If forgetting is clearly the problem and you have a few hundred subscribers, that is the moment to approach Safaricom about creating Ratiba standing orders from inside your product.

Key takeaways

  • Treat an M-Pesa subscription as prepaid access. The customer pays for a period, and access ends when the period does.
  • The cheapest reliable setup is a reminder before the due date and a PIN prompt on the day.
  • M-Pesa Ratiba is Safaricom's standing order. A customer can create one alone, or a business can create it through Daraja under a commercial agreement.
  • A Ratiba payment fails if the wallet is short and is not retried, so you still need reminders and a manual way to pay.
  • Paystack's subscription tools bill cards, not M-Pesa. Offer cards as a second option for customers who have them.
  • Selling three, six or twelve months at once removes most of the billing problem.

Frequently asked questions

Is there an auto-debit for M-Pesa?
The closest thing is M-Pesa Ratiba, Safaricom's standing order service. The customer approves the order once with their PIN and M-Pesa then pays the set amount on the set dates without asking again. It only succeeds when the wallet holds enough money on the day.
Can I use Paystack subscriptions with M-Pesa?
Not for automatic renewals. Paystack's documentation says its Subscriptions feature supports cards, and its help page says recurring payments are not currently possible on the Pay with M-Pesa channel. You can still collect each M-Pesa payment through Paystack by sending a new prompt every period.
Which is better for subscriptions, a Till or a Paybill?
A Paybill, in most cases. Each payment arrives with an account number, so your system knows which subscriber paid even when they pay from a different phone. A Till works if every payment is started from a prompt sent by your own product.
What happens if a subscriber's M-Pesa balance is too low on the due date?
Nothing is taken. A prompt simply fails, and Safaricom says a Ratiba standing order fails without a penalty and without another automatic attempt. Your product has to notice the missed payment, tell the customer, and give them an easy way to pay later.
Should I charge monthly or annually?
Offer both if you can. Monthly is easier to say yes to, because the amount is smaller. A discounted three or twelve month option means fewer collections and fewer missed payments, and it brings cash in earlier.

Sources

  1. M-Pesa Ratiba (standing order API documentation), Safaricom Daraja developer portal. Checked on 19 November 2026.
  2. M-PESA Ratiba, Safaricom. Checked on 19 November 2026.
  3. M-PESA Ratiba, frequently asked questions, Safaricom. Checked on 19 November 2026.
  4. M-Pesa Express Simulate (Lipa na M-Pesa Online API documentation), Safaricom Daraja developer portal. Checked on 19 November 2026.
  5. M-PESA Paybill (Business Paybill), Safaricom. Checked on 19 November 2026.
  6. Subscriptions, Paystack developer documentation. Checked on 19 November 2026.
  7. Recurring Charges, Paystack developer documentation. Checked on 19 November 2026.
  8. Pay with M-PESA, Paystack support. Checked on 19 November 2026.