Data Caps for Local MikroTik Hotspot Vouchers

WayaDesk / Hotspot billing

A data cap is useful only when the access system can enforce it. A usage figure displayed in a report does not by itself stop traffic at a purchased threshold. Operators should verify both counting and enforcement before selling a capped package.

Know the current supported scope

LinkDesk’s documented data caps apply to supported local Hotspot voucher plans using the router’s relevant byte-limit mechanism. The current release does not present PPPoE or RADIUS data quotas as enforced. Select the access method first, then decide whether a capped offer is appropriate.

Explain the unit used

The current local cap setting treats one MB as 1,048,576 bytes. Make sure package wording and internal calculations use a consistent convention. A mismatch between the advertised allowance and the configured quantity can create avoidable customer complaints.

• Use a small test allowance for the controlled acceptance exercise.
• Observe the counter and the access result at the threshold.
• Retry provisioning and check that used allowance is not unexpectedly reset.

Separate time from traffic

A package may have a time boundary as well as a supported data boundary. Explain which conditions can end access. Customers should understand why a pass might stop before its displayed time ends if the traffic allowance has already been consumed.

Keep reporting claims narrow

Accounting totals retained for a subscriber are not automatically a calendar-month quota or a universal measure across access methods. Label reports for what they contain, and avoid promising a hard limit on a service path that the current software deliberately does not enforce.