#raghu-rate-limit
1 messages · Page 1 of 1 (latest)
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
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
With automatic capture: yes. That Payment Intent, for example, was confirmed 7 seconds after the failed request.
how can we turn it off. we dont want to retry on the stripe side
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?
if we were to send the cancel PaymentIntent before the retry it will stop it?
what is the retry frequency ?
Are you trying to solve this for this one occurrence of the rate limit? Or for all possible rate limits in the future?
It's variable based on a number of factors, so it usually retries a couple of times consecutively, then backs off over time: https://stripe.com/docs/invoicing/automatic-collection#smart-retries
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
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
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.
ya make sense @sick quartz . well thanks a lot for taking time to answering my queries.