That's funny, because I recall in 2015 hitting their endpoint for a large-ish customer, and if you added a boolean to get the total result count, it would 500 every time, presumably because it was doing some kind of "SELECT count(1)" over a postgres table. IIRC, Stripe was ruby internally for a long time, no?

Also their documentation was frequently just straight up incorrect (as in the described json schema for a response was violated. keys missing, different field names, etc.).

But it's been over 10 years, has it improved since then? I'm still in my impression of their stack from back then, although they were decently mature by then as well.