What a company buyer needs that a consumer does not
A person buying a license decides alone and pays by card. A company buyer has a process. Someone requests a quote, finance asks for an invoice with a VAT number, a security team sends a questionnaire, and the license is renewed once a year by someone who was not there at the start. The licensing setup has to survive that handover.
Seats: three ways to model them
| Model | How it works in Clavem | Good for | Gap |
|---|---|---|---|
| One key per seat | Quantity at checkout; each unit becomes a key with its own device limit | Per-user pricing | The buyer’s admin hands out keys and tracks who has which |
| One key with a higher device limit | A product with a limit of 10, or a key raised to 10 | A site license for a small team | One person leaving does not free their access, since the key is shared |
| A key per team | Separate checkout per team | Departments with separate budgets | More keys to manage |
A quantity of 3 in one line item issues three keys, up to 100 per line item. Several mapped products in one checkout issue licenses for each. To raise or lower a key’s limit later, use the dashboard or PATCH /v1/admin/licenses/:id; see the API reference.
What Clavem does not have
This is the list a buyer’s IT team will ask about, so put it on your sales page rather than discovering it at renewal.
- No team seats or admin console. There is no screen where a manager reassigns seats across a team.
- No single sign-on. Access is by license key.
- No outbound webhooks. Clavem does not call your systems when a license is created; if you want your CRM updated, read licenses with the management API.
- No floating or network licenses, where a pool of seats is lent out on demand.
- No merchant of record. Clavem does not collect or remit tax.
What a seat move looks like instead: the person leaving removes their device on the device page, or you disable their key, and the manager gives the key or a new one to a colleague. Disabling keeps the key answering with a reason, which beats deleting it.
Invoices, tax IDs and purchase orders
Stripe is the system for money, tax and invoices, and Clavem does not touch it. Three Stripe features matter here:
- Quantity at checkout. The buyer sets seats; the price scales.
- Tax ID collection. Stripe’s docs say to set
tax_id_collection[enabled]totruewhen you create a Checkout session, and a business buyer can enter a VAT or other tax ID. This is what reverse-charge invoices need, and Stripe or your accountant sets the rule. - Invoices. For buyers who pay by bank transfer on a purchase order, send a Stripe invoice. A payment that settles later, such as a bank debit, issues the license when Stripe reports the payment succeeded, not when the invoice is created. Clavem handles both
checkout.session.completedandcheckout.session.async_payment_succeeded.
Taxes are your responsibility when you sell directly. This is general information, not tax advice. The merchant of record article and the EU VAT article cover the choices.
Renewals and what happens when a payment fails
A company renews a subscription once a year, and the card on file expires. Clavem follows the Stripe subscription:
| Stripe state | License |
|---|---|
| Active or trialing | Valid |
Payment failed, Stripe retrying (past_due) |
Stays valid during retries |
| Renewal paid | Expiry extended to the new period end, plus three days of grace; revives an expired license |
| Canceled or unpaid | Expires |
| Fully refunded one-time payment | License disabled |
A partial refund changes nothing, and refunding a subscription invoice does not disable its license: cancel the subscription, or disable the license yourself. See failed subscription payments and grace periods.
The vendor questionnaire
Security teams ask where license data goes. Facts you can state about the licensing layer: Clavem stores the buyer’s email and name, the license, the device names and fingerprints your app sends, and the order. Validation can run offline with a public key, so installs need no call for most launches. Card data never reaches Clavem; it reads only the Stripe objects listed in Connecting Stripe, through a restricted key that it stores encrypted. Clavem launched in November 2026, is a one-person service made in Switzerland, and exports all licenses as CSV, which is part of the answer if a buyer asks about vendor risk. Offline verification means that tokens already issued keep working on devices until their refresh date even if the service were unavailable.
Recommended setup
| Setting | Suggested value | Why |
|---|---|---|
| License type | Annual subscription per seat | Fits budgets and renewals |
| Device limit | 2 per seat | A desktop and a laptop |
| Trial | 14 to 30 days, started by a sales form | Evaluation needs a contact and a clock |
| Updates | Releases endpoint, gated on a current license | Lapsed customers see that an update exists and renew |
Doing this with Clavem
Create a product per tier, connect Stripe with a restricted key, and map each price. Buyers receive keys by email and an order page. An MCP server lets you look up, issue, extend and revoke licenses from an assistant with a management API key. For the code in your app, follow the guide for your stack; the Qt, C# and Java guides suit many business desktop products.
Guides to follow
Questions
How do I sell several seats of my software to one company?
Set a quantity at checkout. Clavem issues one key for each unit, up to 100 per Stripe line item, and each key has its own device limit. The company assigns the keys to people.
Does Clavem handle VAT or act as the seller of record?
No. Clavem is not a merchant of record and does not handle tax. Stripe takes the payment into your account and you are responsible for tax, or you use a merchant of record such as Stripe Managed Payments.