Future Investments
LICENSE HUB DOCUMENTATION

Build, sell and support software from one place.

This guide covers the complete store-owner workflow and the experience your customers receive.

01

Requirements

Install License Hub on a secure WordPress website running PHP 7.4 or later. Use HTTPS, working outgoing web requests and a server with enough private storage for your release ZIP files. Configure a reliable WordPress email sender before accepting live orders.

  • WordPress administrator access
  • HTTPS certificate and permanent domain
  • PayPal Business account for live checkout
  • Regular database and file backups
02

First-time setup

After activation, open License Hub → Setup. Activate the License Hub product licence to receive updates, select English or another available language, and choose Install Demo Store or Start Empty. The demo option installs the storefront theme, pages, menu and this example product.

Keep PayPal in Sandbox while testing. Review every legal page and replace all demonstration wording before launch.

03

Products and licence plans

Open License Hub → Products to create each plugin or theme. Add a unique product slug, customer-facing description, currency, billing period and prices. Starter, Business and Agency plans support 1, 5 and 25 site activations; plan limits can be adapted in white-label settings.

The product slug connects purchases, licence validation and releases. Do not change it after customers begin using the product.

04

Checkout and PayPal

Enter PayPal Sandbox credentials first and complete a full test purchase. A confirmed payment creates the order, issues the correct licence and makes the protected download available to the buyer. Switch to Live only after return URLs, notification handling, emails and refund procedures have been verified.

Never mark an order as paid from a browser return alone; License Hub verifies the payment with PayPal before fulfilment.

05

Releases and automatic updates

Upload a clean installation ZIP from License Hub → Updates. Set its semantic version, minimum WordPress and PHP versions, tested WordPress version and release notes. The file remains outside the public media library and is delivered through an authorised request.

Customer plugins call the License Hub API with their product slug, installed version, domain identity and licence. Eligible sites see the release in the standard WordPress Updates screen.

06

Customer portal

Customers open My Account, request a one-time sign-in code by email and view licences, site activations, orders and protected downloads. They do not need a WordPress administrator account on the store website.

Before launch, test code delivery, expired codes, licence recovery, logout and downloads in a private browser window.

07

Branding, footer and language

Use License Hub → Setup → White-label settings to upload the main logo, dark-background logo and favicon. Set the business name, store tagline, primary colour, email identity, footer copy, legal links and social profiles. English is the default language; Bulgarian, German, French and Spanish can be selected and extended.

Changes apply to the public storefront, checkout and customer area. Existing custom logos are preserved during plugin updates.

08

Security and maintenance

  • Keep WordPress, License Hub and the server runtime updated.
  • Restrict administrator accounts and enable two-factor authentication.
  • Keep licence keys, PayPal secrets and release archives out of public logs.
  • Back up the database and private release directory before major updates.
  • Test a release on staging before publishing it to customers.
09

Troubleshooting

If activation or updates fail, check that the licence is active, the product slug matches, the domain is correct and the customer server allows outbound HTTPS requests. If checkout fails, confirm Sandbox/Live mode, PayPal credentials and the exact return URL. If email codes do not arrive, inspect the WordPress mail provider and spam folder.

When requesting support, include the License Hub version, WordPress and PHP versions, order number, affected product slug and the exact error message. Never send full licence keys or payment secrets.