HandyCafe Docs
admin

Cloud Admin License Operations

Authorized HandyCafe platform administrators can manage a customer's commercial access from the customer detail page. The page starts with an account overview, profile status, live connection status and Genesis license count. Each Genesis license has one operations card showing its current plan, PC and console limits, AI balance, member balance, add-on access and Stripe state.

Legacy and beta tools are kept in a separate expandable section. Ping activity and profile changes are available under Diagnostics and change history. This keeps the current Genesis workflow visible without removing older support tools.

View all Genesis licenses

Open Licenses in the internal admin dashboard. The Genesis tab opens by default and lists only current Free and Genesis plans. Historical Beta grants remain in the separate Beta tab.

The summary cards show total, active, paid and free license counts. The list can be searched by cafe, account, email, plan or license key. Administrators can also filter by plan type or status. Each row shows capacity, Cloud and Cafeteria access, AI balance, validity and status. Select Manage to open the customer workspace for plan, service, credit and billing operations.

Create the first Genesis license

When an account has no Genesis license, the customer detail page displays a license creation form instead of an empty result. Select an active Genesis plan and a future expiration date. Review the plan, expiration and country in the confirmation dialog. Select Create license to assign it directly to the customer account.

The account must have a cafe name and country before creation. Select Edit profile to add missing details. The plan defines both PC and console limits. The selected expiration date is valid through the end of that UTC day.

Available operations

  • Assign a Genesis plan. Manual licenses receive the selected plan capacity and expiration date. Stripe-managed subscriptions use the normal upgrade and downgrade rules, including immediate charges or scheduled changes.
  • Manage Cloud and Cafeteria. Cloud entitlement is updated on the license. Enabling Cafeteria also provisions or reactivates the matching tenant on handy.cafe; disabling it suspends that tenant. The two services are never synchronized while a database lock is held.
  • Grant AI credit. The Credit operations section shows the selected license's current AI balance before an administrator enters a top-up. Granting credit adds prepaid USD credit to the AI wallet and records an audit entry.
  • Grant member credit. Adds bonus credit to the HandyCafe member account with the same email address. The operation is unavailable when no matching member exists.
  • Change the next billing date. For Stripe subscriptions, the date is updated in Stripe and then synchronized to the local subscription and license. A scheduled plan change must be canceled first.
  • Refund a payment. An administrator selects a refundable Stripe charge, chooses a Stripe reason, enters a required internal explanation, and confirms the refund. Refunding does not cancel the subscription or remove product access.

Safety and audit behavior

Every mutating action requires confirmation in the dashboard. High-impact backend operations are restricted by the admin API key, validate ownership of Stripe charges, and write an append-only audit record. Payment history is loaded only when requested and is bounded to recent charges. Refunds use a unique idempotency key to prevent accidental duplicate submissions.

If an old license no longer has a recoverable plaintext key, automatic Cafeteria provisioning fails closed and the dashboard reports that an administrator must resolve the license credential first.

License country prefixes

New account-bound license keys use the two-letter country code from the customer's completed profile, such as GEN-TR-... for an admin-created Genesis license or HC-TR-... for a plan-neutral account license. Admin creation stops when the profile has no valid country. The system never creates a new GEN-XX-... or HC-XX-... key.

Updating the country field on an existing license does not silently rotate its active key. Administrators must coordinate the country correction and key rotation because the installed server must sign in again after its credential changes.