Pohlud-ratelimit-issuing

[wide igloo]

hello, you'll have to stay within the rate limits really, I recommend spacing out your requests and retrying any rate limited requests

[onyx dock]

Okay, thanks for informing me. Could you please tell me whats the exact number of rate limit Stripe uses?

How many seconds basically

Or miliseconds

[ruby furnace]

(NOT with Stripe) The rate limits are posted - they're generally 25/sec in Test Mode, 100/Sec in Live - but there are ALSO object lockouts - for example, operations for a particular customer/account can "lock" the object in the database, so such requests can't overlap

[onyx dock]

I mean why would they lock me a product Im allowed to use and im just using it?😄 And for how long/what reason? Kinda confused lol

[ruby furnace]

(NOT with Stripe) rate limits and account locks are entirely separate things. The above limits/"object locks" are to maintain integrity of the database

[onyx dock]

Still kinda confused, but what are you trying to say is that when I hit rate limit too many times the product might be locked for me? (card issuing in my case) Correct?

[ruby furnace]

(NOT with Stripe) the limits mentioned aren't about you, personally, they're about maintaining accuracy and integrity of the database

[onyx dock]

Okay, got it. Thanks for explaining, I fr appreciate it

[ruby furnace]

(NOT with Stripe) if it's either of the above limits, the API call will return a 429 status, effectively indicating you could do an exponential backoff and try again. Much better to not cause that in the first place. Resisting the urge to ask why you would need to hit a Card Issue endpoint that hard/fast...

[wide igloo]

Okay, thanks for informing me. Could you please tell me whats the exact number of rate limit Stripe uses?

https://stripe.com/docs/rate-limits documented here

thanks for the help on explaining this @ruby furnace

to reiterate that part that was confusing @onyx dock

but what are you trying to say is that when I hit rate limit too many times the product might be locked for me?

that is just saying for e.g. if you keep updating a PaymentIntent 70 times a second, while under our rate limit, you'll hit a "lock timeout" possibly (depending) cause each request has to wait on the previous request to complete, cause Stripe internally has to acquire a lock on the PaymentIntent object that is being updated, to prevent concurrent requests from overwriting each other.

[onyx dock]

HOw long does the lock timeout last? Just for me to know what to expect

Thank you

[wide igloo]

there's no time. It depends on how long it takes a request to complete

lock timeouts aren't really common unless you're operating on the same object over and over

[onyx dock]

Okay awesome, thank you so much.
Last question: when generating cards and hitting a rate limit, does the rate limit apply on the WHOLE ACCOUNT or just the CARDHOLDER Im generating cards for? I would love to generate at least simultaneously without getting rate limited.
Thank you