#myenggoodest_api
wispy raftBOT
đ 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/1329315681296191559
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
minor orbit
Generally, Stripe doesn't recommend to use Direct Charges, i.e. using Stripe-Account header for Express connected account as the Express connected account doesn't have full Dashboard access. Direct Charges is only recommended for Standard connected account.
For Express connected account, Destination Charges should be used: https://docs.stripe.com/connect/destination-charges?platform=web that the payment will be created on the platform, then transfer the fund to the connected account.
placid frost
if we use destination charge and provide on_behalf_of parameter it wont result in error? and the parent's TOS URL will be used?
minor orbit
When on_behalf_of is used, connected account will be the business of record for the payment when the customer sees it.
For TOS URL, it should be the one on the platform account. I'd recommend giving it a try in the test mode to ensure that it meets your requirements