#meisei81
forest charm
rapid remnant
hi! It depends on the exact Charge flow you're using : https://stripe.com/docs/connect/charges#types
if you mean you're using Direct Charges when you mention "the stripe connect user is the merchant", then the connected account pays the Stripe fees.
left palm
I don't think I have specified any charge types when creating a stripe checkout session
I've specified the two parameters payment_intent_data[transfer_data][destination] and payment_intent_data[on_behalf_of] in creating checkout session api
Both values of the parameters are connect account id
rapid remnant
you should know which type of charge you're using since it would be clearly stated in the guide you followed and it's a core design decision of how to build your Connect integration
in any case, if you're using transfer_data[destination] then that's Destination Charges
which means the platform pays all the Stripe transaction fees
left palm
how could I make the user paid the transaction fee?
rapid remnant
one way would be to use Direct Charges, but that is then a quite different integration
this is why this is a core design decision you would make before you write any code, you'd read the docs thoroughly and understand the various account and charges types before writing code and discovering this later
left palm
oh no... it seems we have to re-design our flow
Can I just change the transfer_data value to reach the effect?
We've published the feature to the production environment. I want to find a simple way to solve this issue.
rapid remnant
not really no, there's no simple solution, choice of which Charge to use is a core part of the design of your integration and the docs clearly state how the fee flows work
moving to Direct from Destination takes some work since for example, you're using Checkout, so if you refer to Price price_xxx objects, right now you are referring to Price objects that exist on your platform account, for Direct you have to create/refer to objects on the connected account instead.
I'd suggest taking a step back, checking the docs again, and thinking deeper about the overall design of your marketplace set up
left palm
Well. Which docs should I check?
trail charm
You'd want to look at this page: https://stripe.com/docs/connect/charges#types
That outlines the different types of payments available with Connect
left palm
Hi, I've just make a stripe connect payment which charge type is directly, and the payment_intent id is pi_3LzI8y2QYrCdj1c01HfmCkId.
Could you help me to confirm that is the correct way?
And the transaction fee is paid by the stripe connect account, not the platform.
I do this according by the docs https://stripe.com/docs/connect/creating-a-payments-page?destination-or-direct=direct-charges
trail charm
Well, depends what you mean by 'correct'. But yes, in that example the connected account (acct_1LLgFF2QYrCdj1c0) was the MoR (merchant of record) and the transaction fee was charged to that account – a direct charge
left palm
Now the transaction fee is paid by our platform because of using the payment intent destination. We want the stripe connect account, which is the merchant, to pay the transaction fee.
So, the payment intent that I've just created can archive the effect, right?
trail charm
Yep!
left palm
ok. thanks
trail charm
That's how direct charges work: https://stripe.com/docs/connect/charges#:~:text=The connected account’s balance will be debited for the cost of Stripe fees%2C refunds%2C and chargebacks.