#GiovanniV-rate-limits
1 messages · Page 1 of 1 (latest)
do you know what are those limits ?
Yup! We document those here: https://stripe.com/docs/rate-limits (I'd highly suggest reading through this whole doc). It's 100 reads per second and 100 writes per second (with some exceptions like the Files API)
yes, we saw this, we wanted to confirm that stripe doesn't have separate limits for failed requests specifically
Gotcha - no, we don't have separate limits for failed requests
Also, feel free to use this thread for your new question - copy pasting it here:
Hello team 1 more question Does Stripe support re/captcha for the checkout flow natively? The checkout product mentions triggering captcha to prevent card testing. All the clients of Stripe with this widget (which requires a publishable Stripe key) are susceptible to card testing problems, so I'm wondering if there is a solution to combat it.
Which widget are you speaking about specifically?
Ah, so you're referring to legacy checkout! We don't specifically support captcha with that product, and we really don't recommend it for a variety of reasons (as you've already said - it was susceptible to card testing, it isn't SCA compliant, etc). One solution would be for you to implement captcha on your end BEFORE the customer gets to that specific UI
But again, if you're building a new integration I really would recommend you look into using something else
something else like what ?
Like our current Checkout product (https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=checkout)
thank you very much always the BEST service with you guys
👍
does the new checkout element support captcha?
Hello, stepping in
yes we do present captcha in case it's a 3D Secure card and we detect some unusual pattern about it.
But I don't think you can somehow manually configure captcha
so is part of the 3D secure and all inside that element is not controlled by stripe but by the Banks right ?
Yeah