Update, disable or move the module

Updating, disabling and moving the module all leave your invoices, saved cards, payment history and Whop connection in place.

Update the module

Back up your WHMCS files, database and encryption configuration, as you normally would before any update.
Replace the module files with the new version, using the file list from Install the module. Include both payment template files, whop-payment.tpl and whop-complete.tpl, in every active system theme.
Open System Settings > Payment Gateways > Whop Payments (older WHMCS versions call this menu Setup) and click Save Changes. This runs the module's own local setup for the new version and makes no request to Whop itself.
Click Check connection on each environment you have configured, Sandbox and Live.
Confirm the environment you intend to use is still selected.

Local setup preserves your display names, activation, visibility, connections and any records already waiting to process. Afterward, place a test order or open an existing invoice to confirm checkout still works.

Hide a payment choice

Turn off Show on Order Form on a gateway to stop offering it on new orders. This does not change anything about invoices already using it, or cards customers already saved with Whop.

If you want to remove a payment choice entirely in Apps & Integrations, deactivating Whop Checkout on its own is safe: it shares Whop Payments' connection but does not own it. Whop Payments is the gateway that holds the actual connection to Whop, so if you plan to deactivate it too, follow Stop using Whop below rather than doing it on its own.

Stop using Whop

Before you deactivate, check that no payment or refund is still in flight, that no dispute or Resolution Center case (a complaint a buyer opens directly in Whop) is open, and see which clients still have a saved Whop card. Then deactivate Whop Payments and Whop Checkout in Apps & Integrations.

Deactivating does not delete anything. What stays behind:

Every transaction Whop already collected, in Billing > Transactions, exactly as it is.
Any client Pay Methods (saved cards) created through Whop. They stay listed under each client's Payment Methods, but none of them can be charged anymore once the gateway is deactivated.
The module's own database tables: mod_whop_connections, mod_whop_pending_payments, mod_whop_partner_provisioning, mod_whop_webhook_inbox and mod_whop_dispute_notices. You can leave them in place. They take up little space and do nothing while the gateways are inactive.

Nothing needs to happen on the Whop side, and it is worth leaving the key in place. Refunding a past Whop payment from WHMCS, and recording a refund or a case that Whop reports later, both use the saved connection. Revoke the key only once you are sure you will never need either.

Move WHMCS to another server or domain

Copy your files and database the same way you normally migrate a WHMCS installation. Nothing about Whop needs special handling in the copy itself, as long as your encryption configuration moves with it.

After the move:

Set the new System URL in WHMCS to the new address.
Open Payment Gateways > Whop Payments and click Check connection for each environment you use.

Check connection repairs the webhook (the address Whop calls to tell WHMCS about a payment) so it uses your new System URL. It can then show a dated notice asking you to review payments and refunds from around the move, because Whop was still calling the old address until the repair. Review them, then dismiss the notice. Do not add a second webhook in Whop by hand. Your API keys keep working, and saved cards keep working, without any change on their side.