#noodle_unexpected
autumn abyssBOT
đ 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/1328860030740729958
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
opaque roost
Hi there
Just to make sure we're on the same page, are these destination charges that you're refunding? If you're not sure, could you provide the PaymentIntent ID of the payment you refunded?
charred python
Hmm I'm not sure. Here's the payment intent ID: pi_3QhIpCP32NF091LO1iokfdDU
opaque roost
Okay, yes, it looks like you're using destination charges. When you create the PaymentIntent, you're passing transfer_data.destination to transfer a portion of the funds from that charge to a specific connected account
If your goal when creating the refund is to reverse the transfer (from the original charge) from the connected account back to the platform, you should include reverse_transfer: true in your refund creation request: https://docs.stripe.com/connect/destination-charges?platform=web&ui=stripe-hosted#issue-refunds
charred python
Ahh okay perfect. That answers it. Thanks! Have a good day
opaque roost
You too!