#yulu_code
molten sirenBOT
👋 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/1443949176504451215
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
chilly lichen
hey there 👋 looking into your question now
plush oar
Thank you!
chilly lichen
for the connected account to be the one that pays the Stripe processing fee directly, you would need to use Direct Charges (i.e. PaymentIntent created on the connected account)
https://docs.stripe.com/connect/charges#stripe-fees
https://docs.stripe.com/connect/direct-charges-fee-payer-behavior
since your code snippet has transfer_data.destination, it looks like you've been leaning towards Destination Charges instead (PaymentIntent created on the platform) - is there a specific reason for that?
for context, who pays the Stripe fee is just one factor to consider when choosing what Connect charge type to implement - there are other factors that are also important, such as who is responsible for managing refunds/disputes
even if you end up implementing Destination Charges, you can still pass the Stripe fee on to the connected account by increasing the application fee (even though technically, with Destination Charges, the fee is taken from the platform's balance first)
your platform profile should give you a recommendation for which charge type to implement: https://dashboard.stripe.com/connect/settings/profile
plush oar
Thank you! If I use Direct Charges, does it deduct platform fee first or stripe fee first?