An ISP billing system in India is the software that decides who is connected, who has paid, and what happens the moment those two stop matching. For a local operator running a few hundred subscribers off a MikroTik router, that decision is currently made by hand — a WhatsApp reminder, a UPI screenshot, a login to Winbox to switch someone back on. Automating it is the difference between an operator who can grow past a thousand subscribers and one who cannot.
The Indian market is different in two specific ways
Most billing platforms are written for a market where you take a card and send an email. Neither assumption holds here, and both have a technical consequence.
Payments are UPI-first, not card-first
India runs on UPI. A subscriber expects to scan, approve in their own bank app, and be back online in seconds — not to type a sixteen-digit card number into a captive portal. Any billing system that treats UPI as an afterthought behind cards will lose payments at the last step.
What matters operationally is not just accepting UPI but reconciling it. A payment that lands in your account but is not matched to an invoice still leaves the subscriber disconnected and still generates a support call. The reconnection has to be automatic, triggered by the confirmed payment itself.
SMS is governed by DLT, and unregistered messages simply vanish
This is the part that surprises operators coming from other markets. Under TRAI's Distributed Ledger Technology rules, every commercial SMS sender in India must register three things with the telecom operators before a single message is delivered:
- The entity — your business, registered on a DLT platform.
- The header — your six-character sender ID, approved and tied to your entity.
- The template — the exact wording of each message, with variables marked.
Send outside that and the message is dropped at the carrier. Not delayed — dropped. An operator who wires up a generic bulk-SMS API and starts sending expiry reminders will see a delivery report full of successes and subscribers who received nothing.
This is why a billing system built for India has to send through DLT-aware providers and refuse to send when a template is missing, rather than quietly burning your SMS credit.
What automation actually replaces
The manual loop most Indian operators run looks like this:
- A subscriber's plan expires and they lose access.
- They message you on WhatsApp.
- They send a UPI payment and a screenshot.
- You check the bank app, open Winbox, and re-enable them.
- You remember — or forget — to note it down.
Every step is a place to lose money or a customer. An automated platform collapses it into: the subscriber pays, the payment is matched, access is restored, and the ledger is written. Nobody is woken up at 11pm.
PPPoE, hotspot and static IP from one account
Indian operators rarely run just one kind of connection. A cable operator might have PPPoE customers in apartment blocks, hotspot vouchers in a market or hostel, and static IPs for a handful of small businesses. Splitting those across separate tools is how reconciliation breaks.
Centipid runs all three against the same MikroTik routers from one account: PPPoE subscribers with automatic suspension and restoration, hotspot vouchers sold in bulk or per session, and static IP customers billed on the same cycle.
What to look for in an Indian ISP billing platform
If you are comparing options, these are the questions that separate software that works here from software that merely runs here.
Does it collect by UPI, and does the payment reconnect the subscriber? Accepting UPI is table stakes. Reconnecting automatically on the confirmed payment is the part that removes work.
Is the SMS DLT-aware? Ask specifically whether it supports registered headers and template IDs. If the answer is a generic "yes, we support SMS", it will not deliver in India.
Does it talk to MikroTik directly? RADIUS authentication, PPPoE profile changes and hotspot user management should happen from the billing system, not from a second window in Winbox.
Can you try it without a card? You should be able to connect a router and take a real payment before committing anything.
How Centipid handles it
Centipid collects Indian payments through Razorpay — UPI, cards, netbanking and wallets all arrive over one payment link, and the confirmed payment renews the subscriber automatically without anyone touching the router.
For messaging, it sends through MSG91 and Fast2SMS on India's DLT rails using your own registered header and templates. If you would rather not register at all, TextBee sends from an ordinary Android handset, which DLT does not cover — a practical shortcut for a small operator getting started.
Underneath, it is the same platform running ISPs across Kenya, Uganda, Ghana and Nigeria: RADIUS authentication, MikroTik provisioning, automated invoicing, expiry reminders and a subscriber portal. The market differs; the network does not.
The India page lists the payment and SMS providers available locally, and the pricing page shows what it costs per active subscriber. The trial runs 14 days and needs no card.
Where to start
Do not migrate everything at once. Connect one router, move a small group of subscribers onto it, and run a full billing cycle — expiry, reminder, payment, reconnection — before you move the rest. You will learn more from twenty subscribers going through one real cycle than from a month of evaluating feature lists.
Two practical notes for India specifically: begin your DLT registration early, because template approval takes days rather than minutes and it will otherwise be the thing holding up your launch. And test a real UPI payment end to end — not a sandbox one — before you tell subscribers to use it.
If you are running MikroTik in other markets too, the same principles apply: our guides for Indonesia and Nigeria cover how the local payment and messaging rails change the same underlying workflow.
