License lifecycle: publish, buy, renew, and expire

Prepare your software for sale

Use Update file to replace the current file. You do not need to create a GitHub Release.

1
Complete payment once. Refreshing or replaying confirmation must not issue a second key.
2
Open Library for the purchased key and exact release; secrets are revealed only to the entitled buyer.
3
Licensed downloads fail closed if the purchase is not bound to an approved immutable release.
4
Use a random installation ID, keep the refresh token in OS-protected storage, and never use hardware fingerprints.
5
If all seats are used, deactivate an old installation from Library before activating another.
6
Apps should verify ES256, issuer, audience, time claims, key ID, and the purchased version policy.

1
The renewal screen shows the exact next amount, currency, date, and same-duration successor plan.
2
Enabling auto-renew requires explicit confirmation of that charge and is unavailable without an exact quote.
3
A period extends only after the wallet debit is confirmed. Retries are idempotent and technical failures retry.
4
Manual renewal uses a signed expiring link bound to the key and a server-validated plan.
5
A refund caps the authoritative period and cannot be undone by older renewal history.

1
After economic end, new verification and downloads fail closed; the worker expires the key and tears down sessions.
2
Already issued offline tokens can remain valid only until their signed expiration time.
3
Seller revocation is audited and retried until activation teardown and notification side effects complete.
4
Insufficient balance has a specific notification. Technical failures are not mislabeled and retry after cooldown.
5
If fulfillment is delayed or state disagrees, keep the payment reference and contact support; do not buy again.