Skip to Content
Paddle integrationOverview

Paddle integration

The Paddle integration creates licenses automatically when your customers pay with Paddle Billing . You keep selling with Paddle Checkout, overlay or inline, and Paddle stays your merchant of record: it collects the payment, handles taxes and sends the receipt. LicenseManager listens to the payments: each time a customer pays a price you chose, it creates the licenses they bought and emails them their keys.

Paddle Billing doesn’t generate or activate license keys: Paddle deprecated that feature, which only Paddle Classic had. This integration replaces it, with machine activations, offline validation and SDKs for Electron, Tauri and macOS.

Sell once, with one-time prices, or with a subscription, with recurring prices: monthly, yearly, or any period. A subscription license stays valid while the customer pays, gets every update, and expires on its own when they stop. See subscriptions.

You don’t write any code for the payments, and LicenseManager never touches your money. The only things it changes in Paddle are the refunds of the licenses canceled, and the subscriptions of the licenses you cancel, when you allow it.

How it works

  1. You connect your Paddle account with an API key. LicenseManager creates a notification destination on your Paddle account, so Paddle notifies it of payments.
  2. You map Paddle prices to policies: “paying this price creates licenses of this product, with this policy”.
  3. A customer pays one of these prices with Paddle Checkout, or subscribes to it.
  4. Paddle notifies LicenseManager, which creates one license per unit bought, or one per subscription, for the customer’s email, and emails them their keys.
  5. For a subscription, each renewal keeps the license valid for another period, and the license expires when the subscription ends.

What the integration does

  • Creates licenses for completed transactions of the one-time prices you mapped: one license per unit bought, each with its own key.
  • Creates one license per subscription to the recurring prices you mapped, with the policy’s machines times the quantity subscribed. It stays valid while the subscription is paid, with a grace period while Paddle retries a failed payment, includes every update, and expires when the subscription ends or is paused.
  • Records each subscription payment, and each failed one, as events, counted in your revenue and MRR.
  • Opens the Paddle customer portal from the customer portal, where customers update their payment method and cancel their subscription. Optional.
  • Cancels the subscription of the subscription licenses you cancel. Optional.
  • Creates or finds the customer from the email of the Paddle customer, and links them to it.
  • Emails the license keys to the customer, in one email per transaction, or when a subscription starts.
  • Records the price paid on each license, after discounts and before taxes.
  • Requests the refund of canceled licenses: when a customer cancels a license during its money back guarantee, or you cancel it, its share of the transaction is refunded. Paddle reviews refunds: the license shows the refund as pending until Paddle approves or rejects it. Optional, and on by default. See refunds.
  • Links each license to its Paddle transaction, and each customer to their Paddle customer.
  • Watches your prices and products: when a mapped price or product is archived in Paddle, the mapping is flagged.
  • Checks itself every day: when the API key is revoked or loses a permission, or the notification destination is deleted, the integration is flagged and the owners and admins of your organization are emailed.
  • Keeps live and sandbox apart: a live key for your live products, a key of a Paddle sandbox account  for your test products.

What the integration doesn’t do

Read this list before you start selling: in these cases, you have to act manually, in LicenseManager or in Paddle.

  • Custom (non-catalog) prices aren’t supported. Prices created on the fly for one transaction can’t be mapped: only the catalog prices of your products.
  • One-time licenses don’t renew. A license sold once with a policy that expires after a year isn’t extended when the customer pays again: they get a new license. To renew automatically, sell a subscription.
  • Subscription payments are never refunded by LicenseManager, and subscription licenses have no money back guarantee. Refund them from Paddle.
  • Refunds and chargebacks made in Paddle aren’t handled. Refunding a transaction from the Paddle dashboard doesn’t change its licenses: they stay valid until you cancel, expire or delete them.
  • Missed purchases aren’t created afterwards. While the integration is broken, for example after the API key is revoked, customers can still be charged without getting a license, and these licenses aren’t created once it’s fixed. See when the integration breaks.
  • Nothing else is written to your Paddle account: LicenseManager doesn’t create products, prices, customers, transactions or subscriptions, and can’t charge anyone.
  • One Paddle account per mode. An organization connects one Paddle account for its live products and one sandbox account for its test products. It can connect Stripe at the same time.