nikosdmsi

DMSI DDLS – Digital Downloads, Licensing & Subscriptions (DDLS) is a comprehensive solution for software vendors, digital product sellers, and subscription-based businesses who need to manage licenses, subscriptions, and digital downloads through WooCommerce.
<h4>Why Choose DDLS?</h4>
Unlike expensive alternatives that cost $500-700/year, DDLS provides enterprise-grade licensing features completely free. Built specifically for WordPress and WooCommerce, it integrates seamlessly with your existing store.
<h4>Core Features</h4>
License Management
<ul>
<li>Generate unique license keys automatically on purchase</li>
<li>Set activation limits per license (unlimited or fixed number)</li>
<li>Track activations with detailed site information</li>
<li>License expiration with automatic notifications</li>
<li>License status management (active, expired, suspended, revoked)</li>
<li>Transfer licenses between customers (with admin approval)</li>
<li>Bulk actions (activate, suspend, delete)</li>
</ul>
Subscription Management
<ul>
<li>Custom subscription system (no WooCommerce Subscriptions required)</li>
<li>Subscription tracking and status management</li>
<li>Manual renewal order creation</li>
<li>Grace periods for expired subscriptions</li>
<li>Admin notifications for renewals due</li>
</ul>
Digital Downloads
<ul>
<li>Secure file delivery with signed URLs</li>
<li>Version management for software products</li>
<li>Multiple files per product version</li>
<li>Platform-specific downloads (Windows, Mac, Linux)</li>
<li>Download tracking and logging</li>
<li>Access control based on license status</li>
</ul>
Customer Portal
<ul>
<li>Self-service license management</li>
<li>View and download purchased products</li>
<li>Deactivate sites from the portal</li>
<li>View subscription status</li>
<li>Download history</li>
<li>Account settings</li>
</ul>
Email Notifications
<ul>
<li>30+ email templates</li>
<li>Customer and admin notifications</li>
<li>License lifecycle emails (created, activated, expiring, expired)</li>
<li>Subscription status emails</li>
<li>Email queue with retry logic</li>
<li>Email logs</li>
</ul>
REST API
<ul>
<li>License validation endpoint</li>
<li>Activation and deactivation endpoints</li>
<li>Download endpoints</li>
<li>Secure API key authentication</li>
<li>Rate limiting protection</li>
</ul>
Admin Dashboard
<ul>
<li>Overview widgets with key metrics</li>
<li>License status summary</li>
<li>Recent activity feed</li>
<li>Quick actions for common tasks</li>
</ul>
Reports
<ul>
<li>License reports</li>
<li>Customer reports</li>
<li>Basic analytics</li>
<li>Export capabilities</li>
</ul>
Security
<ul>
<li>4 user roles with granular permissions</li>
<li>API key authentication</li>
<li>Audit logging</li>
<li>GDPR compliance tools</li>
</ul>
<h4>Premium Extensions (Coming Soon)</h4>
Extend DDLS functionality with optional premium extensions:
<ul>
<li>Update Server – Automatic plugin/theme updates</li>
<li>Subscriptions Pro – Automatic renewals, payment retry, dunning</li>
<li>Analytics – Advanced revenue analytics and reporting</li>
<li>Webhooks – Outbound event notifications</li>
<li>Team Licenses – Multi-user license management</li>
<li>Template Editor – Customize email templates with live preview</li>
<li>And more…</li>
</ul>
<h4>Perfect For</h4>
<ul>
<li>Software developers selling plugins, themes, or desktop applications</li>
<li>Digital product sellers needing license control and secure downloads</li>
<li>Subscription-based businesses with recurring billing needs</li>
<li>Agencies managing client licenses and software access</li>
<li>E-book, course, or media creators with download access control</li>
<li>Anyone selling digital products through WooCommerce</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 6.0 or higher</li>
<li>WooCommerce 7.0 or higher</li>
<li>PHP 8.0 or higher</li>
<li>MySQL 5.7 or higher</li>
</ul>
<h4>Documentation</h4>
Comprehensive documentation is available at <a href="https://dmsi.gr/docs/ddls/" rel="nofollow ugc">dmsi.gr/docs/ddls/</a>
<h4>Support</h4>
For support questions, please visit <a href="https://dmsi.gr/support/get-help/" rel="nofollow ugc">dmsi.gr/support/</a>
<h3>Privacy Policy</h3>
DMSI Digital Downloads, Licensing & Subscriptions stores the following data:
<ul>
<li>Customer information (name, email) linked to WooCommerce orders</li>
<li>License keys and activation records</li>
<li>Site URLs where licenses are activated</li>
<li>Download logs for security auditing</li>
<li>Email logs for delivery tracking</li>
</ul>
This data is stored in your WordPress database and is not transmitted to external servers except when customers activate licenses (their site URL is recorded).
For GDPR compliance, customers can request data export or deletion through the Customer Portal or WordPress privacy tools.

