#jarnold7613
1 messages · Page 1 of 1 (latest)
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.
- jarnold7613, 4 days ago, 5 messages
- jarnold7613, 5 days ago, 3 messages
- jarnold7613, 5 days ago, 8 messages
Hi there 👋 if you're working with Express Connected Accounts, our recommendation is to work with Destination Charges (there are known gaps that you will encounter if you try to use Direct Charges). This is where we talk about refunds for those in a bit more detail:
https://stripe.com/docs/connect/destination-charges#issuing-refunds
With Destination Charges, the payment happens on your Platform account, and is followed by a Transfer of funds to your Connected Account. The Refund should also mostly appear on the Platform since that is where the associated Payment Intent exists.
We aren't too familiar with how the dashboard presents that information, as we primarily focus on helping developers work with our SDKs and APIs in this forum. Refunds do take time to process, similar to payments, though.
Yeah, that's what I am currently doing. Will look at that article and contact support if I can't figure it out. Thanks!
I needed to set the following:
reverse_transfer: true,
refund_application_fee: true,
Ah gotcha, so you were only refunding the payment from the Platform, and weren't recovering the funds from the Connected Account when doing so?