Earlier quoted context omitted.
Thanks for the replies. By stable, I meant something that doesn't have the unpredictable UI variations of checkout.js, which for some of us is a significant concern. (See various previous HN discussions about Stripe, particularly around the time the phone number/remember me changes came in.) When there was always the alternative of using stripe.js (as also repeatedly mentioned in previous HN discussions) this wasn't…
Thanks very much for the feedback. (Feedback helps! As you may remember from the previous thread, we did change the Remember Me + phone number fields to be optional, in large part because of the feedback we got on HN.) Each new payment method comes with its own constraints. We'll always try to give our users as many options as possible while working within those constraints. The constraints with Alipay are particular…
That's good to know. FWIW, I hadn't heard anything about that change, which would have been of immediate interest to at least one team I worked on that was still relying on checkout.js at the time.
Each new payment method comes with its own constraints. We'll always try to give our users as many options as possible while working within those constraints. The constraints with Alipay are particularly tight, and for now the only way we can satisfy them is through checkout.js - but over time, if we can relax that, we will.
Understood, and thanks again for taking the time to explain.