Side by side
Creem facts are as of November 2026, from its pricing page and documentation.
| Clavem | Creem (as of November 2026) | |
|---|---|---|
| Price | Free for 50 active licenses; $29, $79 or $199 a month | No monthly or setup fee; per transaction |
| Fees on 100 sales of $49 | $29 plan, plus Stripe’s fee: about $201 | 3.9% plus 40 cents: $231.10 |
| Merchant of record | No | Yes: VAT, GST and sales tax collection and remittance in 50+ countries |
| License keys | Created when Stripe confirms a payment | A license key delivery item on a product, one key per unit bought |
| Device limits | Per license; buyer device page | An activation limit per key, and an expiry |
| Offline checks | Signed sgt1 token |
Not published |
| Downloads | Releases, order page, update endpoint | File downloads as a product delivery item |
| API | License API plus management API | Activate, validate and deactivate endpoints; SDKs, CLI and webhooks |
| Migration path | Import file; Lemon Squeezy and Dodo importers | Creem’s guide: products, prices and customers move; keys do not |
Fees on 100 sales of $49
Creem’s pricing page gives the example directly: on a $100 sale it takes $3.90 plus $0.40. On 100 sales of $49 that is $191.10 plus $40, $231.10. Payouts are made on the 1st and 15th of each month to a bank account or a USDC wallet.
With Clavem and Stripe’s standard 2.9% plus 30 cents (as of November 2026), the same sales cost $29 plus $172.10, $201.10. The difference is about $30 a month at this volume, and Creem’s fee covers the merchant-of-record work while Clavem’s does not. At 1,000 sales of $49 a month Creem costs $2,311, while Clavem Scale, which covers 50,000 licenses, costs $199 plus $1,721 of Stripe fees, $1,920.
How Creem’s keys work
In Creem’s dashboard you add a license key as a delivery item on a product, and choose an activation limit, such as three devices per key, and an optional expiry. After a purchase, each unit gets its own key. The key appears in four places:
- The order confirmation page, unless the product or checkout has a success URL, in which case the customer is sent back to your site and you must show the key yourself.
- The email receipt.
- The customer portal.
- Your backend, in the
license_keysarray of thecheckout.completedwebhook.
That success-URL behaviour is a real edge case. If you redirect buyers to your own page after payment, read the key from the webhook, or fetch the checkout with the id from the redirect, and show it on your page.
Clavem gives every buyer a private order page with the key, the downloads and your instructions, whether or not you use a success URL. It does not send outbound webhooks, so you cannot rely on a push to your own backend; use the management API to look licenses up.
Payouts, receipts and records
Creem’s pricing page says it pays out on the 1st and 15th of each month, to a bank account or a USDC wallet, and that it can split payments automatically between co-founders, affiliates and contractors. A merchant of record is the seller on the buyer’s receipt, and the money reaches you after it has taken its share.
With Clavem the sale stays in your Stripe account: the receipt, the customer record and the payout schedule are yours, set in Stripe. Clavem has no revenue splits, so a split between partners is something you handle outside it. That also means tax: you are the seller of record, so you register and file where the rules require. This page gives general information only; talk to a tax adviser about your own position.
When Creem is the better choice
- You want a merchant of record that collects tax, handles fraud and disputes, and issues invoices.
- You want checkout, keys, file delivery, revenue splits and usage-based billing in one place.
- You want webhooks into your own systems.
- Your sales are small enough that 3.9% plus 40 cents is less than a monthly plan.
- You do not have, or do not want, a Stripe account.
When Clavem is the better choice
- You want to keep your own Stripe account, customers and payout schedule.
- Your volume is high enough that a flat plan costs less than a percentage.
- You need to carry existing keys, and their devices, across without reissuing them.
- You want a signed token your app verifies offline.
Moving from Creem to Clavem
Clavem has no Creem importer, but the file importer takes any source. Export each key with its buyer email, activation limit, expiry and activated devices from Creem’s API into a CSV or JSON file, and import it. See importing licenses. Keys keep their strings. You then change the app’s calls from Creem’s endpoints to Clavem’s, and move checkout to Stripe Checkout or Payment Links.
Going the other way is harder. Creem’s Lemon Squeezy migration page lists existing license keys among the things that do not move to Creem: it issues new keys, and recommends validating the old ones in your backend until those customers switch. Teams moving from Lemon Squeezy may prefer an importer that keeps the old keys working. See moving from Lemon Squeezy.
Questions
How much does Creem charge?
As of November 2026 Creem charges 3.9% plus 40 US cents per successful transaction, with no monthly or setup fees. Its pricing page also lists no international card fees. A partner plan with custom pricing is available for higher volumes.
Can Creem keep my existing Lemon Squeezy license keys?
Creem's own migration page says no. Creem issues new keys for purchases made on Creem, and suggests you keep validating Lemon Squeezy keys in your backend until those customers move. Clavem has an importer that keeps existing key strings.
Where do Creem customers find their key?
On the order confirmation page when there is no success URL, in the email receipt, and in the customer portal. Your backend also receives it in the checkout.completed webhook.