#samara-perfectlypanda_best-practices

1 messages · Page 1 of 1 (latest)

opal daggerBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1410710645506179203

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

wintry badge
#

Hi 👋

Customer object IDs will remain the same between the source and destination accounts but the payment IDs will change.

blissful tulip
#

Is that true if there's an existing customer ID?

For example:

  • Customer purchased a product from us via Stripe in 2023. This generates a customer ID on our primary account which we do have stored in our database
  • In January, they purchase a subscription through the secondary account, which I'm guessing means they have a different customer ID there?
  • If I do a straight copy, that customer would now have two seperate customer IDs that I need to keep track of?
opal daggerBOT
blissful tulip
#

I would prefer it's 1:1 customers to IDs. I can deal with multiple, but I want to be sure that's the best option I have.

ebon pine
#

Hello, creating the new customers on the other account would create new IDs and that is the best option unfortunately. We don't really have a good way to migrate and keep the same customers IDs

blissful tulip
#

If the steps I outlined are correct, that's fine. I appreciate confirming that's the correct process. We do sometimes run into customers that ended up with two different IDs now, so it's not a huge hardship.

ebon pine
#

Ah actually it looks like our support team may have a process that lets you keep those IDs. This server is mostly familiar with the API, so the steps that you laid out definitely make sense if you want to do this migration yourself, but it may make sense to reach out to our support team:
https://support.stripe.com/questions/copy-existing-account-data-to-a-new-stripe-account

Copy existing account data to a new Stripe account : Stripe: Help &...

Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

blissful tulip
#

I think that's for new accounts- it seems like it'll have the same issue becuase both accounts are a couple years old at this point.

#

I appreciate you looking into this for me - unsure yet if we'll end up using API or UI options, but it doesn't look like it matters much

ebon pine
#

I'm not familiar with the process, but I'm not immediately seeing anything saying that accounts need to be new to do it. So I am unsure there, but the support team will know for sure.
Also something that may help you if you are doing this via the API is payment method cloning
https://docs.stripe.com/connect/direct-charges-multiple-accounts
To do it, you would use our OAuth process to make your primary account a connected account to the secondary account and then you could use the secondary account's API keys to do the PM cloning so no one needs to re-enter their PM info.
https://docs.stripe.com/connect/oauth-reference

blissful tulip
#

Oh, that's going to be useful. Thank you!