MikroTik M-Pesa integration for internet billing
LinkDesk supports M-Pesa internet payment workflows in a configured MikroTik deployment. Start with your own supported merchant integration and customer HTTPS service, then test provider verification and access delivery. The WayaDesk software checkout is separate from the payments your subscribers make.
How Customers Buy WiFi with M-Pesa: LinkDesk Workflow · Hotspot Captive Portal Software with M-Pesa
WayaDesk / M-Pesa payments
An internet payment must identify more than an amount. The operator needs to know which account or package it belongs to, whether the provider confirmed it and what access should follow. Keeping those facts together makes renewals and payment disputes easier to investigate.
Two different payment journeys
An operator’s customers pay for internet access through the configured merchant integration. Separately, an operator may buy a WayaDesk software licence from the seller. A working internet-billing integration does not automatically create a checkout for selling software licences, and a licence payment does not add a customer’s internet entitlement.
Follow the complete record
For an internet purchase, inspect the payment reference, intended account, package and resulting service period. Then inspect the access action. If the router cannot be reached, the payment may still be successful. Diagnose that second part without asking the customer to buy the same service again.
- Give each purchase a traceable reference.
- Keep pending, failed and verified outcomes distinguishable.
- Compare merchant evidence with the correct account before manual intervention.
Plan for normal exceptions
Customers may close a payment window, cancel a prompt or pay while a network component is unavailable. Write a short operating procedure for each case. Staff should know when to wait, when to verify and when to recover access using the existing record.
What to demonstrate
During the pilot, verify a successful purchase, a failed attempt and an interruption between payment and access. Record what the merchant side, application and router each show. This creates evidence for the workflow you intend to sell rather than relying on a general claim of instant activation.
Explore m-pesa payments
- Understanding M-Pesa STK Push Payment Status
- M-Pesa Payment References for Internet Accounts
- Handling Duplicate M-Pesa Payment Events
- M-Pesa Paid but Internet Access Is Delayed
- Failed or Cancelled M-Pesa Payments: Operator Workflow
- M-Pesa Internet Renewals and Service Dates
- Internet Payment Receipts and Transaction Records
- Payment Reconciliation for a Small Internet Business
- Preparing Your M-Pesa Merchant Setup for Billing
Frequently asked questions
Can a payment be successful while access is delayed?
Yes. Payment confirmation and applying access are separate operations, so both states need inspection.
Does buying the software configure my merchant account?
No. Your internet-payment integration still requires the appropriate merchant configuration and live checks.
Choose your software licence
One installation, a clear router allowance, and perpetual use of the purchased version. Setup assistance, hosting and external services are separate.