Skip to main content
OwnPay provides a one-click update system that keeps your instance current with the latest features, security patches, and bug fixes.

Check for updates

Navigate to System > System Update. The page shows your current version and whether a newer release is available. If an update is found, the new version number and a summary of changes are displayed.
You can also check the OwnPay GitHub releases page for the full changelog.

Update process

1
Click Check for Updates to query the update server.
2
If an update is available, review the changelog and click Update Now.
3
OwnPay automatically creates a full backup of your current installation (files and database) before applying the update.
4
The update downloads and extracts the new version, runs database migrations, and clears caches.
5
You are redirected to the login page once the update completes.

Post-update steps

After every update, perform these checks:
  1. Log in and verify the dashboard loads correctly
  2. Check the Environment Info panel in Settings to confirm the new version
  3. Test a checkout on at least one brand to ensure payment flows work
  4. Review plugin compatibility - some plugins may need updates after a major OwnPay release
OwnPay automatically clears the Redis cache after an update. If you see stale data, manually refresh the page.

Rollback procedure

If something goes wrong after an update, you can roll back to the previous version:
1
Navigate to System > System Update.
2
If a rollback is available, click Rollback to v0.2.0.
3
OwnPay restores the backup created before the update.
4
Verify the rollback by checking the version in Settings > Environment Info.
Rollback restores files and database to the pre-update state. Any transactions processed between the update and the rollback are preserved in the database - they are not reverted.

Update via CLI

For advanced users or automated deployment pipelines, you can update OwnPay from the command line:
This command performs the same backup-and-update flow as the web UI. Use --no-backup to skip the automatic backup if you have your own backup strategy.
For migration guidance between major versions, see the Migration Guide.
Last modified on August 25, 2026