Company
Industry
Use Case
Favorite Feature
Website:
https://wordpress.org/plugins/digipass/The idea for DigiPass came from a prospective NetLicensing customer. They ran a WordPress site with written content and wanted readers to pay for access to some of it.
They had tried to build this from several plugins: one for payments, one for user roles, and some manual work in between. Every payment had to be matched to a user and the right role switched on, and switched off again when the subscription ended. It took several people to keep track of payments and subscribers, and it was easy to get wrong.
We built DigiPass to do this inside WordPress, with NetLicensing handling subscriptions and payments. Site owners don’t need to write code.
The site owner sets up a product with a Subscription module in NetLicensing, with subscription periods and prices as license templates, say one month and one year. In WordPress, they enter their NetLicensing credentials in the DigiPass settings and connect a post or page to that product module.
In the post, everything after the <!--digipass--> marker (or after the standard <!--more--> tag) is protected. When a reader opens the post:
ttl from the response, so the next page view doesn’t call NetLicensing again.successURL and cancelURL, and shows a “subscription options” link instead of the protected part.The reader pays in the NetLicensing Shop and returns to the same post, now unlocked. When the subscription runs out, the next validation returns valid=false and the paywall comes back by itself. Nobody has to change a role. Site administrators always see the full content.
If NetLicensing can’t be reached, readers see a short notice, and the site administrator gets an email.
Payments, subscription periods and access come from one source. The site owner’s team no longer matches payments to users or switches roles on and off. Readers buy and renew in the Shop on their own, and access follows the subscription automatically.
The DigiPass source code is on GitHub. The plugin’s last release (0.4.0) dates from 2016 and stores the vendor’s account credentials in WordPress. Today we’d use an API key with the role ROLE_APIKEY_LICENSEE for the reader-facing validation and shop links (see API security).
Want to sell content or software from WordPress? Create a free NetLicensing account and start with the Subscription model.

B2B SaaS: From Stripe-Only to Licensing-as-a-Service
How a B2B SaaS vendor can keep Stripe Billing for payments and use NetLicensing as the single source of truth for subscriptions, trials and add-on features.
Wordpress Plugin: Credit Tracker
How Labs64 uses NetLicensing in its free Credit Tracker WordPress plugin to see which sites use the plugin, with licensee auto-create and a single validation call.