Kinno - payment | Stripe Developers | Page 1

upbeat vortex Aug 4, 2022, 1:28 PM

#

Hello, do you have a Stripe ID for this payment that I can look at?

maiden jungle Aug 4, 2022, 1:30 PM

#

py_1LSDB3D8QolFAiVJ45elPJ25
Is the ID I believe

upbeat vortex Aug 4, 2022, 1:31 PM

#

Thank you, checking in to it.

#

And how did that charge come to your attention?

maiden jungle Aug 4, 2022, 1:33 PM

#

Our CTO + 1 more person were looking through some of our data as we plan to expand some of our functionality regarding stripe, not sure how exactly they fell upon this one though, if it's important I can ask or invite the person here

upbeat vortex Aug 4, 2022, 1:41 PM

#

No need for now. I can see a log of the API call that created this charge. It actually looked like the call errored for some reason though the Charge was still created. https://dashboard.stripe.com/logs/req_M4J13c9zgRwzWG

#

Unfortunately this is always kind of a possibility so we recommend treating 500 errors as indeterminate https://stripe.com/docs/error-low-level#server-errors

#

So it can be useful here to build in error handling for these scenarios. Not fully clear what might be appropriate here but I will consult a colleague on what might help

maiden jungle Aug 4, 2022, 1:47 PM

#

I'm guessing the case is then that the charge actually went through and that it's our side that is now missing the information and depending on how heavily we rely on webhooks vs requests it might be a bit of a pain to get the updated information

upbeat vortex Aug 4, 2022, 1:49 PM

#

Yeah, we should have send a webhook about that Charge, checking in to what was sent for this one.

upbeat vortex Aug 4, 2022, 2:26 PM

#

Hey apologies on the long delay here. I am still looking in to this but have not found webhook events on this at the moment. We found the internal error that seems to have caused this but I don't have further info on the moment on how your system could have worked around this error

upbeat vortex Aug 4, 2022, 2:54 PM

#

Hey apologies for the delay. So it looks like there wasn't an event sent here either, though they typically should be. Unfortunately we don't have comprehensive advice for how you may want to handle these errors in future. You can try to react to errors like this as best you can programmatically and have events as fallbacks but for errors like this the solutions may be messy so it comes down to monitoring these errors, especially ones that couldn't be handled by those fallbacks, and you can work with the customer/stripe support if those automatic fallbacks don't work.

maiden jungle Aug 4, 2022, 2:55 PM

#

I see, well since we have the request it should be possible to replicate the flow that usually happens, this specific instance where even a webhook isn't launched is pretty rare iirc right? Not sure if handling this kind of case specifically would be possible anyways :/

upbeat vortex Aug 4, 2022, 2:56 PM

#

Exactly. This is very rare and unfortunately there isn't a one-size-fits-all solutions when this does happen.

maiden jungle Aug 4, 2022, 2:58 PM

#

I see, thanks for all the help so far in identifying the issue :D
We'll move into investigating what steps we have to take using the request log you found and hope for the best

Have a nice day and once again thanks for the support you provided :)

upbeat vortex Aug 4, 2022, 2:59 PM

#

Of course, glad we could clarify a bit of what is going on. Just let us know if you have any further questions

#Kinno - payment