Remove WP Charitable from Stripe

  • Resolved scammedbycharitable

    (@scammedbycharitable)


    5 days, 3 hours ago

    I mistakenly set up stripe through WP charitable (ginormous mistake) and now I can’t get rid of it, despite the fact that I don’t use it, it has primary power over my stripe account and I don’t have permission to revoke it. If I have to create a new stripe account and go through all that hassle, I will, but in the meantime is there a way to get rid of charitable without destroying the entire account?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author David Bisset

    (@dimensionmedia)

    5 days, 2 hours ago

    Hello! Sorry for the frustration, happy to help you get this sorted.

    Charitable uses Stripe Connect, the same standard OAuth integration used by Shopify, Substack, and most donation/commerce platforms. The connection only allows Charitable to create charges on your behalf… that permission is what lets donors enter their card on your donation forms and have the money flow straight into your Stripe account automatically. It does not give us access to your funds, bank details, or account settings, and you can revoke it at any time from either side.

    Two ways to disconnect:

    1. From WordPress (if Charitable is still installed): In Charitable’s Stripe settings, click “Disconnect this account.”
    2. From Stripe directly (works even if the plugin has been removed) – the UI may look slightly different, but in your Stripe Dashboard, go to Settings, find Installed apps (or Connected accounts), locate Charitable, and click Revoke access. That’s it.

    Happy to help answer further questions or with additional info (like a url) we can even confirm the disconnection.

    Plugin Author David Bisset

    (@dimensionmedia)

    1 day, 10 hours ago

    We are going to go ahead and close this thread for now. But if you’d like us to assist further, please feel welcome to continue the conversation.

    Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.