Billing controls access to hosted WatchTower dashboard/API features, protected location limits, included history, and optional modules. The in-world terminal is the machine package; the subscription controls the hosted service and feature access.
Base terminal
The current guidebook draft lists the base WatchTower Terminal as a one-time machine purchase of **L$1,999**. This is the in-world object package. Hosted live dashboard features still require an active plan when they depend on the FlaroCity servers.
Subscription plans
| Plan | Protected locations | Weekly price | Monthly price | Included history |
|---|---|---|---|---|
| Starter | 1 location | L$99/week | L$349/month | 7-Day History |
| Plus | 3 locations | L$199/week | L$699/month | 30-Day History |
| Pro | 10 locations | L$399/week | L$1,399/month | 90-Day History |
| Network | 25 locations | L$799/week | L$2,799/month | 180-Day History |
The dashboard should show the plan name, paid-through date, renewal state, grace state if used, active add-ons, and location usage such as 2 of 3 locations used.
What counts as a protected location
A protected location is a place the owner wants WatchTower to monitor. It may be a parcel, store, club, event space, rental area, or region management point. It should not simply count inventory copies. A moved terminal should update or review the location instead of always creating a new billable location.
Location states should include:
- **Active** — covered by the plan and receiving data.
- **Stale** — assigned, but no recent data.
- **Paused** — intentionally disabled by owner/admin.
- **Pending Review** — needs matching or owner confirmation.
- **Over Limit** — the plan does not currently cover it.
Add-ons
| Add-on | Current listed price | Purpose |
|---|---|---|
| Extra Location Pack | L$499 | Adds location capacity beyond the base plan rules. |
| Discord Alerts | L$499 | Sends selected WatchTower alerts to Discord. |
| Adult Access Gate | L$699 | Helps owners manage adult-content access workflows. |
| Staff Role Manager | L$799 | Lets owners assign staff permissions in the dashboard. |
| Advanced Security Actions | L$999 | Enables dashboard-driven security actions where land permissions allow. |
| Chat Relay | L$999 | Relays public local chat channel 0 to the owner dashboard according to safe settings. |
| Extended History | L$999 | Extends dashboard history beyond the included plan period according to final policy. |
| Custom Branding | L$1,499 | Allows branded customer presentation beyond standard FlaroCity styling. |
Owned add-ons should remain attached to the account even if the subscription expires. Hosted features may pause while the subscription is inactive, but the owner should not have to buy the same owned add-on again when reactivating.
Weekly vs monthly payments
Weekly payments are easier for customers who prefer small Second Life L$ payments. Monthly payments are easier for stable store, club, or rental owners who want fewer renewals. The dashboard should make both options clear and show when the current period ends.
Payment Station
The Payment Station is the in-world payment workflow for subscriptions and add-ons. It should record who paid, how much they paid, when they paid, what product/plan was selected, and whether the payment matched a known product.
Recommended payment record fields:
- Payer avatar UUID
- Payer name
- Amount paid
- Product selected
- Plan/add-on intent
- Timestamp
- Object UUID
- Region and parcel
- Matched account or pending account
- Review state
Payment matching
Payments are easiest to process when the station knows exactly what the customer selected. If two products share the same price, the station should require a selected product button before payment so the dashboard can tell what was intended.
Payment states:
| State | Meaning |
|---|---|
| Matched | Amount and selected product match a known plan/add-on. |
| Pending Review | Amount or account match is unclear. |
| Applied | Subscription or add-on was updated. |
| Rejected | Payment cannot be applied as submitted. |
| Refunded / Manual | Staff handled it outside the automatic flow. |
Grace period recommendation
A short grace period can prevent support problems caused by region downtime, HTTP lag, delayed manual review, or a customer paying slightly late. If used, the dashboard should clearly show **Active**, **Grace**, **Expired**, and **Locked** states.
Suggested wording:
Your WatchTower Terminal may remain in-world after a subscription ends, but hosted live dashboard/API features require an active plan. Owned add-ons remain attached to your account and can be used again when your subscription is active.
Downgrades and over-limit locations
Plan downgrades should not immediately delete data. Instead, the dashboard should mark extra locations as over limit, paused, or locked according to policy. Owners should be able to choose which locations remain active.
Billing support policy
If a payment does not apply automatically, the owner should open a support ticket with the transaction details, payer avatar name, approximate time, amount, and selected product. Staff should verify the Payment Station log before manually changing subscription or add-on state.