Disconnect Stripe without removing paid users
under review
JS
1) The problem → I would need to remove all paying members to a free membership in order to disconnect Stripe.
2) Why is this important → My users might churn if I have to get them to sign up again.
3) What's your plan B →
4) Possible solutions we could build for you → A way to disconnect my stripe without having to cancel my user's subscription
Naitik Mehta
under review
Update: This feature depends on the same functionality that's required for importing paid members — which is going to be 10x easier for us to implement in 2.0 than in the current version of the application.
So, unfortunately, we'll have to save this request for 2.0's future roadmap. Keep the feedback coming if you have more thoughts!
Edgaras
Naitik Mehta: alright;) What’s the ETA of 2.0?
Naitik Mehta
Edgaras: We shared an update here recently and will continue to share as things fall into place 🙏 Memberstack 2.0 🙌
Edgaras
Having the same issue. We want to change Stripe business account, and now we have to remove all of our paid subscribers and manually ask them to sign up again. This is a huge bottleneck. Some of them might churn.
Naitik Mehta
Edgaras: If possible, could you share more about the decision behind changing your Stripe business account? Trying to understand the scenario in which this situation/bottleneck would occur 🙏
Edgaras
Naitik Mehta: sure! It often happens that you have an existing business, so you use your same Stripe account for the new project. Then if this project becomes a bit more successful you want to register a new Stripe account (often together with a new business entity).
Naitik Mehta
Edgaras: Got it, thanks for elaborating! I'm going to check with our engineering to see what the limitations & possibilities could be here, but I'm not hopeful since it could get technically super-tricky very quickly.
Memberstack sometimes offers native features that Stripe might not have (eg: coupons), and that are controlling Stripe subscriptions on our backend, so it would require a lot of re-wiring.
Either way, stay tuned :)
Edgaras
Naitik Mehta: just to mention one thing, Stripe is actually supporting the migration, with some manual process of writing to support, but not everything gets migrated:
From Stripe support email regarding the migration:
---
"In short, we can copy over Customer and Credit Card (and/or ACH) details."
"We cannot copy over Subscriptions, Subscription logic, Charges, Invoices, Plans, Coupons, Events, Logs, SEPA sources, Bacs PaymentMethods, Connected accounts, or additional objects. I recommend reading through these references if you have subscriptions to recreate in the new account:
"Customer IDs will remain the same between source and destination but card IDs will change. Even though card IDs change, they will still refer to the same card details (i.e., card number, expiration date, address, etc). Customers will still exist in the source account, so you can continue to charge them there. Customers will not be informed that this copy is taking place in the background.
Before we can copy over any information, we'll need to verify the migration for both accounts." (...)
---
But regardless, it would be super helpful if at least customers could be connected to Memberstack again after the migration.
Naitik Mehta
Edgaras: Amazing, this is great input, thank you! The fact that customers can exist simultaneously in both the source and the new Stripe account gives me some hope. Will continue to share any updates here.
Naitik Mehta
Thanks for sharing this! I'd love to hear more thoughts on this — I've asked our engineering team for more input here as well.