#bronson_best-practices
pulsar ivyBOT
đ 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/1300410939438399571
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- bronson_sandbox-email, 3 days ago, 26 messages
- bronson_api, 3 days ago, 6 messages
dreamy cypress
We wish to use direct charges for a few reasons:
- The customer will be interacting with the connected account
- Easier administration for our Ops via Stripe UI, as all the stripe entities (products, customers, subscriptions) are ring-fenced within the connected account.
However, from my understanding it is not recommended to use direct charges with our account setup type, as the connected account is liable for refunds and disputes, but they do not have access to any Stripe dashboards.
pulsar ivyBOT
analog jungle
hi! I'm taking over this thread.
who do you want to be liable for refunds and disputes? you (the paltform) or the connected accounts?
dreamy cypress
Hi!
We're definitely leaning towards the platform being liable for the disputes, but I am keen to understand the scenario where we would want the connected account to be liable and managing their own disputes, but without a Stripe hosted dashboard
analog jungle
if you want the platform to be liable, then you should use Destination Charges, with or without on_behalf_of. you can learn more about this here: https://docs.stripe.com/connect/destination-charges
but I am keen to understand the scenario where we would want the connected account to be liable and managing their own disputes, but without a Stripe hosted dashboard
it is possible yes, but quite difficult. becasue since they don't have access to the Stripe dashboard, how can they manage disputes and refunds? that's something you'll have to build yourself.
dreamy cypress
Right, Yeah I understand that.
Just so I understand - by liable do you just mean who is responsible to respond to that dispute? Or does it relate to financial reliability - eg the connected account needing to have a certain amount of balance to provide a refund?
If we wanted to manage the disputes ourselves, could we not use Direct Charges & respond via the Conntected Account UI?
analog jungle
Just so I understand - by liable do you just mean who is responsible to respond to that dispute? Or does it relate to financial reliability - eg the connected account needing to have a certain amount of balance to provide a refund?
Both, when using Direct Charge the customer is directly interacting with the connected account, not the platform. So it's the connected account who is reponsible for Refunds/Disputes/etc, and the connected account who can manage all of this.
if you want to manage all of this, then use Destination Charges
which is the recommended option when using Connected account that don't have access to the Stripe dashboard
dreamy cypress
Sorry, just on the last question - I understand it's not recommended, but is it possible to manage disputes on a connected accounts behalf with direct charges? Ie using the Stripe UI?
Appreciate your help btw!
analog jungle
I don't understand. which UI are you talking about? a UI you build yourself that your connected account can use?
dreamy cypress
Sorry, the Stripe UI that we have access to as a platform. Eg we can see a list of connected accounts, and then in each account see their payments / products / customers etc.
analog jungle
not sure, we are not very familiar with the Stripe dashboard here. you could try asking that question to Stripe support directly: https://support.stripe.com/contact
pulsar ivyBOT
dreamy cypress
Ok, thanks for your help!
Just writing a quick summary to confirm if thats cool
If I can just sum up, the essential decision around which charge type to use is who we want to be responsible for refunds & disputes.
Given we are not providing a Stripe hosted Dashboard to connected accounts, connected accounts will not be able to do this if we go with direct charges. We could build a solution in which they manage disputes for direct charges, but it would be entirely custom.
The other option is to go with destination charges with OBO - this moves the dispute responsibility to the platform level. Our primary concern with this option is the Stripe UI will be hard to use - eg there is no functionality via the Stripe UI to view customers for a specific connected account. There are ways around this, eg using the Stripe Search API & metadata, but this again would be something we have to build, and not something Stripe UI provides.
Keen to double check if the above sounds correct with you. Totally understand if that is more of a support question, and I appreciate your help so far.
pulsar ivyBOT