Prepaid billing needs speed and proof
Prepaid subscribers expect service to renew quickly after payment. The ISP needs proof that the payment matched the right account, the access state changed correctly, and support can explain the result.
Prepaid workflows
| Workflow | ISPAgents role | |---|---| | Renewal reminders | Send SMS or WhatsApp reminders before expiry. | | Payment matching | Match mobile money, cash, bank, or manual payment to the subscriber. | | Restore | Restore access through RADIUS, MikroTik, or a connector after confirmation. | | Grace period | Apply local policy for grace days, partial payments, or exceptions. | | Finance review | Reconcile receipts, provider batches, and customer account history. |
Flexible local rules
Prepaid models vary by country and ISP. ISPAgents should support monthly, weekly, custom-duration, package-based, and negotiated models without forcing one billing design.
FAQ
Can prepaid billing suspend automatically?
Yes. Suspension can run after expiry according to operator policy, customer segment, grace rules, and access mapping.
Can prepaid and postpaid run together?
Yes. Many ISPs need both models because customers, business accounts, and regions may require different commercial rules.