This is only applicable to Paddle Classic
There are four ways to deliver your product to customers:
Server Notification (Webhook)
This is what the majority of our sellers use. Webhooks are HTTP GET/POST requests sent to your server, used to receive data from Paddle and for your server to communicate back. This is typically used to send order-specific data to a customer after the payment process (e.g. a unique license code). It is our most flexible fulfillment method, which allows you to build your own user database from the data you receive. For more information regarding this, click here.
An email with download instructions will be sent directly to the customer with a link to the file uploaded* or the download URL specified.
* Please note that any files uploaded and hosted by Paddle will not be order-authenticated (and will provide a static download link for all buyers). If you’re selling a product that does not require any order verification to use it (such as e-books and graphic files), we would strongly recommend that you consider hosting these files using an alternative provider.
Upload a plain text document (
.txt) file containing a list of licenses (newline-separated). When a customer purchases the product, they will be emailed a license key and any information/instructions that you have specified. Once this list has been exhausted, it will throw an error and you will be contacted by someone at Paddle requesting more license codes be added.
Paddle License (SDK)
Generate licenses specifically for use with your Mac application using our licensing feature within the Paddle SDK. For more information on how to build this integration, click here.