Before you start
- Decide whether customers buy calendar access, accumulated connected time, or accumulated time with a final deadline.
- Confirm that the selected vendor/controller supports the intended policy.
Procedure
Follow these steps in order
Expires after first login
The validity clock starts at the first successful login. A 24-hour voucher ends 24 hours later even if the customer disconnects or uses only part of the time.
Connected time only
Only authenticated connected time is consumed. A one-hour voucher can be used across multiple sessions until the full hour is consumed, subject to any vendor limitations.
Connected time within a window
The first login starts a final activation window while connected usage is accumulated. Example: up to one hour of connected time, but any unused time expires 24 hours after first login.
Set limits explicitly
Enter time, optional data allowance, speed, shared users, and the activation window. Review the human-readable summary before saving.
Test with a new voucher
Install one voucher on the target device, sign in, disconnect, reconnect, and verify both connected usage and the final expiry timestamp.
Verify success
- The package summary describes the intended clock behavior.
- The target controller accepts the mapped policy.
- The test voucher shows the expected remaining time after disconnecting and reconnecting.
Troubleshooting
The voucher expires immediately
Check timezone, duration units, first-login time, activation-window length, and controller package mapping. Do not reuse an already activated voucher for the test.
Connected time continues while offline
The selected device/controller may enforce calendar expiry instead of accumulated usage. Choose a supported policy or use the gateway that performs authentication.
Was this guide helpful?
Your response helps the system owner prioritize documentation updates.