What Gumroad gives a software seller
Gumroad is a storefront, a checkout and, since 1 January 2025 by its own pricing page, a merchant of record that handles sales tax collection and remittance worldwide. Its pricing page lists 10% plus 50 cents on direct sales and 30% on sales through Gumroad Discover. For software, it adds license keys: enable a license key block on the product, and each buyer gets a key in the receipt and on the product page.
Gumroad’s license key help describes the model plainly. Your app calls a verify endpoint with product_id and license_key. “License key enforcement is completely up to the creator”, and Gumroad “performs no additional license key verification”. Each verify call increments a usage count unless increment_uses_count is false, and you decide how many uses a key gets. A multi-seat option sets a quantity on one key.
That is a light system, and for a small app it may be all you need. Stay on Gumroad if you value the merchant of record work and the storefront more than the fee, and the key check does what you need.
Where people outgrow it
| Need | Gumroad | Clavem with Stripe |
|---|---|---|
| Limit installs per key | A usage count per key, which you interpret; not per device | A device limit, with a name per device and a page where buyers remove one |
| Free a seat when someone changes computers | You correct the count from the Sales dashboard | The buyer removes the device on /licenses/manage with no account |
| Work offline | Your app builds its own offline cache | A signed token the app verifies with a public key |
| Fee on sales | 10% plus 50 cents on direct sales | Stripe’s processing fee and a flat Clavem plan, with no cut of sales |
| Tax | Gumroad collects and remits as merchant of record | Yours, through Stripe, or Stripe Managed Payments |
| Storefront and discovery | Yes | No: use Stripe Checkout or a Payment Link on your own site |
| Email list of buyers | Gumroad’s audience tools | Not included |
If you need the merchant of record and the storefront, a flat price does not replace them. If you want device limits and a cheaper fee at volume, and you are ready to handle tax, the move is worth costing. The pricing page has the break-even by plan, and the comparison with Gumroad goes further.
Your app changes more than a hostname
Clavem’s License API follows the Lemon Squeezy shape, not Gumroad’s. Moving from Gumroad means changing the calls, not only the host:
| Gumroad | Clavem |
|---|---|
POST https://api.gumroad.com/v2/licenses/verify with product_id and license_key |
POST https://clavem.io/v1/licenses/validate with license_key, and instance_id once activated |
| No activation step; a use count rises with each check | POST /v1/licenses/activate with license_key and instance_name once per device |
uses counts checks |
activation_usage counts active devices; activation_limit is the cap |
| A refunded or disputed flag in the response | status of disabled after a full refund, and valid: false |
| No offline token | token, signed with Ed25519 |
Plan the code in three parts: an activation flow on first run, a validate call at launch with the stored instance_id, and the offline fallback with the signed token. The guide for your stack has all three, for example Swift or Electron.
Moving existing keys
- Get your customers’ keys out of Gumroad. Check what your sales export includes, and whether Gumroad’s sales API returns each sale’s license key; Clavem’s import needs a
keyand anemailfor each row. - Import them with a CSV or JSON file. Clavem keeps each key string as written and matches it without regard to case. Add
activation_limitandexpires_atif you want them, since Gumroad has no device limit to carry over. Rows are checked one by one, and running the import again is safe. - Set a sensible device limit on the product. An imported key with no devices shows 0 of 3 until your app calls
activate. - Ship the app update, and run both systems for a while: try Clavem first and, for keys Clavem does not know, fall back to Gumroad’s verify endpoint until the import is complete and old app versions are gone.
Imported licenses have no order page, because the import creates licenses, not orders. Those buyers get updates through your app’s update check or your site. New buyers, after you connect Stripe, get the full order page.
What you take on
- Tax. When you leave a merchant of record, VAT and sales tax become yours, or you adopt another merchant of record. This is general information, not tax advice; ask an accountant before you switch.
- A checkout. Clavem has no hosted checkout. Use Stripe Checkout, Payment Links or your own page.
- Support. Buyers contact you, not Gumroad.
Recommended setup
| Setting | Suggested value | Why |
|---|---|---|
| License type | Whatever your Gumroad product used | Do not change the deal for existing buyers |
| Device limit | 3 on the product; keep imported keys at their own limits | Gumroad had no device limit to preserve |
| Trial | As today | Moving platforms is not the time to change it |
| Updates | Releases endpoint | Imported keys can check for updates too |
Doing this with Clavem
Start with the Gumroad migration guide, create a product, and import a few keys first. Connect Stripe and test one purchase before you move traffic. The import docs list every column.
Guides to follow
Questions
How does Gumroad's license key check work?
Your app sends the product id and the license key to Gumroad's verify endpoint. Gumroad says enforcement is completely up to the creator, and that checking on each launch increments the usage count unless you set increment_uses_count to false. The count is per key, not per device.
Can I keep my customers' existing Gumroad keys?
Yes, if you can export them. Clavem's import keeps key strings exactly as written, with the buyer, limit and expiry. Your app then calls Clavem instead of Gumroad. Check what your Gumroad export or sales API includes for each sale.