Paddle’s licensing platform is flexible and easy to configure. Follow this guide to find the best licensing option for you.
A license key or code is a data string that verifies authorised software product access. Licensing remains a popular tool for on-the-shelf software, however, the emergence of cloud computing software has enabled more and more sellers to move to a user management system with log ons and passwords.
At Paddle, there are a variety of options for flexible license usage.
If you have created a one-off purchase product, you can deliver the customer a license from a list of licenses which you have inputted (usually via a .txt file). When the list of licenses has been exhausted, you will receive an email suggesting that you should create more licenses.
Why/When?
- This is the quickest way to test a product.
- If you do not require remote verification.
- One-off product purchases.
You’ll find the option to deliver licenses from a pre-populated list in the Seller Dashboard.
Paddle uses webhook fulfillment and alerts which can be used to trigger your own license server to assign/allocate licenses for subscriptions or one-off purchases.
Why/When?
- Building own license server enables greater flexibility and control.
- Subscriptions with licenses.
- If you already have a license server in place, can integrate seamlessly.
Read our docs on Fulfillment Webhooks here for more information
This is Paddle’s licensing system / trial technology and has to be used with our Paddle SDK. The SDK was built with the core function of providing checkout, licensing, and trials to software products.
Why/When?
- Automatic remote verification
- Subscriptions with licenses.
- When you are using the Paddle SDK with your product.
Find out more about the Mac SDK and Windows SDK.
Read our docs on the Paddle License Framework here for more information (Mac) (Windows C#/.Net)