Collections and payments

Why a payment receipt does not prove internet access is back

Guided pilot: how payment qualification, RADIUS session freshness and missing identity affect a paid-but-offline support queue.

Illustrative investigation checklist

Keep the evidence distinct

Check qualification
Payment
Check observation
Session
Keep visible
Unknown
ReviewPayment recordConfirm scope
ReviewSession timestampCheck freshness
ReviewMissing identityInvestigate
Illustrative checklist, not a live dashboard or customer outcome.
Page type
Blog
Primary search
Why a payment receipt does not prove internet access is back
Updated
2026-10-16

Two pieces of evidence, two different questions

A payment receipt answers a billing question. A current session observation answers a different question: what does the access system report now? Support needs both, tied to the same service and a clear observation time, before deciding what to investigate next.

Guided pilot implementation example, not a customer case study. This article describes the paid-but-offline report and synthetic test expectations in the implementation. CRM, billing and access-policy capabilities retain their Guided pilot status. Automatic restoration remains unproven, as does production reliability.

What the queue actually counts

The report uses one row per service. Under its defaults, the customer's lack of positive open invoice balance, or a positive posted payment received within 30 days, meets the payment condition. A recent partial payment can qualify even with debt remaining. No invoice history can qualify too. The queue is therefore not proof of a fully settled account.

A qualifying service enters the default queue when it has a mapped username but no matching active RADIUS accounting session observed within 900 seconds. Missing, stopped and stale session evidence are distinguished. Cancelled services and orphaned customer references are excluded; future timestamps do not establish current evidence.

The report matches a RADIUS username, then PPPoE username, then Hotspot username inside the tenant. Operators must keep these names unique across the tenant's accounting sources. There is no MAC/IP guess. A missing identity is unknown, excluded from the offline total and available in a separate Unmapped identity view.

A synthetic accounting example

The implementation uses fresh active accounting evidence to suppress a qualifying service from the queue. The following synthetic example describes the expected behavior; it is not a new test result or a live restoration claim:

Local observationTile and queue countMeaning
No current matching session1Investigate the accounting evidence
Start packet processed0Fresh active evidence suppresses the row
Interim packet processed0The observed session remains current
Stop packet processed1The session has ended in the accounting evidence

The broader synthetic fixture expects four offline services and one separately unknown service. Its assertions check that current session evidence removes a service from the offline total and that another tenant's session cannot suppress that row.

This example does not establish production behavior, browser validation or duplicate and late payment-event handling. Automatic payment-to-access restoration is not yet shipped under this readiness scope.

Check the accounting source before diagnosing a line

The tile and queue name RADIUS accounting as their source and show the effective windows. They also show the newest stored packet time for each observed NAS. An evaluation timestamp is not a packet timestamp.

If a NAS stops sending accounting, many services can appear offline after the freshness window expires. Check packet delivery, ingestion delay and clock quality before diagnosing subscriber lines. A recent Stop is a recent packet, but it does not make that service online. NASes that have never appeared in stored accounting cannot appear in the NAS list.

The default 30-day payment window and 900-second freshness window are tenant configurable in the guided pilot. Large-tenant load and production behavior are not established by this example.

Follow the exception without promising a restore

Start with the customer's payment and invoice evidence. Check the mapped service identity, accounting source and freshness. If those agree, investigate the relevant access path using the operator's approved procedures. The report itself is read-only and does not restore a connection or prove a physical outage. It is not MikroTik router evidence.

Review payment collection scope and the RADIUS options guide. Existing-FreeRADIUS probing and opt-in SQL accounting import remain a guided pilot; fake-transport CoA proof does not establish real NAS mutation.

Continue with the manual access-check worksheet and the support automation checklist.

Next step

Discuss the scope for your network.