nikoschns_best-practices

[brittle herald]

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

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

[jagged oar]

Direct charges & separate transfers are not compatible with one another, they are mutually exclusive flows

Direct charges are created by your platform directly on a (single) connected account, and the funds settle to that connected account. Your platform optionally takes an application fee related to that payment.

Separate charge & transfer payments are two steps: first a payment on your platform (not on a conencted account, like a direct charge), then second is making one or more transfers to connect accounts to split those funds. Your platform keeps the difference between the payment and the transfers.

transfer_group is largely a convenience for you to track transfer related to a single customer payment/order etc.

[granite crescent]

Thanks for the response. And the second step (sending funds to connected accounts) can happen immediately after the paymentIntent is confirmed or the funds should be captured first?

[jagged oar]

If depends on how you control the flow of funds

if you want the funds to be tied to the pending charge (ie, using source_transaction) then you'll need to capture first