Local payment methods should drive operations
For many ISPs, mobile money is not an add-on. It is how subscribers pay every month. ISPAgents should connect mobile money events to invoices, receipts, customer state, restoration, support context, and finance reconciliation.
Payment workflows
| Workflow | ISPAgents role | |---|---| | Payment matching | Match provider references to the right customer, invoice, or service. | | Automatic restore | Restore service after payment confirmation and keep proof on the timeline. | | Failed match review | Queue unmatched payments for finance review instead of losing them. | | Reminders | Send SMS or WhatsApp reminders based on billing state and local rules. | | Reconciliation | Compare provider batches, account balances, receipts, and statements. |
Flexible provider layer
Payment providers differ by country and customer segment. ISPAgents should use an abstract payment layer so regional integrations can be added without rewriting the billing workflow.
FAQ
Can mobile money restore internet automatically?
Yes. When the provider confirmation, customer match, and access policy are trusted, ISPAgents can restore through RADIUS, MikroTik, or a custom connector.
What happens to unmatched payments?
Unmatched payments should appear in a finance review queue with provider reference, amount, time, possible customer matches, and audit history.