Usage, invoices, and receipts

Review service and billing history

The portal keeps 3 records of your service: what you used, what you were billed, and what you paid. All of your invoices and payments load on one page, with no paging.

Usage

Open Usage for current month totals, package/FUP context, a 30-day daily chart, and session rows containing start/stop, duration, download/upload, and IP where available. Recent sessions lists your latest 10 sessions. Sizes use 1,024-based units.

Usage depends on RADIUS accounting. A session still open or delayed accounting record can change later. Use the displayed units and period; router-interface totals are not necessarily the same as one subscriber’s accounted usage.

Invoices

Open Invoices to see invoice number, amount, due date, and status. Open a row for line items, total, paid, remaining, issue/due dates, and current payment action.

Statuses can include pending, partial, paid, cancelled, and overdue display state. An open invoice shows Overdue once its due date has passed.

Pay an invoice

1. Confirm invoice number, line items, total, paid, and remaining.
2. Choose the payment action when the invoice is payable.
3. Confirm the prompt/checkout for the remaining amount.
4. Authorize payment.
5. Wait while the page polls the checkout status. It checks every 2 seconds for up to 2 minutes.
6. Verify the invoice reloads as paid/partial and the payment appears in receipts.

The current page can present an M-Pesa prompt depending on the ISP’s gateway. A provider/browser return does not by itself prove the invoice is settled.

Receipts

Open Receipts for payment date, amount, method, and receipt/reference. A PDF download is available when the payment has a receipt number. The file is named after it, for example receipt-SJK4H7Y2LM.pdf.

If a receipt is missing or incorrect, contact the ISP with payment date, amount, masked phone/account, and provider reference. Do not send a PIN, OTP, password, or full financial credential.

Disputing an amount

Do not pay twice while asking for clarification. Record the invoice/payment identifiers and use Portal support tickets. The operator can compare the invoice activity, linked payments, package, and provider record.