#masonhale-connect
1 messages · Page 1 of 1 (latest)
hello, reading
Is there a better way for me to create manual Transfers that will follow the same pattern (especially with regard to the amount and application fees) as the Transfer automatically created when the PaymentIntent has the transfer_data[destination] and application_fee_amount set?
there is not! There are two ways to take fees, one is by explicitly taking an application_fee_amount (in which case the transfer is made to the connected account and then the fee comes back, per https://stripe.com/docs/connect/destination-charges#flow-of-funds-app-fee) ; the other way is by transferring an amount less than the actual payment, so the fee is the difference.
application_fee_amount is something you can only use when doing a Destination charge, there's no way to use it when doing a separate charge and transfer to multiple accounts, you can only use the other approach
as such you might find it easier to switch your destination charges to the other approach(https://stripe.com/docs/connect/destination-charges#transfer-amount) , so at least things are consistent for you in how you can analyse your payments and fees instead of split between some objects having ApplicationFees and some not.