#maxypoo
lilac wharf
When creating a transfer object, you will need to calculate the amount yourself and specify it to the API. For our subscription APIs we do allow setting the application fee as a percentage, but that is for a different flow and otherwise the exact amount needs to be specialized
lethal spoke
Understood thank you
lethal spoke
Hi, just did a little bit more looking around the API docs and our codebase.
We are actually creating PaymentIntents and specifying the transfer_data.destination https://docs.stripe.com/api/payment_intents/object#payment_intent_object-transfer_data
If we are creating a PaymentIntent with amount=100, but the transfer_data.amount=80, does that mean the paymentintent is created for 100 but we only transfer 80 of it?
empty galleonBOT
lilac wharf
Correct, transfer_data is how much will be sent to the connected account. So your platform keeps the total amount minus that transfer amount. This doc explains it much better than the API reference does https://docs.stripe.com/connect/destination-charges#transfer-amount
lethal spoke
Thank you!! 
Will the connect account know what the original amount on the PaymentIntent is, compared to the amount in the Transfer Data? We want our customer to be aware of the fee being taken out for reporting's sake.
austere urchin
Hello! I'm taking over and catching up...
lethal spoke
No rush 😄
austere urchin
For a destination charge, no, the connected account won't see the total. They'll only see the amount you transfer to them.
If you want them to know the total you need to relay that information to them in another way.
lethal spoke
Do you have any suggestions on how to do that?
austere urchin
Typically that kind of information would show up in whatever UI/portal/etc. you build for your connected account holders.
It wouldn't be handled inside Stripe.
lethal spoke
Gotcha, ty
austere urchin
Happy to help!
lethal spoke
I did a little more digging around on that doc linked earlier,
https://docs.stripe.com/connect/destination-charges?shell=true&api=true&resource=payment_intents&action=create#application-fee
this application_fee_amount sounds like it would be relevant, do you think this might work for my use case?
From how I read it, it sounds like it would transfer the full amount to the connect account, and then transfer back the application_fee_amount to our platform account.