24 lines
899 B
Markdown
24 lines
899 B
Markdown
|
# Subscriptions & Services
|
||
|
|
|
||
|
|
How active services are displayed and refreshed.
|
||
|
|
|
||
|
|
## Data Source
|
||
|
|
|
||
|
|
- Subscriptions (services/products) are read from WHMCS via the mapped client ID.
|
||
|
|
- Statuses (Active, Pending, Suspended, Cancelled, Completed) come directly from WHMCS.
|
||
|
|
|
||
|
|
## Freshness
|
||
|
|
|
||
|
|
- Subscription list cached for 5 minutes; individual subscription cached for 10 minutes.
|
||
|
|
- Cache is cleared when WHMCS signals a change (webhooks) or when we update profile/address data that could affect related services.
|
||
|
|
|
||
|
|
## What you see
|
||
|
|
|
||
|
|
- Service name, status, start date, amount, and currency as stored in WHMCS.
|
||
|
|
- Subscriptions are also used in the dashboard stats (e.g., active count). Those stats refresh after cache invalidation.
|
||
|
|
|
||
|
|
## If something goes wrong
|
||
|
|
|
||
|
|
- Missing WHMCS mapping: we return a clear error instead of an empty list.
|
||
|
|
- WHMCS unavailable: we show “try again later” and do not cache failures.
|