#josh_error
1 messages ¡ Page 1 of 1 (latest)
đ 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/1376715564751261857
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
hello! I'm taking a look, gimme a couple of minutes
No worries
hmmm, okay, so looks like you were making a destination charge. For a destination charge, the related objects (e.g. that charge id included) all exist on the platform which in this case is acct_1QyNdE4DV5v9huRd
Okay that is my platform account. how do I make it such that the acct_1QyNtFQO0RUdDsWD can see / control those charges and perform refunds
Thanks for looking into this so quickly
if it helps, you can take a look at this diagram for a visual representation : https://docs.stripe.com/connect/destination-charges?platform=web&ui=stripe-hosted#flow-of-funds-app-fee
Thank you so much, so if I do this You can set the on_behalf_of parameter to the ID of a connected account to make that account the settlement merchant for the payment. When using on_behalf_of. The connected account should be able to see the charges and payment intents, and be able to perform refunds via the payment-details embedded component?
ah, nope, so destination charges (regardless of obo) follows that diagram. The difference is just with who is the merchant of record
if you want to allow the connected account to see / control those charges, then you need to do direct charges