jensdraserschieb_01602

[sand wagon]

To clarify, when sending the file to party B, we are creating a payment intent, which needs the final sum to be defined, however, since we don’t know the payment method etc., we cannot foresee the fees at that stage.

[azure shuttle]

Hi! you mention Connect but you only have two parties here, a merchant and an end-customer, which doesn't need Connect. Where does the Express account come into this?

B) get the total amount of fees during the payin
https://stripe.com/docs/expand/use-cases#stripe-fee-for-payment is how you can see the fees charged on a given transaction.

, since we don’t know the payment method etc., we cannot foresee the fees at that stage.
true. Generally you should just set an overall application_fee_amount that covers you and lets you make a profit rather than trying to know it up front, that's what I'd recommend.

you can later do things like use the Transfers API to make "true-ups" if you really need to.

Also you can estimate the fees, since you can test in test mode in various scenarios, and use the balance_tranasction per the link I shared. That lets you build logic in your code to estimate what fees would be and validate in test mode.
Also if you integrate in ways like https://stripe.com/docs/payments/build-a-two-step-confirmation you can see the PaymentMethod details before you need to create the PaymentIntent.

so there are solutions there.

[sand wagon]

That’s what I figured, however, ths maximum fee could be quite high and therefore unattractive (something around the lines of 5%) and might turn off users, who would otherwise only need to pay 2%.