Prepare before the product download
In your verified Orbit account, choose the correct organisation and obtain the installation preparation kit from Product downloads. It contains the licence SDK and helper without EmailaBiller application code. This allows you to prepare the intended host before the product ZIP is available for an active installation.
Use PHP 8.4 CLI with cURL, JSON, POSIX and sodium, running as the same Unix user that will run web PHP. Compare the kit's SHA-256 with Product downloads, then extract it into a private working directory. Open the extracted emaila-orbit-installation-kit/ directory. Terminal access or your host's assistance is required for this first step.
From that kit directory, replace EXACT_RELEASE_VERSION, the example domain and the absolute private-directory placeholder with your selected entitled release and host settings:
php prepare-installation.php prepare hoster EXACT_RELEASE_VERSION billing.example.com /ABSOLUTE/PRIVATE/biller-licence
hoster is the retained machine code used by EmailaBiller's licence integration. Use a new absolute directory outside the application and every public web root. Its parent must already exist; the kit creates the final directory with private permissions. Keep private keys on the host and copy only the displayed public key and canonical domain into Orbit.
Approve and activate the same identity
Open My licences for the same organisation. Select the genuine EmailaBiller entitlement for the exact release, choose Activate an installation and provide that prepared public key and domain. For paid rights, the invoice must actually be fulfilled; an updates-only purchase does not substitute for a base product licence.
Copy the complete ORBITSETUP1 setup code from its activation receipt. From the preparation-kit directory on the intended host:
php prepare-installation.php activate /ABSOLUTE/PRIVATE/biller-licence
php prepare-installation.php status /ABSOLUTE/PRIVATE/biller-licence
Use the same actual directory. Activation reads the setup code from standard input; follow the kit's private input instructions and keep it out of command arguments, URLs and shared logs. Status verifies the real authority permission online.
After activation succeeds, return to Product downloads, select that active installation and download the bound EmailaBiller release ZIP. Compare its SHA-256 with Product downloads before extracting it.
Reuse it during application setup
Configure ORBIT_LICENSE_CONFIG for web PHP and scheduled commands to point to the prepared directory's config.json. A terminal-only environment setting does not configure the web PHP process. Keep the same Unix ownership; ask your host to configure both contexts if needed.
Complete fresh application setup without generating another installation key. Sign in at /admin/master/login, enrol MFA through /admin/master/security and check System → EmailaBiller licence. Those default paths follow a customised ADMIN_PATH.
If the product cannot find the existing identity, inspect the configured path, web/CLI environment and private-directory access before using a new-key preparation action. Preserve the prepared directory with the database, .env and APP_KEY. Existing installations should retain their original identity and use the matching licence-recovery procedure.
Understand restrictions
Capacity counts primary billing client accounts across brands, including suspended/imported accounts; delegated customer team members are separate. The signed permission determines the actual allowance and update rights. During a temporary authority outage, only the remaining signed validity is usable. Expired or denied permission restricts licensed management and signs administrators out; it does not delete customer services or turn existing invoice payments into licence purchases.