GHOST + STRIPE user duplicate on 2 different websites after successfull stripe Payment?

I have 2 websites site 1 **abc.com and another one is site 2 xyz.com hosted on GHOST cms and I connected my Stripe account with both websites. The issue is when any subscriber is subscribing to the PAID plan from the site site 1 then it becomes a user to site 2 also (it becomes a user to both the websites) which is a huge disaster for me.

Please help me with how can I solve this.

Thanks in Advance.

Have a look here: Multiple Ghost sites - should I use separate Stripe accounts?

Looks like Ghost won’t be able to handle two sites using the same Stripe account, unfortunately.

Make a second stripe account - Stripe allows more than one, and they can all share a login.

Export your members list. Check that it is complete. Do the same for the other site. If you have a site backup option, use it.

Then unlink one Ghost site from Stripe and link it to the new Stripe.

Import your members list (after removing free members and members of the other site, if you can tell who is who) to the re-linked site, if the subscriptions don’t appear correctly.

2 Likes

I have a total of 6-7 sites (currently 2 are working) hosted on GHOST so it is not sound good to create separate Stripe accounts for each domain.

Stripe makes it very simple to create separate sub-accounts all managed by the same login/owner. You can find more info here.

2 Likes

How would you even manage to do that using Stripe?

When you set up to use Stripe you need to type in the domain where it is supposed to be used. So making an account for site 123.site mean that you use that account for 123.site and not for 321.site. 321 needs its own account account under your main profile.

If you place your cursor on your account name up in the left hand corner and click the arrow you’ll get a drop down menu where you can add on a new account. It can belong to the exact same company and share all details but the actual website where it is supposed to be in use.

ps, I don’t get why they call the user profile and the “companies” accounts. For me it would make more sense the other way around

1 Like

I think it’s a major limitation (for me rather a bug, tbh), which doesn’t seem justifiable as Stripe separates products nicely based on IDs etc., so I imagine that it would easily be doable to “follow” only Ghost’s own products. It’s not unusual that an organisation uses one Stripe account for multiple subprojects. (Which brings me to a feature request to let the user define metadata that is transferred to Stripe – one of Stripe’s very nice features.)

For now (as long as it is not fixed/supported), I would advice to warn the user upon Stripe connect that other Stripe products in the same account (i.e., products not “generated/owned” by this Ghost instance) will interfere with the Ghost instance.

@prschulz thanks for pointing to a workaround (Stripe subaccounts)!

Having switched on paid memberships this afternoon I’ve just realised - due to duplicate emails - that I had a trial DigitalPress site also connected to Stripe. I’d wiped this trial site, but when they sign up to a paid membership on my site hosted on MagicPages they also appear on the DigitalPress site. Grrrr!

Only a few have signed up now (but they’re obviously precious!) … I cannot disconnect Stripe from the DigitalPress site “while there are still members with active Stripe subscriptions”

Can I just delete the members from the DigitalPress site, disconnect the latter from Stripe, and they will remain on my active site? I’ll obviously back them all up first. The only members on the DigitalPress site are those who signed up from MagicPages.

Just when I thought I was getting the hang of this :wink:

OK … the answer to my own question was, as suggested, to individually delete members from the ‘wrong’ DigitalPress site (making sure to not disconnect them from Stripe), then disconnect the DigitalPress Ghost account from my Stripe account.

I wasn’t brave enough to do this without first creating a new paid member in my own name!

It cost me a processing fee, but solved the problem :wink:

2 Likes