In test mode, how many operations per second are allowed for each type (read and write) before hitting the limit?

In test mode, how many operations per second are allowed for each type (read and write) before hitting the limit?

• A. 25 operations per second for each type.
• B. 100 operations per second for reads and 100 for writes.
• C. 10 operations per second for reads and 50 for writes.
• D. No limit in test mode.

Answer: (A)

Understanding rate limits is essential when working with Stripe. In test mode, the API imposes a cap to simulate production constraints, and this cap applies separately to reads and writes. You can perform up to 25 read operations per second and up to 25 write operations per second, independently. If you exceed these limits, you’ll receive a 429 Too Many Requests response, so you should implement a backoff strategy (with exponential backoff and jitter) and retry later. The key point is that the limit is per operation type, not a single combined limit, which is why the 25-per-second-per-type rule is the best fit.

Understanding rate limits is essential when working with Stripe. In test mode, the API imposes a cap to simulate production constraints, and this cap applies separately to reads and writes. You can perform up to 25 read operations per second and up to 25 write operations per second, independently. If you exceed these limits, you’ll receive a 429 Too Many Requests response, so you should implement a backoff strategy (with exponential backoff and jitter) and retry later. The key point is that the limit is per operation type, not a single combined limit, which is why the 25-per-second-per-type rule is the best fit.