ethan_connect-funds-flow

[fickle snow]

👋 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/1459238070154170443

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[marble root]

thanks for submitting this for us @late urchin

[mortal prawn]

👋

This is something that would require Connect.

Platforms can copy Payment Methods to their Connected Merchants, make API calls for their Connected merchants, etc.

[marble root]

you guessed it @late urchin 😆 that's what we were thinking.
@mortal prawn is that a pretty big lift?

[mortal prawn]

It does adds some complexity relative to an basic integration for Standard account, but I wouldn't say it's a big lift per say.

There are a few different ways to orchestrate Payments between Platforms and Merchants with connect so I think the important thing is to have a clear vision of your use case so you can identify which kind of Connect integration makes the most sense for you to avoid having to redesign later.

A lot of it comes down to the type of "charge" pattern you want to engage with.
https://docs.stripe.com/connect/charges

Does a good job of breaking down the types of charges that can be used with Connect and what use cases they are best suited for.

Platforms can set up different kinds of Connect accounts for their merchants, typically Standard, Express, and Custom, but what type of Charges you want to use will typically dictate what kind of accounts you want your merchants to have.

[marble root]

ok, here is a more specific use case: With our current development we use Stripe Payment Element within our checkout page.
Product 1 is an on-demand training video, in Tenant A, with Stripe account A
Product 2 is a subscription typically sold on another site for a subsidiary business we own, Tenant B with a Stripe account B
For the eCommerce catalog for TenantA we add both Product 1 and 2 to the cart. We want Product 1 to in the Stripe Account A and Product 2 to be in the Stripe Account B and renewed from Stripe Account B

[mortal prawn]

Who would you want managing refunds/disputes? Would you like that to be the merchant/subsidiary or you as the platform?

it sounds like Express or Custom account with separate charges and transfers might be the best fitted as you can then have products from multiple connected accounts(merchants) in one checkout page.
https://docs.stripe.com/connect/separate-charges-and-transfers

[late urchin]

Looks like it's a combination where we may handle the refunds or the subsidiary may do it themselves. Which approach would allow us the most flexibility to support such a situation?

[boreal orchid]

Hi 👋

I'm stepping in as my colleague had to go.

Who handles refunds is controlled by where the payment is created

So if you are using Direct Charges where the payment is created on the Connected Account, they would be resposible for handling refunds and chargebacks.

For Destination Charges or Separate Charges & Transfers, the Payment is created on the Platform Account and that is who handles creating Refunds

But, to be clear, I still think the Separate Charge & Transfers funds flow my colleague suggested still best fits the business model you have described.