#jemen_docs
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1313787601668542496
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello, @fossil grail ๐
I saw those diagrams, but I'm just not sure, when do Application/Stripe fees are being deducted, in what moment? In direct charges, let's say is it automatical?
In destination charges do we need to handle it?
And why are destination charges better fit for marketplace-like apps?
๐ happy to help
Hello, @fallow void ๐
I'm just not sure, when do Application/Stripe fees are being deducted
the Stripe fee objects are created automatically upon the success of the charge regardless of the type of Charge
And App fee object?
Also object is being created you said, so there is need to pay it manually?
do you mean the application_fee_amount?
(aka Application Fee object)?
it depends how you're integrating
whether you're using the application_fee_amount or the transfer_data.amount or a Separate Charge and Transfer
No, no. We are deciding ONLY between direct and destination chargers, rn.
the decision about Direct vs Destination boils down to a matter of who needs to be liable in case of refunds and disputes
So, if it is Direct Connected account is liable, in Destination is opposite?
yes in Destination it's the platform
OK, I see.
and the platform would also pay the Stripe fee (but you can account that as being part of the application_fee_amount that you would eventually deduct)
Yeah, I saw the diagram, when direct stripe fee is on side of Connected account and when destination, we (platform) pays it.
Right?
correct
Great, great.
Let's imagine two scenarios:
- We use direct charges - money goes, to connected account, two fees "objects" are being created - application_fee_amount and stripe_fee?
- We use destination charges - money goes, to us, we send money to connected account subtracted with our fee, and then stripe_fee object is being created?
We just don't know when those "Objects" you said, are being created, you see?
you don't have to worry about that because you don't need to create them, we (Stripe) create the objects automatically for you
OK, that's great.
So, what happened, when Connected account, not paid those?
Or maybe we forgot?
Where do we get those objects?
Does it have maturity date?
And one more question, why is destination charges better suited for marketplace-like apps? Is it because we have the responsibility about users which operates on our platform?
the fees are automatically deductible
what you get in your Stripe Balance is the net value that you see in the diagrams
yes exactly
This is interesting, can you elaborate more?
You mean, no matter what, those fees are being deducted?
yes correct
And one more thing, I saw two scenarios in destination, how do I choose one?
do you mean with or without on_behalf_of?
Without
this is about the settlement merchant
I saw two scenarios in destination, how do I choose one?
which two scenarios are you referring to if notobo?
You mean this?
There are two scenarios how to do it, I can choose, right? How?
It is about settlement merchant?
no
this is basically the choice of whether you want to use application_fee_amount or transfer_data.amount
Oooooh
you can read more about this here https://docs.stripe.com/connect/destination-charges?platform=web&ui=stripe-hosted#collect-fees
This is great!
Great, I think that's it. Pleasure to cooperate with you. ๐
let me know if you need any more help