#piercy
hot pollenBOT
Hello! We'll be with you shortly. 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.
solid egret
Hi 👋 what type of Connected Accounts are you working with, and what Charge structure are you using?
left grotto
Express account, and its charged by creating a payment intent on the connected account. We're using application_fee_amount to get our bit from the connected account
also, we're not passing in receipt_email
solid egret
That's not a recommended flow (using Express Accounts with Direct Charges) and this scenario is one of the reasons. When using Direct Charges, the settings of the account control a lot of the behavior that is seen, but you can't get to those settings if you're working with Express accounts.
It's why we recommend using Destination Charges if you're using Express Connected Accounts, so then payments happen on your Platform Account and your settings control the behavior that is seen.
left grotto
er, maybe i misworded it..
I believe were using the platform accounts secret key, and then passing in the accountId of the connected account
but now I say that I am going to double check thats the case..
solid egret
That sounds like a Direct Charge, those are the flow that use the stripe-account header to make requests for Connected Account.
left grotto
So the recommended way is to transfer the money to the connected account?
Wouldn't that mean on a refund we have to reverse that transfer and sort everything out?
solid egret
Yup, our recommendation for those account types is Destination Charges, which process the payment on your Platform Account and then create a Transfer to move the funds to your Connected Account.
https://stripe.com/docs/connect/charges#destination
https://stripe.com/docs/connect/destination-charges
Yes, thinking about reversing the Transfers is something you'll need to think about (similar to how you had to think about whether/how to refund application fees for Direct Charges).
https://stripe.com/docs/connect/destination-charges#issuing-refunds
left grotto
Im going to have to see how this would change things. I will say its getting rather frustrating every option thats taken seems to now have a "new way" thats now the recommended way and the old ways get forgotten about
account onboarding is all changing to drop the oauth functionality, now this all changing. It feels a lot like stripe want to get out assisting us with what we want it do , and instead we do it all ourselves
solid egret
I totally get that (and it's something our team actively advocates against because we see how frequent changes are painful), but this is not a recent change. We've always recommended Destination Charges for Express or Custom Connected Accounts.
left grotto
Well, nothing you can really do about it but we've had nothing but pain from stripe over the last few months. This is just another thing were going to have to tank and deal with.