labs64

Easily control the use and monetize your WordPress plugins and themes using PluginPass – a WordPress License Manager backed by <a href="https://netlicensing.io" title="Software License Management" rel="nofollow ugc">Labs64 NetLicensing</a>.
The Plugin is designed to be easy-to-use, which you easily define as a dependency to your plugin or theme, so this takes care of the plugin’s & theme’s features activation and validation.
<h4>Features</h4>
<ul>
<li>Enable the subscription model for the plugin/theme</li>
<li>Sell PRO versions of your plugin/theme</li>
<li>Offer trial/evaluation version on the PRO features (with the fallback to the lite version)</li>
<li>Enable up-selling by offering additional plugin/theme features</li>
<li>Use plugin or theme on the given domain only</li>
<li>License as many plugins/themes as you want</li>
<li>Need more features? – <a href="https://github.com/Labs64/PluginPass/issues" rel="nofollow ugc">Let us know</a></li>
</ul>
<h4>Payment Gateways</h4>
Payment Gateways supported in the plugin:
<ul>
<li>PayPal</li>
<li>Stripe</li>
<li>MyCommerce</li>
<li>FastSpring</li>
<li>Braintree – PLANNED</li>
<li>Authorize.net – PLANNED</li>
<li>2Checkout – PLANNED</li>
<li>SOFORT Banking – PLANNED</li>
</ul>
<h4>Quickstart</h4>
Add this code-snippet to your plugin:
<pre><code>$quard = new \PluginPass\Inc\Common\PluginPass_Guard( $api_key, $product_number, $plugin_folder );
if ($quard->validate( $product_module_number )) {
 // do something
 $quard->open_shop();
}
</code></pre>
Detailed integration instructions, NetLicensing products configuration tips and troubleshooting can be found on plugin’s <a href="https://github.com/Labs64/PluginPass/wiki" rel="nofollow ugc">Wiki page</a>.
<h3>Privacy Policy & GDPR</h3>
This plugin integrating components of an external service – <a href="https://netlicensing.io" title="Software License Management" rel="nofollow ugc">Labs64 NetLicensing</a> (processor). Labs64 NetLicensing is an online license management service provider. License validation requests are processed using plugin or theme developer (controller) NetLicensing account.
By using this plugin validation requests will be sent to the Labs64 NetLicensing in order to verify valid use of the plugin or theme. Personal data may be transferred with these requests such as Unique Identifiers, Plugin and Theme Details, WordPress Instance Name, Domain Name, System Details of the data subject.
The European operating company of Labs64 NetLicensing is: 
Labs64 GmbH 
Radlkoferstr. 2 
81373 Munich, Germany 
Labs64 NetLicensing website: <a href="https://netlicensing.io" rel="nofollow ugc">NetLicensing.IO</a>
The applicable data protection provisions of Labs64 NetLicensing may be retrieved under Labs64 <a href="https://www.labs64.com/legal/privacy-policy/" rel="nofollow ugc">Privacy Policy</a>.
We strongly encourage you to comply with WordPress <a href="https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/" rel="nofollow ugc">Plugin Guidelines</a> and General Data Protection Regulation (GDPR) while developing your plugins and themes and interfacing with <a href="https://netlicensing.io" rel="nofollow ugc">Labs64 NetLicensing Services</a>.
For more details on Labs64 NetLicensing data protection provisions visit Labs64 <a href="https://www.labs64.de/confluence/x/vQEKAQ" rel="nofollow ugc">Privacy Center</a>.
<h4>Controller’s Responsibilities</h4>
The controller is the principal party for data collection responsibilities. These responsibilities include collecting individual’s consent, storing of the data, managing consent-revoking, enabling the right to access, etc.
If an individual revokes consent, the controller will be responsible for initiating this request. Therefore, on receipt of this request, it will be responsible to remove the revoked data through NetLicensing vendor account.

PluginPass – WordPress PRO Plugin/Theme Licensing (Public Alpha)

Very useful plugin helping WordPress plugin developers to monerize their works.

Very useful plugin

I was able to enable license management for my plugin with almost no effort. Time spent (all in): 30 min !! Great & Thank you!

Easy and painless integration

PluginPass is a WordPress license manager that makes it easy to monetize your WordPress plugins and themes.

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.

PluginPass – WordPress PRO Plugin/Theme Licensing (Public Alpha) vs {eac}SoftwareRegistry Distribution SDK