I was also unpleasantly surprised. My initial reaction was that Stripe had jumped the shark to create a Paypalesque checkout experience.
I switched to Stripe Checkout to allow me to focus on other tasks. I was using a versioned API (v2 in the URI), and then it was changed unexpededly. I had to stop in the middle of busy week and go code up my own payment form and get it into production.
My chagrin wasn't just over the UI changes, it was also that the data fields collected and passed to my app changed. (The "Name on Card" field was dropped and email address added)
I switched to Stripe Checkout to allow me to focus on other tasks. I was using a versioned API (v2 in the URI), and then it was changed unexpededly. I had to stop in the middle of busy week and go code up my own payment form and get it into production.
My chagrin wasn't just over the UI changes, it was also that the data fields collected and passed to my app changed. (The "Name on Card" field was dropped and email address added)
I think it would've been prudent to respect the versioned API (https://checkout.stripe.com/v2/checkout.js), and do A/B testing on the latest (https://checkout.stripe.com/checkout.js).