rogeryang_popchill

[keen veldt]

hello! To clarify, do you mean you want to refund an already captured payment? Or do you want to cancel the held amount?

[hoary badger]

both.

We found the api https://stripe.com/docs/connect/separate-charges-and-transfers#issuing-refunds

[keen veldt]

https://stripe.com/docs/payments/place-a-hold-on-a-payment-method#cancel-authorization

[hoary badger]

but we just want to know is it correct to call this api when we haven't capture yet?

I mean we just want to cancel the pre-authorization.

[keen veldt]

this section explains exactly that : https://stripe.com/docs/payments/place-a-hold-on-a-payment-method#cancel-authorization

[hoary badger]

So, we have to intergrate two situations when we separate auth and capture?

In the pre-auth session, we call the cancel paymentintent api?

In the captured session, we call the refund charge?

Is it correct?

[keen veldt]

yep, that's right

[hoary badger]

thanks!

and another question

Should we save charge id when we call this api?https://stripe.com/docs/payments/place-a-hold-on-a-payment-method#capture-funds

the response parameter "latest_charge" is the charge id to let us used in the refund charge api?

[keen veldt]

you could refund with a PaymentIntent id also if that's what you prefer : https://stripe.com/docs/api/refunds/create#create_refund-payment_intent

[hoary badger]

ok I see, but can we call this api to cancel a pre-auth payment intent?

which means in two situations, we call the same api to refund? And just pass the paymentintent id?

[keen veldt]

i thought we just discussed this?

In the pre-auth session, you would call the cancel paymentintent api
In the captured session, you would call the refund charge

[hoary badger]

I see, so we should use two api to intergrate refund?

[keen veldt]

yes, that's correct