Today
…
Today · Home Clients
—
Not connected yet
This Week
…
Paid this week
This Month
…
Active Now
…
Unmatched Sessions
—
Connected, no matching payment
Home Clients
—
Not connected yet
Pending Compensation
—
Not connected yet
Router health
Live from MikroTik /system/resource
Monthly revenue
Inbound payments, KSh (Pay Hero)
Flagged right now sample data
Devices connected without a matching payment or points redemption
| Device / MAC | IP | Connected | Last known payment | Status | |
|---|---|---|---|---|---|
| Unknown device BC:D7:33:06:0C:42 |
10.5.12.44 | 2h 14m | None found | ● Unmatched | |
| Unknown device E4:5F:01:9A:22:7B |
10.5.12.61 | 41m | KSh 20 · expired 38m ago | ● Plan expired, still online |
Recent customers
Who just paid. Message anyone in one tap.
| Phone | Plan | Amount | Receipt | Time |
|---|
All active sessions
Cross-checked against payment & points records automatically
| Type | Device / MAC | IP | Plan | Time left | Match |
|---|
Home clients
Each client is pinned to a static IP on the 10.20.x.x range
| Name | MAC | Static IP | Plan | Status |
|---|
Recent hotspot purchases
Latest M-PESA confirmations from the captive portal
| Phone | Plan | Amount | Receipt | Time |
|---|
Possible double payments
Same phone paid again within 5 min after a payment that never got connected. These customers were likely short-changed, and many never ask.
| Phone | Day | 1st payment | 2nd payment | Gap | Owed |
|---|
Compensate a client
For downtime, double-charges, or verified complaints
Automatic compensation
Auto-credit affected clients when the router/VPS reports downtime
| When | Client | Reason | Given |
|---|---|---|---|
| Today, 6:12am | 07XX···341 | Router reboot during active session | +20 min |
| Yesterday | 07XX···998 | Duplicate M-PESA charge | KSh 20 refund |
PayHero / M-PESA API
Active
Token expires in 27 days
SMS Credits
214
~2 days left at current rate
KPLC Lookup Credits
88
Token lookups remaining
Top up a service
Applies instantly to the backend — no server restart needed
Line segments
Home clients act as always-on checkpoints along each physical run. 3+ consecutive points down usually means a break, not a payment issue.
Idle-time anomalies
A connected session's idle timer should reset with normal use. Climbing idle time — especially on several points at once — usually means the router is stuck in a reboot loop, not that people stopped using WiFi.
| Client | Point | Idle time | Normally resets at | Phone |
|---|
Router connection
How this dashboard talks to your MikroTik
This panel is a placeholder — wiring it up needs your RouterOS API credentials, entered once on your server, never in the browser.