Paymenter Security and Update Checklist for Hosting Stores

A Paymenter update can affect checkout, invoices, provisioning and installed extensions. Treat it as a store deployment: check the release, protect the database, update in a maintenance window and run a real end-to-end test afterward. This checklist follows the official Paymenter update guide; read that page for the version you actually run.

Before updating

1. Read the current Paymenter release notes and check whether your theme and extensions support the target version.
2. Back up the database, .env, uploaded files and extension source. Verify that a restore is possible.
3. List payment gateways, webhooks, queues and provisioning modules so you can test each one afterward.
4. Choose a maintenance window and tell customers if checkout may be briefly unavailable.

Choose an update path

Paymenter documents both an app:upgrade command and manual update steps. The manual path puts the application in maintenance mode, downloads the release, updates extensions, runs migrations, clears caches, restores file ownership and brings the site back up. Docker deployments have different steps, including rebuilding or switching the theme after an update. Follow the path for your own installation rather than mixing commands from both.

Verify the storefront

Check customer login, product pages, a test checkout, invoice creation, webhook processing and delivery or provisioning. Review the application and queue logs for new errors. If a theme or extension fails, compare its supported version with the installed Paymenter release before changing core files.

For a wider security review, restrict admin access, rotate credentials after suspected exposure, enable available account protection and keep the operating system and PHP runtime patched through planned manual maintenance. Updating Paymenter alone does not patch its host. If you sell recurring services, also test billing agreements and automatic charges after a release.

On BuiltByOtte Cloud, Paymenter updates are installed with one click and rolled back automatically if they fail.