Uninstall
If you want to remove Billing Booster from your installation entirely, follow these steps in order.
Deactivating keeps Billing Booster's database tables, so a later reactivation picks up where you left off. Removing them is a deliberate choice, made on Settings → Advanced (see the step below). If you do, export your configurations first under Settings → Advanced → Backup & Restore — payment codes, e-invoicing and statement processing configs are all in the file. There is no undo.
1. Switch the invoice template back
If you switched to one of the billboost-* child themes, change it before removing the files, or WHMCS will be left pointing at a template that no longer exists.
Go to Setup → General Settings → General and set the Template back to the parent theme (Six, Twenty-One or Nexus), then save.
On Lagom 2, set Addons → RS Themes → Pages → Invoice PDF back to its stock option. If you hand-edited your own invoicepdf.tpl, restore the backup.
If you use BestPDF instead, there is nothing to change here — remove the Payment Code component from your design when convenient. It renders nothing once Billing Booster is gone.
2. Remove the email tag
Edit your invoice email templates under Setup → Email Templates → Invoice and remove any {$paycode} tags you added. Left in place they are harmless, but will render as empty.
3. Deactivate the Payment Code gateway
If you installed it, go to Setup → Payments → Payment Gateways, find Payment Code, and deactivate it. Make sure no client is mid-checkout on it first.
Note that WHMCS keeps the transactions already booked against it — your payment history is not affected by removing the gateway.
4. Decide whether to keep your data
In the Billing Booster interface, open Settings → Advanced. In the Danger Zone, leave Remove all data when the addon is deactivated off to keep everything for a later reactivation, or switch it on and click Save Changes to have deactivating drop Billing Booster's tables as well. See Configuration → Danger Zone.
If you scheduled crons/billboost.php in the system cron, remove that entry now.
5. Deactivate the addon
On Setup → Addon Modules, click Deactivate on the Billing Booster row.
With the switch from step 4 on, this drops Billing Booster's database tables — all payment code, e-invoicing, and processing configurations are removed, along with bank connections, EBICS keys, its log and its review queue. With it off, the tables stay, and WHMCS confirms that the data has been kept. Either way, its cron work stops.
Existing PDF invoices that were already generated are unaffected; new invoices simply stop receiving payment codes and e-invoices.
6. Remove the files
Delete these from the filesystem:
/crons/billboost.php
/modules/addons/billboost
/modules/gateways/paycode
/modules/gateways/paycode.php
/templates/billboost-six
/templates/billboost-twenty-one
/templates/billboost-nexus
If you used the Lagom 2 route, also remove the BillBoost page-option folder under /templates/lagom2/core/pages/invoicepdf/.
7. (Optional) Clean up the data directory
The Billing Booster data storage directory (whatever path you configured under Configuration → Data Storage) holds archived payment codes and downloaded bank statement files. These files are not removed automatically.
If you don't plan to reinstall, delete that directory too for a clean state — bearing in mind it may contain bank statement files you want to retain for your records.
Reinstalling later
If you kept your data, re-uploading the files and activating the addon brings back every configuration and setting, license key included; redo the wiring steps from Installation that you undid above.
If you removed it, you start with empty configuration lists. Import a settings file exported under Settings → Advanced, or re-add your payment codes, e-invoicing rules, and processing configurations as described in Configuration, and redo the wiring steps from Installation — the invoice template routing and the email tag in particular. If you kept the data storage directory and point the new install at the same path, your archived files remain available.