Prepare the host
Follow the PHP, database and web-root requirements. Use a new empty database and dedicated user. The eventual application directory must stay outside the web document root; serve only multibrandaccounts/public/ through HTTPS.
Before obtaining the product ZIP, complete installation preparation and genuine activation. Select that active installation in your organisation's Product downloads, then extract the verified complete release. Configure web PHP's ORBIT_LICENSE_CONFIG to reuse the preparation directory's config.json before opening Accounts; do not generate another key during setup.
Unlock browser setup
- Open your HTTPS workspace at its origin root.
- In hosting File Manager, read the private
storage/setup/setup-key.txtinside the application directory. - Paste its one-hour key into the setup form. Do not place it in a URL or share it.
The first visit generates the setup key automatically. After the separate licence-preparation step, administrator/database setup uses the browser. Reload the setup page to renew an expired key. The unlocked browser has a twenty-minute window. Successful setup removes the temporary key and permanently locks the installer.
Create your administrator and first business
Choose the System Administrator's name, email and password and review the canonical HTTPS URL. Use a 12–72 byte password with letters and a number or symbol. No default administrator password is supplied.
Enter the first business's name, code and supported base currency, then confirm fresh setup. The installer creates independent encryption keys and the product schema. Billing remains disabled until the business's issuer information and numbering have been reviewed.
Continue to Product licence, confirm the chosen administrator credentials and check the already activated identity. If it asks for a new installation key, first correct the web PHP environment path and private-directory ownership. Retain the prepared key.
Optional terminal tools
From the private application root, as the PHP user:
php bin/install.php --check
php bin/install.php --enable-web
The second command is an optional way to prepare a one-hour browser key. Advanced CLI input is documented in the release guide; passwords belong in private input files rather than command arguments.
Finish deliberately
Review issuer details and numbering before enabling billing. Add separate financial users and assign their businesses. Configure SMTP and payment connections with your own credentials.
Back up config/accounts.php, private storage/, the external licence directory and database together. Never delete pending keys or setup state to force installation into an existing database. Follow the exact release's interrupted-setup instructions so original independent encryption keys are retained.