How a license key works
- A buyer pays, for example through Stripe Checkout.
- A licensing service creates a unique key for that purchase and sends it to the buyer.
- The buyer pastes the key into the app.
- The app sends the key to the licensing service, which answers whether it is valid, for which product, and how many devices may use it.
What a key looks like
Clavem keys are 25 characters in five groups, for example 7K4QX-9WZ2P-H5RB8-M3TQA-0DFNC. They use Crockford base32, which leaves out I, L, O and U, so a key read aloud or retyped from a screenshot still works; each key carries 125 random bits. The format matters less than two other things: the key must be random, and the server, not the app, decides whether it is valid.
Keys versus signed tokens
A key is a credential the buyer types. A signed token is what the server returns after checking it: a small document saying “this key is valid for product 75 until 1 December”, signed with the product’s private key. Your app can verify that signature with the public key it ships, so it keeps working offline. See offline verification.
Where keys go wrong
- Keys generated in the app. If the app can compute valid keys, so can anyone who reads its code. That is how key generators (“keygens”) work. Keys must come from a server and be checked against it, or against a signature only the server can make.
- No device limit. A key without an activation count can be posted online and used by everyone. A limit of two or three devices covers a laptop and a desktop without inviting sharing.
- Hard-coded checks against one hostname. Apps that call a licensing API directly break when the vendor closes, as Lemon Squeezy sellers found when it announced the end of processing for 31 March 2027. Keep the hostname in one place, and store the last signed answer so the app still works while you move.
License keys in Clavem
Clavem creates a key the moment Stripe confirms a payment, one per seat bought, and emails it with the download link. Your app calls POST /v1/licenses/activate once per device and POST /v1/licenses/validate on start. Both are described in the API reference, with code for each language in the guides.
Questions
Is a license key the same as a serial number?
In everyday use, yes. Older software printed serial numbers on the box; today most software sold online sends a license key by email right after payment. Both identify one purchase.
Can a license key be shared?
It can be typed into any copy of the app, which is why most licensing services count activations. When a key reaches its device limit, further activations are refused until the buyer frees a seat.