Clavem

Paddle sellers: adding license keys to software sold through Paddle

Paddle Billing does not generate license keys, and Paddle tells sellers to build fulfillment themselves from webhooks. Clavem has no Paddle connector, so you either call Clavem's management API from your own Paddle webhook handler, or move your payments to Stripe and let Clavem issue keys by itself.

What Paddle says about license keys

Paddle Classic could generate license keys and deliver files. Paddle Billing, its current platform, does not. Paddle’s feature comparison lists “Paddle-led fulfillment, including product delivery and license key generation” as deprecated, and its migration plan says “Product delivery and license key generation aren’t handled by Paddle in Paddle Billing. We recommend building this functionality yourself.” The tool it points you to is webhooks: Paddle Billing, it says, includes webhooks and a unified event stream that you can use to build your own fulfillment workflows.

Paddle is a merchant of record, so it handles tax and the checkout. What you need is the part after payment: a key, a limit on devices, a download and an answer for your app. That is the gap this page covers.

Two ways to get keys

Keep Paddle, issue keys yourself Move payments to Stripe
Who takes payment and handles tax Paddle, as merchant of record You, through Stripe, or Stripe Managed Payments
How keys are issued Your webhook handler calls Clavem’s management API Clavem issues them when Stripe reports a paid checkout
Renewals, expiry and refunds You map Paddle’s events to Clavem calls Automatic: Clavem follows Stripe’s events
Code you write A webhook endpoint with Paddle signature checks, plus calls to Clavem The three License API calls in your app
Fits when You want to stay on Paddle’s merchant of record service You are ready to own tax or use Stripe Managed Payments

Clavem does not have a Paddle connector, so the first column is real engineering, not configuration. If you do not want to maintain a fulfillment service, the second column is shorter. The Paddle comparison, the alternatives page and the migration guide go further.

Keeping Paddle: the webhook handler

The pieces:

  1. Receive transaction.completed. Paddle names transaction webhooks as the way to build fulfillment. Verify Paddle’s signature on every request, as its documentation describes, before you act.
  2. Work out the buyer and the product. The transaction identifies the customer and the items. Look up the customer’s email through Paddle’s API, and map each Paddle price to a Clavem product id.
  3. Create the license. Call Clavem with a management API key:
// Server only: the management API key must never reach a browser or an app.
async function issueLicense({ productId, email, name, expiresAt = null }) {
  const res = await fetch('https://clavem.io/v1/admin/licenses', {
    method: 'POST',
    headers: {
      Authorization: `Bearer ${process.env.CLAVEM_API_KEY}`,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
      product_id: productId,
      email,
      name,
      expires_at: expiresAt, // null means never; omit to follow the product's validity
    }),
  });
  if (!res.ok) throw new Error(`Clavem ${res.status}: ${await res.text()}`);
  return (await res.json()).data; // includes key, status and order_url
}

This follows the API reference’s request and response.

  1. Send the key. The response contains the license key and an order_url, the buyer’s private order page with the key and downloads. Email them with your own email service. Check in your dashboard what Clavem itself sends for licenses made this way before you rely on it.
  2. Make it idempotent. Paddle may deliver a webhook more than once. Store the Paddle transaction id with the license id you created, and skip a transaction you have already handled. The management API’s create call does not take an idempotency key, so a retry would create a second license.

The rest of the lifecycle is on you

Stripe events do not apply, so Clavem does not see a Paddle renewal or refund. Handle them from Paddle’s webhooks:

Paddle event Your handler calls
A subscription renews PATCH /v1/admin/licenses/:id with a later expires_at
A subscription is canceled, or ends Nothing, if expires_at already marks the end, or a PATCH to set it
A refund PATCH with { "disabled": true }
A seat count changes Create or disable licenses to match

Licenses created by hand or by API have no Stripe subscription, so Clavem never changes them by itself. Creating licenses this way counts against your plan like any other, and past the plan’s limit the call answers 402 plan_limit; Stripe purchases are not blocked, but these are. Check the limits on the pricing page.

Moving to Stripe

If you move payments to Stripe, none of the above is needed: connect a restricted key, map each Stripe price to a Clavem product, and every paid checkout issues a key, an order page and an email. Existing customers’ keys can be imported with a CSV or JSON file, keeping the key strings; see importing licenses. Leaving Paddle means leaving its merchant-of-record service, so tax becomes yours, or you adopt Stripe Managed Payments. This is general information, not tax advice.

The app side is the same either way

Your app calls the same three endpoints: activate once per device, validate at launch, deactivate when a customer moves. It stores the signed token and verifies it offline. Pick a guide: C#, Swift or Electron.

Setting Suggested value Why
License type Match what your Paddle product sells Do not change the offer while you change the plumbing
Device limit 2 or 3 Standard for a personal license
Trial In the app No license is needed before purchase
Updates Releases endpoint Files and update checks work for keys made through the API too

Doing this with Clavem

Create a product, generate a management API key under Developers, and write the handler for your first product. Test it with Paddle’s sandbox before live traffic. If most of your code is the handler and its edge cases, consider whether moving payments is simpler.

Guides to follow

Questions

Does Paddle Billing generate license keys?

No. Paddle's migration docs say that Paddle-led fulfillment, including product delivery and license key generation, has been deprecated, and that product delivery and license key generation are not handled by Paddle in Paddle Billing. It recommends building the functionality yourself with webhooks.

Does Clavem connect to Paddle?

No. Clavem reads events from a Stripe account and has no Paddle connector. With Paddle you create licenses through Clavem's management API from your own server.

Sources

  1. Paddle Developer Docs, migration plan (checked November 2026)
  2. Paddle Developer Docs, Classic and Billing feature comparison (checked November 2026)