youzi

[kindred python]

/cc @amber vale

[echo wing]

Hi there

Overall yep this is the right way to do things. We document our rate limits here: https://stripe.com/docs/rate-limits and mostly what you want to make sure of is that you have strong retry mechanisms in place in case you do end up hitting a 429.

[amber vale]

Thanks for the quick response @echo wing. Can you confirm whether Stripe Elements makes API calls that eat out of the rate limit budget?

Specifically, we've been getting feedback about redundant calls to ElementsSessionRetrieve in our previous implementation. This specific endpoint does not show up in your documentation.

[echo wing]

Yes we do make some requests under the hood client-side like the one you mentioned in order to fully handle confirmPayment

[amber vale]

So for each transaction, how many API calls would we end up making at minimum?

[echo wing]

I believe there are two client-side requests made but you don't really need to worry about client-side -- those rate limits are per IP