Service integrations

Install, update and revoke signed modules

Review publisher identity, package inventory, disabled installation and connection retesting.

Platform
Laravel / PHP
Laravel
13
PHP
8.4
Database
Dedicated MySQL-compatible production database

Review the publisher

Open System → Modules & addons with modules.manage. Executable PHP/Blade modules are privileged code, not a sandbox. Verify their source, release compatibility and independent publisher fingerprint before installation. A public key included in the same ZIP is not independent assurance.

For permitted free-module publishers, the protected Publisher keys action imports an Ed25519 public key and full independently verified SHA-256 fingerprint. Never import a private key. Orbit premium addons use their independently pinned publisher and current main-licence rights; editable free-publisher records cannot replace that pin.

Install and enable

Upload the signed ZIP and independently checked checksum, choose Verify, review its exact name/category/version/publisher/inventory and acknowledge installation. It installs disabled. Take/verify a current backup and explicitly enable. Declared migrations may run; a failed later bootstrap does not automatically undo a schema migration.

Integration packages then need a separate connection/account, private configuration, successful Test and explicit Enable. Saving or upgrading invalidates previous test evidence. A source starter, GitHub source ZIP or loose package.json is not the signed installable package.

Upgrade or disable

Use the installer's supported newer-version flow after disabling the old version and reviewing compatibility/dependencies. Versions use separate directories and must not overwrite core files. Retest affected connections. Disable obsolete modules without deleting financial/provider history. Removal is guarded by dependencies and usage; it is not a destructive uninstall/data rollback tool.

Revoke a publisher

The protected revoke action disables affected modules and provider connections while preserving stored data. Restoring trust does not silently re-enable or retest them. If integrity fails, preserve evidence and restore the verified exact package rather than editing its manifest. See premium addons for their additional purchase-bound execution checks.

← All EmailaBiller guidesGet help →

Need help with EmailaBiller?

Tell us the product version and what you are trying to do. Keep passwords and private keys out of your message.

Contact Emaila