joelalcedo-on_behalf_of | Stripe Developers | Page 1

ripe spruce Sep 2, 2022, 6:37 PM

#

Setting on_behalf_of is how you change the Merchant of Record for destination charges. So instead of the Platform being considered the merchant of record, it's the connected account. You'll want to read https://stripe.com/docs/connect/destination-charges#settlement-merchant

Creating destination charges on your platform

With Connect, you can create charges on your platform account, take fees, and then transfer remaining funds to your connected accounts.

valid ore Sep 2, 2022, 6:45 PM

#

i see. so in other words, if i wanted to keep the platform as the merchant of record, and use stripe.transfers.create which allocates a percentage to a certain connected account, i should not use on_behalf_of in the original payment intent, right?

ripe spruce Sep 2, 2022, 6:46 PM

#

Correct. You would leave it out if you want to keep the platform the merchant of record

valid ore Sep 2, 2022, 6:48 PM

#

thanks so much karbi!
i have a related follow up question...
if i wanted to include connected_account id as a relevant metadata field in the payment intent object, without using on_behalf_of (as i would like to refer to this field in the webhook after a successful payment intent is emitted) what would the appropriate field be?

#

i'm thinking using the "metadata": { }, field would be the right move but not sure if there's a. better solution

ripe spruce Sep 2, 2022, 6:55 PM

#

Putting it in the metadata would be fine - but I also want to mention, if you only plan on doing a transfer to a single account you could just set transfer_data so that the transfer is done for you automatically when the Payment Intent is paid

valid ore Sep 2, 2022, 6:59 PM

#

omg, THANK YOU SO MUCH!!!!!
i was overcomplicating this so much,
i built an entire webhook connected to my server just to try to pull this off when i could have just used the transfer_data field 😵
appreciate your help so much and have a great weekend

#joelalcedo-on_behalf_of