DMSI DDLS – Digital Downloads, Licensing & Subscriptions

Complete software licensing, subscription management, and digital product delivery for WooCommerce.

Kevin Burkholder

{eac}SoftwareRegistry Distribution SDK is an extension plugin to <a href="https://swregistry.earthasylum.com/software-registration-server/" rel="nofollow ugc">{eac}SoftwareRegistry Software Registration Server</a>.
The Software Registry Distribution SDK is used to generate a custom PHP package that you can include in your software project to register your product with your registration server and manage that registration.
A custom version of this document is included in the generated SDK package.
The SDK provides most of the PHP code you will need to implement the Application Program Interface with your Software Registration Server.
Included with the Software Registration SDK package…
<ul>
<li><code>(your_productid)_registration.(wordpress_or_filebased).trait.php</code></li>
<li><code>(your_productid)_registration.includes.php</code></li>
<li><code>(your_productid)_registration.interface.php</code></li>
<li><code>(your_productid)_registration.interface.trait.php</code></li>
<li><code>(your_productid)_registration.refresh.php</code></li>
<li><code>(your_productid)_registration.readme.md</code></li>
</ul>
<h4>Software Registry Implementation</h4>
After extracting the <code>(your_productid)_registration.zip</code> file, move the <code>(your_productid)_registration</code> folder to your project.
In your project or class file, include <code>(your_productid)_registration/(your_productid)_registration.includes.php</code> to load the required interface and traits.
Your class file must then:
<ul>
<li>implement <code>\(your_namespace)\Interfaces\(your_productid)_registration</code></li>
<li>use <code>\(your_namespace)\Traits\(your_productid)_registration_(wordpress_or_filebased)</code></li>
</ul>
Example:
<pre><code>include "(your_productid)_registration/(your_productid)_registration.includes.php";

