How it works
The server marks the license as no longer valid. From then on, validation answers valid: false, activation is refused, and the update check no longer returns download links for that key. The record stays, so the key keeps answering with a reason instead of “not found”. Typical triggers are a refund, a chargeback, abuse such as a key posted publicly, and a seller’s decision.
Triggers in Clavem
A revoked license has the status disabled. Three things disable one:
- The dashboard. The Disable action on the license.
- The management API.
PATCH /v1/admin/licenses/:idwith{ "disabled": true }. Sendfalseto enable it again. - A full refund. Stripe’s
charge.refundeddisables every license from that order. A partial refund changes nothing. Refunding a subscription invoice does not disable its license: cancel the subscription, which expires it, or disable the license yourself.
Clavem listens to six Stripe events, and none of them is a dispute. A chargeback therefore does not revoke by itself. Disable the license by hand.
Disabled outranks everything. A disabled license stays disabled whatever Stripe later reports, until you enable it, and it does not count against your plan’s license limit.
The limit: offline devices
A signed token says what the license looked like when it was issued. A device that cannot reach the server keeps verifying the token it holds until its refresh_by date, which is iat plus 14 days.
A worked example with invented dates:
| Date | Event |
|---|---|
| 1 Dec | A device validates online. The token has iat of 1 Dec, so refresh_by is 15 Dec. |
| 2 Dec | The seller disables the license. The device is on a plane. |
| 2 to 15 Dec | The device is offline. The token still verifies, so the app keeps running. |
| 15 Dec | refresh_by passes. The app asks the customer to connect. |
| Any online launch | Validate returns 200 with valid: false. The new token says valid: false too. |
The window is a trade. A shorter one makes revocation reach offline machines sooner and bothers honest travellers sooner. Clavem uses 14 days. An app can also be stricter than the default if its own policy requires it.
License revocation versus expiry and deactivation
Expiry is scheduled and automatic. Revocation is a decision. Deactivation frees one seat and leaves the license valid. Revoking affects every device on the key.
How Clavem handles it
Disabling returns status: "disabled" in the license_key object. Validation of a known disabled key answers HTTP 200 with valid: false, so read valid and not just the status. Activation of a disabled key answers 400 with This license key has been disabled. Enabling restores active when a device is using the license and inactive when none is. See connecting Stripe for every event, and offline verification for the token fields.
Questions
Does revoking a license stop the software at once?
Not on a device that is offline. A signed token already on the machine still verifies until its re-validation date, which is up to 14 days after it was issued. Online devices learn at their next check.
Can a revoked license be switched back on?
Yes. In Clavem a disabled license stays disabled until you enable it, and enabling restores it as active if a device is using it or inactive if not.