#adhi14058

1 messages · Page 1 of 1 (latest)

south valleyBOT
#

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.

real monolith
#

Hi, let me help you with this.

#

When you put a hold on funds on a Payment Method, it's not transfered anywhere, hence it doesn't need to be refunded if not captured. You can only refund the captured amount.

#

About the second type of situation, could you please share the PaymentIntent ID pi_xxx?

untold patrol
#

Hi, Thanks for help me out. I have created a new paymentIntent
pi_3OJyh9BKLsxlmQpA0xROxlPm

#

when you cancel this this intent.. charge.refunded would be called.. which is something I wonder why

#

btw, this is in testmode

#

sorry, i dont have access to production account

real monolith
untold patrol
#

should i cancel it

real monolith
#

Yes please

untold patrol
#

done

real monolith
#

Interesting. It doesn't seem very logical, but I guess it's how it's built. Is it causing any problems for your integration?

untold patrol
#

not exactly, since this is not documented in stripe docs, I was wondering if this behaviour is consistent so that I can write logic accordingly

real monolith
#

Yes, it's consistent.

untold patrol
#

Just to double check, do correct me if i am wrong, There are no such edge case where charge.refunded would be emitted during capture of a partial amount, even though remaining amount is refunded

#

it is only emitted when we cancel a payment intent which has manual capture turned on

real monolith
#

Correct.

untold patrol
#

Thanks for your help.!!

real monolith
#

Happy to help.