#mtoledo2_connect-application-fees

1 messages · Page 1 of 1 (latest)

ivory badgerBOT
#

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

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

safe ravine
#

Hi 👋

The difference between these two are how you get the funds. If you use transfer_amount, the charge is created on your Platform account but only the amount you specified is transferred to the Connected Account.

On the other hand, if you specify application_fee_amount, then the entire charge amount is sent to the Connected Account and then the application fee amount is transferred back to your platform account.

hoary wharf
#

ahh interesting

#

but payment intents and the resource creation doesn't change

#

just the backend flow of payouts?

#

Correct?

safe ravine
#

Nope, just the movement of the money

#

With the Application Fee amount, there are more payment objects created to move the money back and forth, so tracking dow the Stripe fees can get more complicated. But, as far as charging the customer goes, it's all the same