#koldhielo
1 messages · Page 1 of 1 (latest)
Yeah don't rely on chatgpt
Use our official docs
Especially since docs change with new things regularly
Are you using destination charges? Also what type are your connect accounts (standard, custom, express)?
I'm looking through the docs and as helpful as they are, I can't really see much that clears this up.
I'm using standard connect accounts for my platform, and sorry what is a destination charge?
Yeah this is why I can't recommend chatgpt for you to learn how to use Stripe. Because if you had read our official Connect docs, one of the very first things you do is choose connect account type and charge fund flow
The fact that you're unaware of what destination charge but are using them in the above code isn't great
That being said, I can help stear you in the right direction
Yeah I'm sorry, I'm a bit of a noob in regards to this and admittedly I have been relying heavily on ChatGPT as I struggle to understand docs sometimes and where to find what I need. it's gotten me so far, but yeah.
I would appreciate that
The destination charge what you talk about though is essentially the transfer_data parameter that transfers the funds to the connected account?
Yeah
But that flow is not recommended with standard accounts
So if you have to use standard accounts, I would not recommend that route
Always recommend reading this first: https://stripe.com/docs/connect/accounts
That will help you determine which account type is right for your use-case. Then, if you determine standard accounts are the best flow for you, you should use direct charges instead: https://stripe.com/docs/connect/direct-charges. Those are recommended with standard accounts
Destination charges are recommended with Express/Custom accounts
Connect is very complicated, so docs are key. Chatgpt gets a lot wrong about it
You're not wrong there. It's been really helpful for the most part going from ChatGPT then to your docs, but yeah as I say I struggle where to look when it comes to docs.
Thank you for the info and the links - I will soak up as much as I can. If I have any questions or queries, would I be okay to ask them on this thread?
Hello! I'm taking over and catching up...
We close idle threads after a little while, but you're welcome to ask a new question in #dev-help if this thread is closed!
And on that note, from a brief look at the connect/direct-charges page, it seems that I need to use the stripe_account parameter and put my business.stripe_id value in there instead of using the transfer_data parameter. So I'm assuming this will have the same result of transferring the funds to the business' Stripe account.
So, when you process a refund like this:
refund = stripe.Refund.create(
payment_intent=appointment.intent_id,
refund_application_fee=True,
stripe_account=business.stripe_id,
)
Will this then refund the full amount to the customer from the business.stripe_id account, and also issue the business.stripe_id account a refund of the fee that I charged from my Stripe account?
Thanks a lot!
No, not really. The stripe_account property is used to make API requests on your connected accounts. See here for more details: https://stripe.com/docs/connect/authentication
In a direct charge scenario the Charge lives on the connected account, not on your platform, so to refund it you need to make the Refund creation request on the connected account where the Charge lives.
I think I understand what you're saying. So if I was going to charge an application fee in this sense with a direct charge, would it more so be a case of using stripe.Transfer.create?
No.
For direct charges you create the payment on the connected account and set an application fee. The application fee is transferred to your platform automatically; you don't create the Transfer manually yourself.
See here for details: https://stripe.com/docs/connect/direct-charges#collecting-fees
It's the refund bit that is confusing me. Will the code above that i wrote not refund my application fee and my connected business' client?