class <your_classname> implements \(your_namespace)\Interfaces\(your_productid)_registration
{
 use \(your_namespace)\Traits\(your_productid)_registration_(wordpress_or_filebased);
 ...
}
</code></pre>
(your_productid)_registration.interface.php will have your product and registration server API constants.
<pre><code>const SOFTWARE_REGISTRY_PRODUCTID = '{your_software_registry_productid}';
const SOFTWARE_REGISTRY_HOST_URL = '{your_software_registry_host_url}';
const SOFTWARE_REGISTRY_CREATE_KEY = '{your_software_registry_create_key}';
const SOFTWARE_REGISTRY_UPDATE_KEY = '{your_software_registry_update_key}';
const SOFTWARE_REGISTRY_READ_KEY = '{your_software_registry_read_key}';
</code></pre>
<h4>Using The API</h4>
API Parameters
API parameters are passed as an array:
<pre><code>$apiParams =
[
 'registry_key' => 'unique ID', // * registration key (assigned by registry server)
 'registry_name' => 'Firstname Lastname', // registrant's full name
 'registry_email' => 'email@domain.com', // * registrant's email address
 'registry_company' => 'Comapny/Organization Name', // registrant's company name
 'registry_address' => 'Street\n City St Zip', // registrant's full address (textarea)
 'registry_phone' => 'nnnnnnnnnn', // registrant's phone
 'registry_product' => 'productId', // * your product name/id ((your_productid))
 'registry_title' => 'Product Title', // your product title
 'registry_description' => 'Product Description', // your product description
 'registry_version' => 'M.m.p', // your product version
 'registry_license' => 'Lx', // 'L1'(Lite), 'L2'(Basic), 'L3'(Standard), 'L4'(Professional), 'L5'(Enterprise), 'LD'(Developer), 'LU'(Unlimited)
 'registry_count' => int, // Number of licenses (users/seats/devices)
 'registry_variations' => array('name'=>'value',...), // array of name/value pairs
 'registry_options' => array('value',...), // array of registry options
 'registry_domains' => array('domain',...), // array of valid/registered domains
 'registry_sites' => array('url',...), // array of valid/registered sites/uris
 'registry_transid' => '', // external transaction id
 'registry_timezone' => '', // standard timezone string (client timezone)
 'registry_locale' => '', // standard locale/language code
];
</code></pre>
* Required values (registry_key not required when creating a new registration).
<blockquote>
If setting registry_transid, the recommended (not required) format is <code>{id}|{source}|{suffix}</code> where {id} is the transaction id, {source} indicates the source of the transaction, and {suffix} may be used as needed.
</blockquote>
Any additional fields passed wil be saved as custom fields.
Although typically set by the Software Registry server, with the proper option setting, the API may override:
<pre><code>[
 'registry_status' => 'status', // 'pending', 'trial', 'active', 'inactive', 'expired', 'terminated'
 'registry_effective' => 'DD-MMM-YYYY', // Effective date
 'registry_expires' => 'DD-MMM-YYYY', // Expiration date or term ('30 days', '1 year',... added to effective date)
];
</code></pre>
Payment information may be posted with:
<pre><code>[
 'registry_paydue' => float, // amount to be paid/billed,
 'registry_payamount' => float, // amount paid,
 'registry_paydate' => 'DD-MMM-YYYY', // date paid
 'registry_payid' => 'payment id' // transaction id/check #, etc.
 'registry_nextpay' => 'DD-MMM-YYYY', // next payment/renewal date
];
</code></pre>
API Requests
Create/request a new registration…
<pre><code>$response = $this->registryApiRequest('create',$apiParams);
</code></pre>
Activate an existing registration…
<pre><code>$response = $this->registryApiRequest('activate',['registry_key' => '<registrationKeyValue>']);
</code></pre>
Activate and Update an existing registration…
<pre><code>$response = $this->registryApiRequest('activate',$apiParams);
</code></pre>
Deactivate an existing registration…
<pre><code>$response = $this->registryApiRequest('deactivate',['registry_key' => '<registrationKeyValue>']);
</code></pre>
Verify or Refresh an existing registration…
<pre><code>$response = $this->registryApiRequest('verify',['registry_key' => '<registrationKeyValue>']);
$response = $this->registryApiRequest('refresh',$apiParams);
</code></pre>
Revise an existing registration…
<pre><code>$response = $this->registryApiRequest('revise',$apiParams);
</code></pre>
API Response
The API response is a standard object. status->code is an http status, 200 indicating success.
<pre><code>status ->
(
 code -> 200, // HTTP status code
 message -> '(action) ok' // (action) = 'create', 'activate', 'deactivate', 'verify', 'revise'
),
registration ->
(
 registry_key -> string // UUID,
 registry_status -> string, // 'pending', 'trial', 'active', 'inactive', 'expired', 'terminated', 'invalid'
 registry_effective -> string, // DD-MMM-YYYY effective date
 registry_expires -> string, // DD-MMM-YYYY expiration date
 registry_name -> string,
 registry_email -> string,
 registry_company -> string,
 registry_address -> string,
 registry_phone -> string,
 registry_product -> string,
 registry_title -> string,
 registry_description -> string,
 registry_version -> string,
 registry_license -> string,
 registry_count -> int,
 registry_variations -> array,
 registry_options -> array,
 registry_domains -> array,
 registry_sites -> array,
 registry_transid -> string,
 registry_timezone -> string,
 registry_locale -> string,
 registry_valid -> bool,
),
registrar ->
(
 contact -> object(
 name -> string // Registrar Name
 email -> string // Registrar Support Email
 phone -> string // Registrar Telephone
 web -> string // Registrar Web Address
 ),
 timezone -> string, // standard timezone string
 locale -> string, // WordPress locale
 cacheTime -> int, // in seconds, time to cache the registration response (Default Cache Time)
 refreshInterval -> int, // in seconds, time before refreshing the registration (Default Refresh Time)
 refreshSchedule -> string, // 'hourly', 'twicedaily', 'daily', 'twiceweekly', 'weekly', 'twicemonthly', 'monthly' - corresponding to refreshInterval
 options -> array( // from settings page, registrar_options (Allow API to...)
 'allow_set_key',
 'allow_set_status',
 'allow_set_effective',
 'allow_set_expiration',
 'allow_activation_update'
 ),
 licenseCodes -> object( // may be changed by filter on registration server
 L1 -> 'Lite'
 L2 -> 'Basic'
 L3 -> 'Standard'
 L4 -> 'Professional'
 L5 -> 'Enterprise'
 LD -> 'Developer'
 LU -> 'Unlimited'
 ),
 notices -> object(
 info -> string, // information message text
 warning -> string, // warning message text
 error -> string, // error message text
 success -> string, // success message text
 ),
 message -> string, // html message
),
registryHtml -> string, // html (table) of human-readable registration values
supplemental -> mixed, // supplemental data/html assigned via filters (developer's discretion).
</code></pre>
On a successful response (status->code = 200), the SDK will automatically cache the registration data and schedule the next refresh event (you do not have to do this).
notices may be set (according to severity) to indicate an expiration or pending expiration and should be displayed to the user. Typically, only one notice will be set but they can be set via the <code>eacSoftwareRegistry_api_registration_notices</code> filter.
message is set via the <code>eacSoftwareRegistry_api_registration_message</code> filter.
supplemental is set via the <code>eacSoftwareRegistry_api_registration_supplemental</code> filter.
On an error response, an additional element is included:
<pre><code>error ->
(
 code -> 'error_code',
 message -> 'error message'
),
</code></pre>
error->message may be more informative than status->message. 
Errors may be handled with something like:
<pre><code>if ($this->is_api_error($response))
{
 echo "<div class='notice notice-error'><h4>Error ".$response->error->code." : ".$response->error->message."</h4></div>";
}
</code></pre>
<h4>Methods, Hooks, and Callbacks</h4>
Useful methods built into the SDK…
<pre><code>$this->isValidRegistration();
 // Returns boolean
 if ( $this->isValidRegistration() ) {...}

