CodeHawkeLicense keys, device limits, and revocation — all from the order.
Issue license keys at checkout, track activations per device, and revoke access automatically on refund or cancellation. No separate license server — entitlement state lives in the same order record as everything else.
Most license systems are detached from the sale.
Separate license servers mean a refund in Stripe doesn't automatically revoke the key. A key shared between users won't show up in your commerce record. When a buyer has a license issue, there's no order context next to it. CodeHawke treats license keys as a fulfillment type — same order, same record, same support surface.
License key issuance
Issue a unique key per order from a pre-loaded pool. Keys deliver instantly with the purchase confirmation.
Device activation limits
Set how many devices can activate a single license. Buyer activates a device, count decrements automatically.
Seat and usage tracking
Track which devices are activated, when, and from which IP. Visible on the order record for support use.
Revocation on refund
When an order is refunded, the license key is deactivated automatically. No manual step required.
Access state management
Gate software, API access, or premium features behind license validity. Access state syncs with order state.
Key validation endpoint
Your software can call the CodeHawke API to validate a license key at runtime — online or periodic check.
Issue on purchase. Revoke on refund. No manual steps.
The license lifecycle is driven by the order state. When the order is paid, the key is issued. When the order is refunded, the key is revoked. No webhook to configure, no cron job to run.
License keys that live and die with the order.
Automatic issuance, device limit enforcement, refund revocation — all tied to the order record, all without a separate license management system.
Try CodeHawke