How ISPs Should Handle Prepaid Monthly Billing
Guided pilot scope. An operator runbook for prepaid renewal dates, wallet balances, grace periods, and verified suspend/reconnect decisions.
Separate money from access
Sell a defined service period, then prove it was delivered
Prepaid monthly billing collects money for a specified service period before that period is provided. The operator must agree what “monthly” means, how funds are allocated, and what happens when a renewal is not funded. A customer balance, a paid renewal, and an active network session are separate facts.
A wallet in this guide means the ISP's internal record of unapplied customer credit, not an external provider wallet or a bank account. A top-up should first create verified payment evidence. A separate allocation consumes the permitted credit for a particular service and period. This separation matters when one customer has two services or a payment covers only part of a renewal.
Architecture: allocation precedes the access decision
Verified payment / approved manual credit
|
Unapplied customer credit ledger
|
Allocate once to service + renewal period
|
Evaluate expiry, balance, grace, manual hold
|
Preview desired state + approval
|
Recheck current policy and target
|
Qualified access adapter or lab mock
|
Observed session + service evidence
|
Confirm outcome / support exception
Keep the financial record even if the access adapter fails. Track the renewal obligation, the allocation, and the access job with separate identifiers. Replaying a payment event must not debit the wallet twice or extend the service period again.
Define the renewal contract before scheduling jobs
| Decision | Rule to document and test |
|---|---|
| Calendar month or fixed duration | Define the anchor, timezone, exact expiry, and treatment of dates absent from a shorter month. |
| Early renewal | State whether credit funds the next scheduled period or changes the current expiry. Prevent overlapping or duplicate terms. |
| Late renewal | Choose whether the new term starts at payment, verified restoration, or the previous anchor. Explain any charge for an interrupted period before payment. |
| Partial payment | Keep the shortfall visible. Require the full renewal amount unless an explicit alternative eligibility rule exists. |
| Grace | Choose the duration and permitted service state, including whether grace time is charged or deducted from the next term. |
| Multiple services | Require an explicit allocation order or customer selection; never spend the same credit twice. |
| Manual hold | Give an authorized hold precedence over any proposed restoration during a guided pilot until an authorized operator releases it. |
Use exact timestamps in storage and display the relevant local time to operators and subscribers. A scheduler retry should target the same service period. Define an outage policy before rollout so a payment-provider failure does not unexpectedly become a bulk suspension event.
Workflow example: partial top-up during grace
The amounts and dates below are synthetic examples, not pricing or customer results. The example service costs 1,500 units in one currency. Its paid term ends at 00:00 on 1 November in the operator's chosen timezone. The illustrative policy allows 48 hours of grace and requires full payment for renewal.
- Before expiry, show the subscriber the next period, amount, and deadline. Prepare the renewal obligation once using the service and period identity.
- At expiry, no funds are allocated. Preview a move to grace; record the reason and the grace end at 00:00 on 3 November. Grace is an explicit service-policy choice, not an extra wallet credit.
- A verified top-up of 600 arrives on 2 November. Record it once and allocate 600 to the renewal. Show 900 still due. A repeat delivery of the same transaction must change neither the allocation nor expiry.
- At grace end, the outstanding balance remains 900. Recheck recent payments, exceptions, and the target service immediately before an approved suspension. Record whether the network actually enforces the restriction; an unreachable adapter means an unresolved outcome.
- A second verified payment of 900 arrives after suspension. Allocate it once. Under this example's agreed policy, the new calendar-month term starts at verified restoration, and grace is not deducted. Other operators may choose a different disclosed rule.
- Re-evaluate eligibility and holds. Cancel or supersede any stale suspension job. Queue restoration only for the correct service profile; a remaining manual hold stops automatic reconnection.
- Verify the session and expected service after the adapter acts, then finalize the term start and expiry according to the chosen policy. If the customer is paid but offline, retain the payment and open a support exception. Do not charge again merely to retry restoration.
Operational risks
- Double spending: concurrent renewals must not allocate the same wallet credit to two services. Test the combined customer balance after both attempts.
- Month-end drift: test January 31, February, leap years, and timezone changes. Display the computed expiry before confirming a renewal.
- Late jobs: a suspension preview can become stale after payment. Revalidate immediately before acting and reconcile any already-started action.
- Reversals: retain original payment evidence and use reviewed corrections. Recompute eligibility; do not blindly reverse an unrelated service's access.
- Provider or router outage: define when automation pauses, who reviews exceptions, and how queued actions are reconciled after recovery.
- False reconnection: an accepted command proves neither a current session nor usable service. Keep an explicit unknown state when evidence is missing.
Implementation checklist
- Document period anchors, month-end behavior, timezone, grace, and early/late renewal rules.
- Separate unapplied credit, invoice allocation, service entitlement, and observed access.
- Rehearse duplicates, partial payments, excess credit, and simultaneous renewals with mocks.
- Verify customer/service/network mappings before granting an adapter permission to act.
- Test payment arrival during suspension and restoration retries after a lost response.
- Make manual holds visible and require an authorized release.
- Practice provider outage, router outage, reversal, and paid-but-offline handling.
- Agree recovery ownership and collect evidence before expanding a guided pilot.
Where ISPAgents fits
ISPAgents has guided-pilot foundations for subscriber invoices, payments, ledger records, allocations, provider evidence, reconciliation, and settlement. This does not establish a complete wallet or recurring prepaid renewal implementation. AR aging works and a USD statement read is verified; journal CSV export is implemented but its contents were not exercised. Tax/multicurrency posting, refund/reversal/receipt flows, credits/deposits/write-offs, settlement cycles, accounting sync, and production recovery remain unqualified. Accounting-grade customer billing is guided pilot scope.
Service-policy preview, queued jobs, approvals, no-op handling, and result recording are guided pilot capabilities with a mock-safe worker. Live router/RADIUS mutation remains gated until real adapters, credential resolution, rollback evidence, and monitoring are registered. Qualify suspend/reconnect behavior for the exact access path before describing it as operational.
Payment-provider mapping and webhook evidence are also guided-pilot foundations. Live M-Pesa Daraja clients are not shipped. MTN MoMo and Orange Money settlement is not verified. Reminder and receipt workflows over WhatsApp/SMS remain roadmap; notification foundations are guided pilot scope. Agree those boundaries when defining the pilot.
Related solutions and guides
Review prepaid internet billing, ISP payment collection, and automatic internet suspension for readiness boundaries. Pair the mobile-money reconciliation guide for pilot evaluation with the staff router-access guide when writing an operator runbook.
Frequently asked questions
Is a prepaid month always 30 days?
No. Choose a calendar-month or fixed-duration policy, document the timezone and month-end rule, and show the exact service expiry. Do not silently alternate between policies.
Should topping up a wallet immediately reconnect a subscriber?
Only a verified allocation that satisfies the renewal policy should make the service eligible. Recheck manual holds and the target service, then verify access after execution. A wallet balance alone is insufficient.
Does ISPAgents ship automatic prepaid suspension and reconnection?
No general live automation promise is made. Subscriber billing and service-policy foundations are guided pilot scope. Live router/RADIUS mutation remains gated on adapters, credential resolution, rollback evidence, and monitoring.
Continue the operations map.
One Subscriber, One Device Identity
Available: The canonical identity foundation supports mapping protocol observations toward one device/customer path using strong serial/MAC evidence. It does not establish universal billing, RADIUS, or controller integration.
Open pageGuidesFair-usage policies for unlimited ISP plans
Keep access available after a usage threshold, explain the reduced speed before purchase, and give support a policy they can defend.
Open pageSolutionsAutomatic Internet Suspension Software — Guided pilot
Guided pilot: Preview, queued jobs, approvals, result recording, and a mock-safe worker can be evaluated in a guided pilot. Live router/RADIUS mutation remains gated; automated suspension and restoration are not a shipped promise.
Open pageSolutionsCustomer Self-Service Foundations — Guided pilot
Guided pilot: Field-job lifecycle, serialized stock, basic tickets and subscriber portal flows have narrow synthetic-data proof and remain guided pilots. Physical installs and invite email delivery are unproven. The technician PWA, dispatch board, dedicated stock workspace and IPAM remain roadmap.
Open page