#changpet_code

1 messages ¡ Page 1 of 1 (latest)

bold wigeonBOT
#

👋 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/1337497506355089529

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

main shore
#

So if I understand correctly, you're a Platform and some of the Platform's Connected Accounts share customers and, you want to be able to "track" the payments a customer made across all of the Connected Accounts?

orchid ivy
#

Yes, that's correct. We ideally want to be able to look at a customer on our main platform account and see all the payments they've made on different connect acounts within our platform. In addition, we want to be able to track all the payments made on the connect accounts on our platform, since the only other way would be to navigate into connect accounts to see payments

main shore
#

Unfortunately this is not something you can do.

#

You're unable to attach an object from one account to another. In this case, the payment method you shared pm_1QplirH5xbpgiwgVT8jDflyp is associated with the Connected Account and cannot be used by the Platform even if it's the same customer.

orchid ivy
#

Are there alternatives to be able to achieve something like this? A way to better track all payments from connect accounts in one area on the stripe dashboard

bold wigeonBOT
main shore
orchid ivy
#

So, when someone gets a subscription in a connect account, it would make a customer in the connected account, and we added logic to also create a customer with the same info on the main platform account. Is there anything we can do on the main platform account customer to be able to reference the connected account customer(s)? Maybe the metadata, some other field. Wanted to see if there's anything that I may be missing

near mirage
#

Yeah you can do it through metadata or just keep track of this in your database

orchid ivy
#

would you be able to elaborate on what a good approach would be using this method?

near mirage
#

I wouldn't rely on metadata tbh

#

I would keep track of this in your db

#

Especially if you're going to have a lot of different connect accounts

#

With direct charges, flows where you need a customer to make payments across many accounts get complicated

#

This is a good use-case for destination charges

#

However, if you want these connect accounts to manage their own subscriptions, then destination charges aren't really an option. You'd need to continue with your current approach

orchid ivy
#

Other people that handle subscriptions for connect accounts, is the "correct" approach to handle the subscriptions and product within the connect accounts? Or do some make the subscriptions on the main platform account and handle destination charges instead?

#

And also, we could store in our DB instead, was wondering what type of info you'd suggest I would store in order to handle this problem

near mirage
#

There is no correct approach. It's what works best for your use case. There's tons of people that do both

near mirage
orchid ivy
#

I have an unrelated question that also has come up, when creating a price on the connect account and setting the price value ($10), if I wanted to edit the price later on, I saw there's no way to delete the price in the API and instead I archived it and then created a new price with the same value. Is that the only solution to this?