License delivery
After the order is confirmed, the system can create a customer record, generate a license key, and send the license to the order email.
- Some payment methods are instant; manual payment methods require operator confirmation.
- Email delivery depends on the configured mail service and can be retried by support.
- The order page can show payment status and license delivery status through a private link.
Activation checks
The product verifies the license through the public API before enabling licensed access.
- The API checks product identifier, license status, expiry, activation count, binding rules, and feature flags.
- The product can cache recent successful checks to reduce requests and allow a short offline grace period.
- If the license expires or is suspended, the product should show the configured customer-facing notice.
Updates and downloads
Update access can depend on license status, support period, product version, and signed release manifests.
- Products should verify update signatures before installing downloaded packages.
- Update packages should be downloaded only through authorized public release links.
- If update entitlement is expired, the product can still show renewal instructions.
Binding changes
Moving a site to a new domain or server may require a rebind request.
- The customer should open a ticket or portal request with the old and new domain details.
- Operators can allow limited self-service rebinds or review each request manually.
- Repeated rebind requests can be treated as a risk signal.