How ISPs Automate Monthly Subscription Renewals with Mobile Money

Monthly renewals are the steady cash flow an internet service provider depends on, and they’re also where most of the leakage happens. A customer who pays on the 3rd is fine. A customer who pays on the 14th after two reminders and a suspension costs you a week of service, a support call, and sometimes the account altogether. In most cases the customer hasn’t refused to pay. The reminder got lost, the Paybill number was buried in an old text, or nobody noticed the payment had landed until the next morning.

This guide walks through how ISPs can automate the renewal cycle with mobile money: scheduled reminders, a clear way for customers to pay, and an automatic reconnection once the payment arrives. It’s written for ISP owners and operations managers running monthly fibre or wireless plans in Kenya, and it’s specific about what the system does and what the customer still has to do.

The ISP renewal cycle, step by step

Every subscriber has a billing date, a due date, and a paid-until date. Most ISPs use the same cycle without naming it, so it helps to lay it out.

  1. Billing date: The day a new billing period starts and the invoice is raised.
  2. Reminder: An SMS goes out a set number of days before the due date. Three days before is a common starting point.
  3. Due date: The day the subscriber’s current period ends.
  4. Grace period: A short window after the due date where the service stays on. Two to three days covers most normal delays.
  5. Suspension: If no payment has arrived by the end of the grace period, access is cut.
  6. Reconnection: When payment arrives, the account is reactivated and the paid-until date moves forward.

Most of the revenue risk sits in steps 2 to 5. A reminder that arrives too late, or a grace period that’s too short or too long, shapes how many subscribers pay on time without any change in their willingness to pay.

How renewal reminders work

Your billing system owns the schedule. It knows each subscriber’s due date, so it sends the reminder SMS at the lead time you choose, and each reminder carries a way to pay: your Paybill number and the subscriber’s account reference, or a payment link the subscriber taps to renew. If you prefer email, an IntaSend payment request emails the customer a link for a specific amount and can resend reminders automatically every 1, 2, 3 or 7 days.

The subscriber is not charged without acting. Every billing period needs a customer action, which is what keeps the process clear for both sides. Once they pay, IntaSend can text them a receipt using your own SMS template, so the confirmation comes from your business name.

This matters for how you set up your customer communication. A reminder works best when it’s short, sent at a consistent time of day, and clearly tied to one amount and one period. A subscriber who sees “your Home 20 Mbps plan renews on the 10th, KES 1,000” is more likely to pay than one who sees a generic notice with no amount.

Subscribers can renew in several ways, and it’s worth offering more than one because they suit different people.

Paybill

The subscriber goes to M-Pesa, enters the Paybill number from the reminder, and uses the account reference shown. This suits customers who already pay bills on M-Pesa and want a familiar flow. The reference matters: the payment has to be matched to the right subscriber, so the reference shown in the reminder should be the exact account number your billing system expects. A typo here is the most common cause of an unmatched payment.

The subscriber taps a link in the SMS and completes the payment from there. This suits customers who are less comfortable with Paybill numbers, and it’s also useful when someone pays on behalf of another household or business. Links make the renewal a single tap for most subscribers.

M-Pesa prompt (STK Push)

Your system sends a payment prompt straight to the subscriber’s phone with the amount filled in, tagged with a reference for that subscriber and period. They only enter their PIN, so there is nothing to mistype. Our comparison of M-Pesa Paybill vs STK Push for ISPs covers the trade-offs in detail.

None of these options needs the customer to type a long account number if the reminder is set up properly. The main thing for an ISP is to test each path with a real subscriber account before rolling it out.

Reactivation when the payment arrives

Once a payment is made, the system needs to know about it quickly and act on it correctly. IntaSend sends a webhook to your billing system as soon as a payment changes state, so activation is automatic rather than waiting for someone to check a dashboard. Your system hears about every completed or failed payment as it happens.

The reactivation logic looks like this:

  1. The webhook arrives with the payment state.
  2. Your system checks that the state is COMPLETE. Anything else is not a renewal.
  3. It matches the payment to the subscriber using the reference that was sent (api_ref for prompts and links, or the Paybill account reference).
  4. It checks that the amount and currency are what was expected.
  5. It moves the paid-until date forward by one billing period.
  6. It reconnects the account, or lifts the suspension if one was applied.

Two details matter here. First, webhooks can be delivered more than once or out of order, so your handling should be idempotent: processing the same payment twice must not extend the paid-until date twice. Second, your endpoint should respond quickly and do the heavier work in the background, so the reconnection doesn’t wait on a slow database write.

Handling missed periods

Not every renewal arrives on time, and the system needs a clear rule for what happens next. A sensible sequence looks like this:

  • Reminder before due date: the first message, with the amount and the renewal options.
  • Due date reminder: a second message on the day, for subscribers who haven’t paid.
  • Grace period: service stays on for a short, defined window. Use it to recover late payers without cutting them off.
  • Suspension: if the grace period ends with no payment, access is cut and a final message goes out.
  • Reconnection on payment: a late payment restores access within the time it takes the webhook to arrive and your system to process it.

