Hey,
Thanks a lot for the quick answer! And I totally hear your feedback. I like rants too 🙂
We made the change internally to a parameter that is supposed to be for internal use only. I don’t think this parameter has been documented in years either. So we did not expected anyone to be relying on its usage.
We take backwards-compatibility really seriously as you can see on our documentation page here and we’re really careful to ensure that we push changes that don’t affect existing integrations.
Unfortunately, it’s not always easy to know when some integrations rely on undocumented behavior as we have no way to track this easily, especially when it all happens client-side like in this case.
We’re really sorry that this broke some of your customers’ integration. It’s not the experience that we want to offer to our users.
In the future, you should feel free to contact us whenever something like this happens. We would have been able to find the issue immediately and pushed a fix that did not require you to make an urgent change on your end. I’d recommend trying #stripe on Freenode or our contact form here: https://support.stripe.com/email if you ever discover another regression like this one. Or you can always email me directly (remi at stripe dot com).
Cheers!
Remi