iconate-connect-onbehalfof

[final chasm]

I think I just figured it out ->

on_behalf_of means the platform is responsible for the fees, chargebacks, refunds? vs stripeAccount option means the connect account is responsible for those things?

[sleek cedar]

yeah it depends a lot on your business model and the type of accounts you work with, see https://stripe.com/docs/connect/charges

basically: if you use Standard accounts -> direct charges.
If you use Express/Custom => Destination charges (or separate and transfer)

which one do you use?

[final chasm]

custom

[sleek cedar]

so yes you want Destination. And whether to use on_behalf_of or not depends on your business model. It's documented here in details: https://stripe.com/docs/connect/destination-charges#settlement-merchant

[final chasm]

Gotcha, so id throw in on_behalf_of if the connected account is going to be the responsible.

and remove if the platform is going to be responsible

[sleek cedar]

not really, read the doc carefully

you're responsible for all refunds and negative balances/disputes as the platform

[final chasm]

Why is this the case? Direct for standard only

[sleek cedar]

because that's how it works, as a plartform using Custom you take on all the risk since you collect all the information and we don't have a direct relationship with them

you shouldn't use Custom otherwise

[final chasm]

Ok so even if I was using custom, using stripeAccount option when creating a payment intent, doesnt really do anything different from a responsibility POV

[sleek cedar]

correct, with Custom/Express you hold liability

[final chasm]

This has been helpful, thanks