Skip to content

Uninstalling

RelyPay separates turning it off from deleting your data. Deactivating is a safe, reversible pause; fully removing your data is a separate, deliberate step. This page covers both, plus a lighter option if you only want to pause.

Deactivate (reversible)

To turn RelyPay off, go to Setup → Addon Modules, find RelyPay, and click Deactivate. WHMCS confirms with:

Deactivation message

"RelyPay deactivated. Sub-gateways removed. Database tables preserved."

Deactivation removes the generated files (the hook loader and the 10 sub-gateway checkout options), so the client-area and runtime feature stops. Your database tables are preserved on purpose — your transaction history, provider configuration and settings all survive — so deactivating and later reactivating is lossless: everything comes back exactly as you left it.

Remove all data (irreversible)

If you want RelyPay gone entirely — for example, when decommissioning a store — first deactivate it (above), then manually drop its database tables. RelyPay's tables are all named with the mod_relypay_* prefix, so drop every table matching mod_relypay_* using your database tool (such as phpMyAdmin).

This cannot be undone

Dropping the mod_relypay_* tables permanently deletes your RelyPay transaction history, provider configuration and license details. There is no undo. Take a full database backup first, and only do this if you are certain you no longer need any of it.

Temporarily disable instead

You usually do not need to uninstall to stop taking a particular payment. A few lighter options that leave your data intact:

  • Stop routing to a provider — disable a provider under Addons → RelyPay → Providers, and adjust your rules under Routing so payments go elsewhere.
  • Pause RelyPay entirely without losing data — simply deactivate under Setup → Addon Modules as above. Because your tables are preserved, reactivating later restores everything.

Coming back later?

If there is any chance you will use RelyPay again, deactivate rather than dropping the tables. Reactivation regenerates the sub-gateway files and picks up right where you left off.

Documentation for the Relyweb app catalogue.