Backup and restore

Zoho Payments has no built-in backup system — no automatic pre-update snapshots or one-click restore. Protect the module using standard WHMCS backup procedures: back up the database and save file copies before updating.

Back up before every update

Because a manual update overwrites files directly, create backups first:

• WHMCS database: Stores credentials, Data Center, Webhook Secret, License Key, invoices, and logs.
• Gateway files:
  • modules/gateways/zohopayments.php
  • modules/gateways/zohopayments/ (entire folder, including webhook handler)

Keep off-server copies

Use scheduled database backups for daily safety. Save a manual file and database snapshot off-server immediately before running module updates.

Where backups are stored

The gateway does not create local backup folders:

• Database backups: Stored in your host panel or remote backup destination.
• File backups: Saved to your secure off-server storage.
• Best practice: Keep at least one verified copy off the primary server.

Rolling back

To return to a previous working state after a bad update or a settings change:

1. Restore module files: Delete existing gateway files and copy saved zohopayments.php and zohopayments/ to modules/gateways/.
2. Restore database: Restore the WHMCS database backup only if gateway configuration or transaction tables were corrupted.
3. Verify configuration: Open Setup → Payment Gateways → Zoho Payments, verify settings, and run a test transaction in Test Mode.

Restoring files alone restores full functionality because credentials and license keys persist in the WHMCS database.

Related pages

• Updating — always back up first
• Uninstalling — removing the gateway cleanly
• Troubleshooting — fixes before you roll back