$this->getRegistrationKey();
 // Returns the current registration key
 $registrationKey = $this->getRegistrationKey();

$this->getCurrentRegistration();
 // Returns the current registration object (above response object)
 $currentRegistration = $this->getCurrentRegistration();

$this->isRegistryValue($keyName);
 // Returns the value of a specific registry key
 $regStatus = $this->isRegistryValue( 'status ');

$this->isRegistryValue($keyName, $value, $test);
 // Returns boolean comparison of the value of a registry key ($test is '=|eq' (default), '<|lt', '>|gt', '<=|le', '>=|ge')
 if ( $this->isRegistryValue('license', 'L3', '>=') ) {...}
</code></pre>
Several hooks are available to customize or react to registration events. 
In WordPresss, there are several actions and filters, for file based projects there are corresponding callback methods…
<pre><code> filter/callback: (your_productid)_api_remote_request( $request, $endpoint )
 @param array $request ['method'=>, 'timeout'=>, 'redirection'=>, 'sslverify'=>, 'headers'=>, 'body'=>]
 @param string $endpoint create, activate, deactivate, verify, refresh, revise
 @return array request body

 action/callback: (your_productid)_api_remote_response( $body, $request, $endpoint )
 @param array $body response body
 @param array $request ['method'=>, 'timeout'=>, 'redirection'=>, 'sslverify'=>, 'headers'=>, 'body'=>]
 @param string $endpoint create, activate, deactivate, verify, refresh, revise

 action/callback: (your_productid)_api_remote_$endpoint( $body, $request, $endpoint )
 @param array $body response body
 @param array $request ['method'=>, 'timeout'=>, 'redirection'=>, 'sslverify'=>, 'headers'=>, 'body'=>]
 @param string $endpoint create, activate, deactivate, verify, refresh, revise

 action/callback: (your_productid)_api_remote_error( $error, $request, $endpoint )
 @param object $error {status:{}, error: {}}
 @param array $request ['method'=>, 'timeout'=>, 'redirection'=>, 'sslverify'=>, 'headers'=>, 'body'=>]
 @param string $endpoint create, activate, deactivate, verify, refresh, revise

 action/callback: (your_productid)_update_registration($registration)
 @param array $registration registration object

 action/callback: (your_productid)_purge_registration()
