Changes to the SDKs, the CLI, the API, the customer portal, the dashboard and the website. Filter by what you use, or follow it in a reader with the Atom feed.
A flood of sign-in requests can no longer use up the hourly limit on emails a customer can set off. Sign-in links use at most half of it, so keys emailed from the portal, recovery and Device limit reached emails still go out. See Emails a customer can set off.
In the customer portal, the line under Manage billing said Stripe for every subscription. It now names Paddle for a key sold through Paddle.
In your customer portal, the buyer of several keys opens Keys you bought and gives each key to the person who will use it. KeyGrant emails the key to them unless you send your own key emails, and a new license.reassigned webhook tells your systems.
Link a Paddle account in Settings > Payments by pasting an API key, live or sandbox. A completed Paddle checkout issues the license key, refunds covering the whole payment or a chargeback take it back, a chargeback Paddle wins back returns it, and renewals and cancellations follow the subscription. The checkout lookup takes a Paddle transaction id, and the customer portal's Manage billing opens Paddle's portal.
A license model can send its key as a signed file buyers drop onto your app, or as an offline license file that works with no connection at all. Buyers can download the file again from the customer portal, and keygrant licenses file fetches it from the CLI.