#EvanO
solid copper
supple nova
Can you share your account ID, so that I can take a closer look at how your integration works? You can find your account ID by logging in to https://dashboard.stripe.com/settings/account. It'll be in the upper right hand corner and looks like acct_123
hasty zinc
acct_1IUH13BxC1nIgm0I
To clarify, none of this has been implemented yet. This is a proposal we’re working on for modifying our setup.
supple nova
Gotcha, thanks for sharing the details!
- Are we thinking about this design correctly?
To use the connected account as the settlement merchant, destination charges on Custom/Express connected account withon_behalf_of[0] is recommended
- When a subscription is created, we want the invoice to use the business name and address for the Connect account. Do we have to set the on_behalf_of field? This field seems like it breaks Bank Transfers and Account Tax IDs, which is a non-starter for us.
Yes.on_behalf_offield should be set to use the connected account as the settlement merchant. Bank transfers don't supporton_behalf_of[1].
Which account tax IDs are you referring to here? Could you share the API spec or doc?
[0] https://stripe.com/docs/connect/destination-charges#settlement-merchant
[1] https://stripe.com/docs/payments/bank-transfers#connect
hasty zinc
What do you recommend we do to support Bank transfers while being able to charge from different entities using our Platform pricing plans?
I’m just referencing that the Connect doc on making the Connect account the settlement merchant doesn’t allow you to specify Tax Account IDs on invoices. Let me find the link
https://stripe.com/docs/invoicing/connect#on-behalf-of
The last sentence of the doc mentions it
supple nova
Unfortunately, there is no workaround to charge from different entities with Bank Transfers or using Account Tax IDs due to the limitations listed in the doc