Laughed out loud when I heard this as my experience with Stripe's API has been quite different. Stripe does quite well with keeping support for old versions of their API, but they're not afraid of making backwards-incompatible changes between versions. We encountered quite a few of these last time we were updating the SDK, and while I was going through their API docs a few weeks ago, I saw quite a few more that we'll need to make next go-around. I wouldn't call that "low needs" myself.