Payment-linked customer records
Keep payment references and receipts connected to the customer or hotspot activity they belong to.
Payment operations
Connect M-Pesa payments to ISP billing records
Move payment information into the same workspace as subscribers, packages, vouchers, and invoices so finance and support teams can work from shared records.
What it brings together
One operational view, fewer handoffs
Track M-Pesa-oriented payment workflows, customer balances, receipts, hotspot revenue, and reconciliation in ISPinnacle.
Gateway callbacks
Process supported payment callbacks at validated server boundaries and record actionable failures without logging secrets.
Reconciliation visibility
Review transaction status, reference details, invoices, and reporting from a consistent operational view.
Payment reminders
Use messaging workflows to send billing reminders and service notices with customer context.
Typical workflow
From setup to daily operation
Start from an account or voucher
Create a payment request from the subscriber, invoice, or hotspot purchase flow.
Receive the result
Validated gateway callbacks update the relevant transaction and operational record.
Confirm and report
Support and finance teams can confirm payment state without comparing several disconnected systems.
Common questions
Answers before your first call
Does ISPinnacle support M-Pesa workflows?
Yes. ISPinnacle includes M-Pesa-oriented payment and callback workflows alongside additional supported payment gateways.
Can hotspot payments be tracked separately?
Yes. Voucher-linked hotspot transactions can be reported and used for monthly revenue-share snapshots.
Can staff send payment reminders?
Yes. Messaging tools can send payment alerts and service notices using the customer records already in ISPinnacle.