How the decoder works
A Clavem token has three parts joined by dots: sgt1, the payload and the signature. The payload is a JSON object encoded as base64url. The tool splits the token, decodes the payload and lists each claim with its meaning. Times are shown in UTC next to the raw number of seconds since 1970.
If you add a public key, the tool verifies the Ed25519 signature over the text sgt1.<payload> using Web Crypto, the same steps as the code in the offline verification guide. It then runs the checks an app should make: the version is 1, the license is valid, exp and refresh_by are in the future and, if you give them, the product id and license key match.
The two examples
Try with the demo asks the live License API for a token for Clavem's public demo license and decodes it. This is the only time the page contacts a server, and only when you press the button. This page does not hold the demo product's public key, so the signature is not checked.Try a self-signed example makes a key pair in your browser, signs a sample token and fills in both, so you can see a full verification without any network call.
Reading the result
Decoding is not verifying. Anyone can write a token with any claims. Only a signature that verifies with the right public key shows the token came from Clavem and is unchanged. A verified token still only says what the license looked like when it was issued: if you revoke the license later, the token stays valid until refresh_by. Your app decides what happens after that.
Questions
Is it safe to paste a token here?
The token is decoded by code running in your browser and is not sent to any server. It still contains the buyer's email address in plain text, so do not post tokens in public places.
Why can the token be read without a key?
A token is signed, not encrypted. The payload is only base64url encoded JSON, so anyone can read it. The signature is what proves Clavem issued it and that nobody changed it.
The signature does not verify. What is wrong?
Usually one of three things: the public key belongs to a different product (each product has its own pair), the token was cut or changed when it was copied, or the payload was edited. Copy the token again and check that the key is the one shown on the product page.
What does refresh_by mean?
It is the time after which your app should ask the server again. Clavem sets it to 14 days after the token was issued. Before it, an offline app can trust the token. After it, the app should validate online.
Every claim and the verification code in five languages are in the offline verification guide. To make a token with your own test key, use the Ed25519 key pair generator. More tools are listed under free tools.