#Pete - API Error
lone hornet
Hello! Can you give me the request ID showing that error? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
lone hornet
Thanks, looking...
Looks like this was an issue on our end that should be cleared up now. Can you try again using the same idempotency key and see if you get a successful response?
ashen notch
I shouldn't re-process the transaction. Looks like the user went ahead and did it themselves.
Just showed up in my Sentry logs and happened to catch it, was curious if something I passed in was incorrect.
If all is good; then I'll ignore 🙂 Thank you!
ashen notch
Right, but wouldn't that process the transaction?
lone hornet
No, have a look here: https://stripe.com/docs/idempotency
ashen notch
Apologies, I must be dense; I'm reading this:
Clients can safely retry requests that include an idempotency key as long as the second request occurs within 24 hours from when you first receive the key (keys expire out of the system after 24 hours)
as:
If i re-request with the Idempotent key, it won't create a duplicate request.
However, the user refreshed the page and initiated a new request all together that successfully went through. My concern here is if I process that above one, it will successfully process that transaction, creating a duplicate for the user.
Duplicate being; the idempotent successfully going through, and the user's which they refreshed the page and created a new one.
lone hornet
Oh, I see what you're saying. That's correct, however, it could be that the original Charge attempt also went through. The 500 indicates an indeterminate state; it may have worked, it may not have worked. You should check to see if there's a duplicate Charge to refund.