Prepare an extension package for installation

A Paymenter extension can include database migrations and core integration steps as well as its main PHP class. Prepare the package before running its installer.

Inspect the downloaded release

Save the ZIP and note its version. Extract it into a working directory and locate README.md. Check whether the package is an Other, Server or Gateway extension; the destination depends on that type.

For the extensions sold in Development, read the product's tested Paymenter and PHP versions. Compatibility with one release is not a guarantee that every future release or custom theme needs no changes.

Gather the installation prerequisites

Confirm that you can back up the database and relevant application files. Check that the account running commands has the documented filesystem permissions and can run migrations. Identify the existing queue worker and scheduler before changing anything.

Do not paste hosting credentials into the package or a public support post. Keep secrets in the existing application configuration.

Review integration changes

If the package includes an integration patch, read which files and hooks it touches. Run the documented preview command first. A refusal caused by custom code should lead to a review, not replacement of the entire custom file with an older copy.

Keep the preview output and backup location privately with the deployment record.

Verify after installation

Check both the new feature and an ordinary checkout or invoice path. Test with a normal customer account as well as an administrator. Confirm that existing prices and issued invoices are retained.

See the Development catalog for product requirements and Combine Invoices installation checks for a concrete package checklist.