</code></pre>
<h4>What You Need To Do</h4>
For WordPress Projects
In your class constructor/initialization, add an action to fulfill the registration refresh scheduled by the <code>scheduleRegistryRefresh()</code> method in <code>(your_productid).wordpress.trait.php</code>
<pre><code>\add_action( '(your_productid)_registry_refresh', array($this, 'refreshRegistration') );
</code></pre>
You can add this and other hooks with:
<pre><code>$this->addSoftwareRegistryHooks();
</code></pre>
The <code>addSoftwareRegistryHooks()</code> method adds:
<pre><code>\add_action( '(your_productid)_registry_refresh', array($this, 'refreshRegistration') );
\add_filter( '(your_productid)_is_registered', array($this, 'isValidRegistration') );
\add_filter( '(your_productid)_registration_key', array($this, 'getRegistrationKey') );
\add_filter( '(your_productid)_registration', array($this, 'getCurrentRegistration') );
\add_filter( '(your_productid)_registry_value', array($this, 'isRegistryValue'), 10, 4 );
</code></pre>
Example:
<pre><code>include "(your_productid)_registration/(your_productid)_registration.includes.php";

class <your_classname> implements \(your_namespace)\Interfaces\(your_productid)_registration
{
 use \(your_namespace)\Traits\(your_productid)_registration_wordpress;
 ...
 public function __construct()
 {
 $this->addSoftwareRegistryHooks();
 }
}
</code></pre>
Note:
If your primary plugin file name is not the same as the product id, edit your <code>(your_productid).interface.tpl</code> file and change the <code>SOFTWARE_REGISTRY_FILENAME</code> constant.
<pre><code> const SOFTWARE_REGISTRY_FILENAME = 'myPluginName';
</code></pre>
For Other File Based Projects
The <code>scheduleRegistryRefresh()</code> method in <code>(your_productid)_registration.filebased.trait.php</code> is called to schedule the next registration refresh. This method can be modified to schedule a cron event to execute the refresh at a future time. The scheduled event may run <code>(your_productid)_registration.refresh.php <registrationKeyValue></code> from the command line to refresh the registration.
When left as is, the <code>checkRegistryRefreshEvent()</code> method uses the key file to check for a needed registration refresh.
In your class constructor or destructor add:
<pre><code>$this->checkRegistryRefreshEvent();
</code></pre>
to trigger the refresh check.
Example:
<pre><code>include "(your_productid)_registration/(your_productid)_registration.includes.php";

class <your_classname> implements \(your_namespace)\Interfaces\(your_productid)_registration
{
 use \(your_namespace)\Traits\(your_productid)_registration_filebased;
 ...
 public function __destruct()
 {
 /* if necessary, set HOME/USERPROFILE and/or TMP/TMPDIR/TEMP directories */
 // putenv('HOME={your home directory}'); // where the registration key is stored, otherwise use $_SERVER['DOCUMENT_ROOT']
 // putenv('TMP={your temp directory}'); // where the registration data is stored, otherwise use sys_get_temp_dir()
 $this->checkRegistryRefreshEvent();
 }
}
</code></pre>
<h4>User Interface</h4>
Of course, the user interface is up to you, the developer, but you may look at (and maybe use) the registration UI trait included with {eac}Doojigger and used by {eac}SoftwareRegistry as an example.
see:
<ul>
<li>…/Traits/swRegistrationUI.trait.php in the eacDoojigger folder.</li>
<li>…/Extensions/class.eacSoftwareRegistry_registration.extension.php in the eacSoftwareRegistry folder.</li>
</ul>
<h4>See Also</h4>
<ul>
<li>
<a href="https://swregistry.earthasylum.com/software-registration-server/" rel="nofollow ugc">{eac}SoftwareRegistry – Software Registration Server</a>
</li>
<li>
<a href="https://swregistry.earthasylum.com/software-registry-hooks/" rel="nofollow ugc">{eac}SoftwareRegistry Custom Hooks</a>
</li>
</ul>
<h3>Copyright</h3>
<h4>Copyright © 2019-2025, EarthAsylum Consulting, distributed under the terms of the GNU GPL.</h4>
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should receive a copy of the GNU General Public License along with this program. If not, see <a href="https://www.gnu.org/licenses/" rel="nofollow ugc">https://www.gnu.org/licenses/</a>.

{eac}SoftwareRegistry Distribution SDK

{eac}SoftwareRegistry Distribution SDK for the Software Registration Server - Implementing the Software Registry SDK Package.

DMSI DDLS – Digital Downloads, Licensing & Subscriptions vs {eac}SoftwareRegistry Distribution SDK