isaac.pak | Stripe Developers | Page 1

vital foxBOT May 19, 2023, 10:20 PM

#

sterile glen May 19, 2023, 10:20 PM

#

I can provide a req id if it'll help debug the problem

pallid moth May 19, 2023, 10:21 PM

#

Hi, yes that would be helpful. Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request

Also, Charges API is deprecated and we recommend that you migrate to Payment Intents, https://stripe.com/docs/payments/payment-intents/migration

sterile glen May 19, 2023, 10:21 PM

#

req_MaXyvAK2GfgCg4

#

We're slowly transitioning over to this new flow behind launchdarkly

#

I can dig for more request ids if necessary

pallid moth May 19, 2023, 10:27 PM

#

No need, looking

sterile glen May 19, 2023, 10:28 PM

#

Thank you!

pallid moth May 19, 2023, 10:30 PM

#

It you're passing idempotent key, https://stripe.com/docs/api/idempotent_requests yes. Looking at this request id, it does not appear so, https://stripe.com/docs/error-low-level#idempotency. Are you making these calls to charge again?

sterile glen May 19, 2023, 10:33 PM

#

Yeah we have a unique idempotent key that's passed over.

#

We also have retries in place

#

Glad to hear that these requests aren't being charged though

#

We've only had a handful of these API errors come our way

pallid moth May 19, 2023, 10:37 PM

#

To add a bit more details, 500 errors are generally indicative of an internal server error and you should treat the outcome/result of that API request as indeterminate. You'd want to read more about it here: https://stripe.com/docs/error-low-level#server-errors

sterile glen May 19, 2023, 10:43 PM

#

Gotcha, sounds good

#

So even with payment intents, I'd imagine this API error could be thrown as well

pallid moth May 19, 2023, 10:45 PM

#

Payment Intents could also return 500 errors, yes

sterile glen May 19, 2023, 10:45 PM

#

Cool, thank you for clarifying and those docs.

#

🙂

#isaac.pak