Uninstalling Split Pay & Your PRO Subscription
What happens to your PRO subscription, license, configuration, and transfer log if you deactivate or delete the plugin — and how to come back later without losing data.
Short version. Deactivating or deleting Split Pay does not cancel your PRO subscription. Billing happens through Freemius and is bound to your account email, not to a particular WordPress install. Your settings and transfer log persist through deactivation; deleting the plugin from Plugins → Installed Plugins does not drop the plugin’s database tables.
If I deactivate or delete the plugin, will I still be charged for my PRO subscription?#
Yes — the subscription is independent of plugin activation status. Freemius (the licensing platform Split Pay uses) bills you on a recurring schedule based on the plan you signed up for, regardless of whether the plugin is active on any of your sites.
If you want to stop the recurring charge, cancel the subscription itself in your Freemius user dashboard:
- Visit users.freemius.com and sign in with the email address you used to purchase.
- Open the Split Pay product entry, then your active subscription.
- Click Cancel. You retain access for the remainder of the paid period.
If I reinstall later, will my PRO license still work?#
Yes. As long as the subscription itself is still active (or you re-purchase one), you can reinstall Split Pay PRO and reactivate the license:
- Download the latest Premium ZIP from your Freemius account email or from users.freemius.com.
- Upload it under Plugins → Add New → Upload Plugin. Choose Replace current with uploaded if a free copy is installed.
- Activate the plugin and follow the “Activate License” prompt — the license auto-binds to your Freemius account.
See Activating PRO for the full step-by-step.
What data is preserved when I deactivate the plugin?#
Everything. Split Pay does not register a deactivation hook that wipes plugin data. Deactivating the plugin in Plugins → Installed Plugins simply stops it from running; on reactivation, every setting and every transfer log row is exactly where you left it.
Specifically, the following are not touched by deactivation:
- WordPress options (
spp_*,bsd_*) — including platform API keys, transfer percentages, vendor roles, and Delayed-Transfers toggle. - Database tables —
{prefix}_bsd_scsp_transfer_log(the transfer log),{prefix}_bsd_strp_accnt(synced connected accounts), and{prefix}_bsd_strp_connected_id(per-product connected-account routing). - Per-product post meta on individual products (vendor selection, percent/amount, shipping rules).
- Freemius license records (stored under separate
fs_*options).
What data is preserved when I delete the plugin?#
Same answer in practice: everything is preserved. Split Pay does not register an uninstall hook either — clicking Delete in WordPress removes the plugin files but leaves the database state intact. This is intentional so that customers who delete-then-reinstall (or migrate to a new WordPress install) can restore their configuration and transfer history.
If you want to wipe the data completely, you have to do it manually. See the Reset to defaults FAQ.
Can I move my Split Pay configuration to another WordPress site?#
Yes — this is one reason data is preserved on uninstall. The simplest paths:
- Standard WordPress migration tools (All-in-One WP Migration, Duplicator, Migrate Guru, etc.) carry all
spp_*/bsd_*options, the three plugin tables, and the per-product post meta over to the new install. - Database export/import works the same way — the data lives in standard WordPress option/post-meta storage plus the three SPP tables listed above.
After the migration, install Split Pay (free or PRO) on the new site and reactivate the license; the existing configuration loads automatically.
Do I need to clean up Stripe webhooks if I uninstall?#
No — since 3.8.1, Split Pay never creates webhook endpoints on your Stripe account, so there is nothing of Split Pay’s to clean up. The webhook endpoints you see in dashboard.stripe.com/webhooks belong to your Stripe gateway plugin (WooCommerce Stripe, Payment Plugins, or FluentCart) and should stay as long as that gateway runs on the site.
One historical exception: Split Pay versions before 3.8.1 added transfer.created, transfer.reversed, and transfer.updated events to your gateway’s endpoint via the old “Sync Webhooks” button. Those events are harmless and were never consumed by Split Pay — you can remove them from the endpoint (or leave them) whether or not you keep the plugin.