#joelalcedo-connect-refunds
1 messages · Page 1 of 1 (latest)
Hi 👋 that's going to be partly dependent on your integration path, do you know what type of charges (direct, destination, separate charges and transfers) you're using or planning to use?
hey Toby, so sorry for the delay
No worries, toby had to step out but I can help
hey Pompey!
the payment flow i am following right now is:
stripe.paymentIntents.create({
amount: finalPrice,
currency: 'usd',
transfer_group: data.orderID,
customer: customerID,
setup_future_usage: 'off_session',
transfer_data: {
amount: finalPrice*0.1,
destination: connectedAccountID
},
so for every single payment intent on the app, i have a price, a customer, payments are tagged as 'off_session', and there is transfer_data with the amount sent to the connected account
If you tell us to reverse the transfer I think we will still pull the proper funds from the connected account even if the original charge's funds were already paid out. I will look to confirm this https://stripe.com/docs/connect/destination-charges#issuing-refunds
And if you can't immediately get the funds back like that, there are other methods to get them. We have an account debiting feature that you can use to pull funds from connected accounts as appropriate. Otherwise there are other methods like taking higher application fees on future purchases until that amount is paid back https://stripe.com/docs/connect/account-debits
Ok, this is extremely helpful, thanks so much Pompey. Really appreciate your support & hope you have a great weekend ahead.