#cashiersprit
rain locust
vivid path
Hi there, sorry for the delay!
frigid widget
I won't call 8min as a delay really 😉 thanks so much for your helps 👍
vivid path
Ah, this appears to be due to Stripe's adaptive acceptance. More details on this are available here: https://stripe.com/guides/optimizing-authorization-rates#adaptive-acceptance
In this case, our models determined that the charge should be retried but it appears the retry also failed
frigid widget
en, but your retries will change the charge_id?
in my understanding, if retries charge failed, it should use previous charge_id 😉
vivid path
Right, the retry will trigger a creation of a brand new charge object
frigid widget
but we have no idea of 2nd charge id until you suddenly inform us that 2nd charge action is failed too
we know 1st charge id since we got it when confirm payment intent
but ok, thanks for your explanation. I think we may need to adjust our current behavior. in our old understanding, the charge id is binded to payment intent id, otherwise, an error throw out. obviously, it is not applicable anymore