#raghu-rate-limit

1 messages · Page 1 of 1 (latest)

sick quartz
#

Do you have an example of one of these errors? Specifically a request ID would be most useful.

Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request

left juniper
#

pi_3LL8IdD3k3512Cve2unJsn0L

#

does stripe re-tries by itself if it sees 429 ?

sick quartz
#

With automatic capture: yes. That Payment Intent, for example, was confirmed 7 seconds after the failed request.

left juniper
#

how can we turn it off. we dont want to retry on the stripe side

sick quartz
#

You can't unfortunately. You would have to proactively cancel the Payment Intent in order for the automatic retries to stop

#

Are you trying to solve this for this one occurrence of the rate limit? Or for all possible rate limits in the future?

left juniper
#

if we were to send the cancel PaymentIntent before the retry it will stop it?

#

what is the retry frequency ?

sick quartz
#

Are you trying to solve this for this one occurrence of the rate limit? Or for all possible rate limits in the future?

sick quartz
left juniper
#

all possible rate limits

#

is there a way to turn off retries for everything ?

sick quartz
#

Unfortunately not. You would have to handle the transition of Payment Intents through their lifecycle on your own without using capture_method: "automatic" in order to retry the confirmation on your own terms.

#

Are you seeing a lot of rate limit errors pretty consistently? That really shouldn't be happening

left juniper
#

we are running around a 1000 requests and some of them has the same payment methods

#

we see around a dozen failing with rate limit errors.

#

we dont listen to webhook responses for these

#

so if they resolve later its a problem

sick quartz
#

Ah, okay. The only thing I can really recommend for this is to listen for the failed payments and set up a webhook endpoint to programmatically cancel the Payment Intent if the error Stripe returns is a 429 lock_timeout or refund the payment in the case of race conditions.

#

Otherwise, you will need to batch those requests so that the rate limit is not being exceeded.

left juniper
#

ya make sense @sick quartz . well thanks a lot for taking time to answering my queries.