#oj_api
vernal epochBOT
👋 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/1316022081674018906
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
clear pier
👋 happy to help
it depends on the type of Charges you're hoping to achieve
in the case of Direct Charges the product catalog should be created on each Connect Account
whereas in the other scenarios you can have the product catalog maintained on the platform
languid frost
ah ok, yes so i think then it makes sense to move them to the connected account, as they are two different legal entities that need to process certain charges directly. I hoped to get off easy and just define all the products on the platform account, but will move them to the connected account
clear pier
even if they are 2 different legal entities, you can still use the Destination Charges with on_behalf_of to specify the settlement merchant
the decision on whether to use Destination or Direct Charges relies more on who pays the Stripe Fees https://docs.stripe.com/connect/charges#stripe-fees and who's responsible for Refunds/Disputes/Charge backs
Creating payments using destination charges or separate charges or transfers, with or without on_behalf_of, always debits refund and disputed amounts from your platform balance, even when Stripe is liable for negative balances on your connected accounts.
languid frost
Ok, will talk the finance department, to figure out what is the best way forward, thanks for clearing up how to structure the charges!