Atish

[bright stratus]

Hi there!

[ionic warren]

Hello

[bright stratus]

If you are using Destination Charge then the Stripe fee is always taken from the platform account. So you would need to adjust your application_fee.

[ionic warren]

Can I know the stripe charges while creating the checkout session?

Or is there any other method where stripe charges is deducted from connected account?

[bright stratus]

Can I know the stripe charges while creating the checkout session?
You mean the Stripe fees? You cannot know them in advance, only after the payment is done.
So you would try to "guess" the average fee (based on stripe.com/pricing), and adjust your application_fee

[ionic warren]

What about deducting the stripe fees from connected account?

[bright stratus]

There's Accounts Debits, but they have many limitations. You can learn more about it here: https://stripe.com/docs/connect/account-debits

Otherwise you can also use Direct Charge, in this case the connected account would pay the fee. But note that using Direct Charge has other implications, so you might not want to do this.

Another option is to use capture_method: manual. This way you can check precisely which payment method is being used, and compute the exact Stripe fee on your end. And then, when you do capture the funds, set the correct application_fee
https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-payment_intent_data-capture_method

[ionic warren]

Will you please explain what will go wrong if we use direct charge?

[bright stratus]

There's nothing wrong with using Direct Charge.

But I recommend reading this guide to better understand the implications: https://stripe.com/docs/connect/direct-charges