Backup and restore

PhonePe for WHMCS has no built-in backup system (no automatic snapshots or one-click restore). Protect your installation using standard WHMCS backup procedures:

• Database backup: Preserves gateway configuration, invoices, and transaction logs.
• File backup: Saves existing module files before applying updates.

Back up before every update

Always back up before performing a manual update:

• WHMCS database backup: Stores gateway configuration (Client ID, webhook credentials, payment mode, License Key), invoices, and transactions. Use WHMCS automated backups (Configuration → System Settings → General → Other) or host tools (mysqldump, cPanel, Plesk).
• Gateway files to preserve:
  • modules/gateways/phonepe.php
  • modules/gateways/phonepe/ (entire directory)
  • modules/gateways/callback/phonepe.php

Keep a copy off the server

Store at least one recent backup somewhere other than the WHMCS server itself, so a server problem never takes your backups with it.

Where backups are stored

• Database backups: Stored in your configured WHMCS or server backup directory.
• File copies: Save in a dated directory outside the web root or download to secure local storage.
• Offsite redundancy: Always maintain at least one backup copy off the server.

Rolling back

To roll back after an update issue:

1. Restore module files: Copy preserved files back into modules/gateways/, overwriting updated files.
2. Restore database: Restore your WHMCS database backup if the update involved schema changes.
3. Verify gateway: Open Setup → Payment Gateways → PhonePe, confirm settings, click Save Changes, and run a test payment.

Related pages

• Updating — the manual update flow that this protects
• Uninstalling — removing the gateway entirely
• Troubleshooting — when a payment or webhook fails