Main-product ownership
In the integrated licensed release, open System → Addons for the premium EmailaBiller library. The newer upstream menu groups extensions under Modules & addons; that menu alone does not prove the installed release includes the Orbit premium integration. Free extensions remain in Modules & addons. A premium purchase attaches to an existing matching EmailaBiller main licence in Orbit Area, with one-time or monthly terms as actually published. No separate addon activation key or extra domain allowance is issued.
Choose the intended main licence before ordering. An unpaid invoice is not installation permission. Copying a package purchased for licence B to licence A does not transfer its entitlement.
Download and install
With active main and addon rights, obtain the published signed package for that installation, check its release identity and use Modules & addons → Verify → Review → Install disabled → Backup acknowledgement → Enable. Premium addons require the compatible licensed core (1.3.8 or later with the actual enforcement integration), matching publisher pin and signed orbit_addon identity.
The product verifies all declared files and current online permission before stage/commit/migrations and before action listing, execution or event handling. Changed files, wrong publisher/addon, disabled extension, inactive purchase or invalid main permission block execution. There is no permanent positive unsigned addon-right cache. A required authority outage holds premium actions until rights can be checked.
Renewal and approved transfer
Monthly addons need a current paid term. One-time rights retain their published limits, refund/revocation and main-licence dependency. Addon renewal does not renew the base product. An approved main-licence domain transfer retains the purchase on that same licence; complete its normal installation transfer/activation and use the new approved identity. Cloning keys does not approve another installation.
Limits
Premium purchase enforcement initially applies to the addon category. Themes and provider modules need separately accepted runtime enforcement before being sold through this premium API. Do not claim every source module is a published premium offer. Product-licence restrictions protect management without deleting customer business data, and readable customer-controlled PHP cannot be promised impossible to alter.