Contents
Chapter 6. Licenses and Site Activations
Sell a product that may be used on a limited number of sites: how licenses and seats work, how sites are recognized, the rules for moving a license to another site, and what customers and administrators can do.
What Licenses Do
Some products are meant to be used on a certain number of websites: a template, an extension, or a service that works on one site per purchase. For these, set the product's Purchase Type to Licenses per site. Each purchase then creates a license (and so does access you grant by hand), with a number of seats. Each seat can be used by one site at a time.
A site gets a seat when the software on it asks for one. Your software (or a service you run) calls PaddleSubs' licensing API with the customer, the product and the site's address; PaddleSubs binds the site to one of the customer's seats, or explains why it can't. That binding is an activation.
A license also grants access like any other product: it adds the product's user groups, appears among the customer's Access Subscriptions, and ends when the access it was bought with ends. What it adds is the count of sites.
Note
PaddleSubs trusts the software that calls the API to have checked that the customer really controls the site. Only give API access to software and services that do. See the section called “Tokens, Service Users and Permissions”.