The grace period is a business decision, not a technical one. Too short and you cut off customers who were about to pay. Too long and you carry unpaid service without income. Most ISPs find that a few days covers normal delays, such as a phone running out of credit or a customer travelling. Your own bad debt figures are the best guide, so review them after the first two billing cycles. Our guide to reducing late payments for ISPs shows how to set the grace period from your own data.

Suspension itself should be reversible. A subscriber who pays on the 12th and reconnects that afternoon should not be treated as a new customer, and their history, router configuration, and plan should stay intact.

What automated renewals do to your collections

Automating renewals changes three things you can measure.

  • Collection timing: Payments that arrive within the due date and grace period replace the long tail of late payments. Track the share of subscribers who renew before the due date, not only the total collected each month.
  • Bad debt: Fewer subscribers reach suspension, so fewer accounts sit unpaid for weeks. The number to watch is the balance carried into the next billing cycle.
  • Staff time: Manual reminder calls, reconciling Paybill payments against a spreadsheet, and reconnecting customers by hand all shrink. Operators who once spent most of a day on collections usually see that time move to support and network work.

These figures depend on your subscriber base, plan prices, and current process, so measure your own baseline for a month before the change and compare the same numbers afterwards.

Get started with mobile money renewals

If you run monthly internet plans and want renewals to happen without chasing payments by hand, talk to the IntaSend team about your subscriber base and billing platform. We’ll help you plan the integration with the Payments API. For a wider view of collections, see our complete M-Pesa billing guide for ISPs.

You can also reach us on WhatsApp at +254 711 082 947, by email at [email protected], or by phone at +254 114 114 644.

What Our Clients Say About Us

Don’t just take our word for it—hear what our satisfied customers have to say! IntaSend has helped businesses and individuals across Kenya and beyond streamline their payments.

  • The experience has been seamless, efficient, and hassle-free. One thing that makes Intasend stand out is the platform's ability to collect payments from anywhere in the world.

    Felistas Njihia - IntaSend customer
    Felistas NjihiaFelin Solutions
    ★★★★★
  • Our experience with IntaSend has been remarkable. The integration process was quite smooth with proper API documentation. Intasend won us over on the ease of B2B transactions which is our mainstay and remains our preferred payment solutions

    Kelvin Muriuki, C.E.O - IntaSend customer
    Kelvin Muriuki, C.E.Otaka.earth
    ★★★★★
  • Their platform is incredibly user-friendly, allowing our customers to easily pay for their weekly meals. The fast and secure payment process also provides peace of mind for both our customers and us.

    John Faderr - IntaSend customer
    John FaderrFoodtable by Roros Co.
    ★★★★★
  • @intaSendHQ I am currently blown away by your product. The documentation is so developer friendly as opposed to one pan-African payment gateway, market leader. Good job!

    @Matinde on Twitter - IntaSend customer
    @Matinde on Twitter
    ★★★★★
  • Their customer service is top-notch. The team at IntaSend Payments is friendly and super responsive, always there to lend a hand whenever you need it.

    Wearify on Shopify - IntaSend customer
    Wearify on ShopifyWearify Kenya
    ★★★★★
  • I would like to commend your service and especially point out your outstanding quick turn-around in processing payment and your after-office hour’s support. We are glad that you can be reached 24/7 for queries and round-the-clock support.

    Peter Nyotta - IntaSend customer
    Peter NyottaTwende Worldwide Tours and Travel Ltd
    ★★★★★
  • This payment processor has allowed me to continue serving my local as well as international customers. They also offer reasonable fees and their payouts are timely. Even without a website, IntaSend payment links works just fine.

    Shadrack Masinde - IntaSend customer
    Shadrack MasindeGofan Safaris Limited
    ★★★★★
  • I have been using Intasend for a while now both on my website as a payment gateway and my business as a payment solution and all I can say is, IntaSend is the best solution to sort out all business payment related difficulties.

    Daniel Nyongesa - IntaSend customer
    Daniel NyongesaA+ Academic Consultants
    ★★★★★
  • IntaSend is one of the best online money transfers with mobile and card payment options and helps in collecting emails for marketing.

    Moses Thoithi - IntaSend customer
    Moses ThoithiWizAdventures Safaris
    ★★★★★

Frequently Asked Questions

Does the customer have to approve each renewal payment?

Yes. Every billing period requires the subscriber to pay, by Paybill, by opening a payment link, or by approving an M-Pesa prompt. Nothing is debited from their mobile money wallet without their action.

What happens if a customer pays their ISP late?

If the payment arrives during the grace period, service stays on and the paid-until date moves forward. If it arrives after suspension, the account is reconnected once the payment webhook is processed.

Can a customer pay for several months at once?

That depends on how your billing system handles advance payments. The payment can cover any amount, and your system decides how far to extend the paid-until date.

How quickly does service come back after a mobile money payment?

As fast as the webhook arrives and your system processes it. Respond to the webhook within a few hundred milliseconds and handle the reconnection in the background.

How do I stop a renewal being counted twice?

Make webhook handling idempotent. Webhooks can arrive more than once or out of order, so record each invoice ID and extend the paid-until date only the first time a payment shows as COMPLETE.