#zishaansunderji - transfer data destination
deft talon
steady obsidian
Awesome! Thanks a ton!
amber cloud
Hi there 👋
As you're using transfer_data.destination it seems like you're working with destination charges, in which case your platform is responsible for refunds and the flow that you're describing sounds like expected behavior.
https://stripe.com/docs/connect/charges#destination
steady obsidian
Hi! I see - so we're executing refund service side in Node JS by making the following request:
const refund = await stripe.refunds.create({
amount: amount,
payment_intent: paymentIntentId,
});
Do i need to pass the transfer_data.destination here as well?
I see charges in the link you sent - but not how to execute refunds
I'm looking at this link right now: https://stripe.com/docs/api/refunds/create - and maybe I have to specify reverse_transfer as true?
amber cloud
That link explains the behavior of various charge types, and the key line in this scenario is the following one from the "Destination charges" section:
Your account balance will be debited for the cost of the Stripe fees, refunds, and chargebacks.
You should be able to initiate a reversal of the transfer to the account when you create the refund by setting reverse_transfer to true.
https://stripe.com/docs/connect/destination-charges#issuing-refunds