Stripe Checkout
111–120 of 214 posts
Re: Stripe Checkout
#112Earlier quoted context omitted.
I’m going to respectfully disagree with almost everything there, based on our experience. TL;DR: The changes do not benefit us or our customers, caught us by surprise, and created customer support issues almost immediately. As a direct result, we are now working on moving to a stripe.js form where Stripe’s branding will be hidden as much as possible and we retain full control of our user experience. I do want to star…
Thanks for the long and considerate comment. To briefly respond -- > So, we’re planning to dump Checkout for a few reasons, but first among them is that Stripe changed our users’ experience for the worse, without our knowledge or consent. When we first launched Checkout, we tried to emphasize that this was a canvas for Stripe to test out improvements. The last paragraph of the launch blog post[1] was: "Ultimately, we…
I'm the author of "Learn Java the Hard Way". My customers aren't interested in a "relationship" with me or my site. They just want my PDF.
Since you implemented this change, 1) my total sales are down and 2) the fraction of users buying with PayPal instead of Stripe has increased.
My 'N' is pretty small, so I can't with confidence say the thing is statistically significant, but it's something I have noticed.
I would VERY MUCH like the option to hide both the "email address" prompt and the "remember me" checkbox.
Re: Stripe Checkout
#113Earlier quoted context omitted.
You could also automatically run split tests on a per-merchant basis, thereby automatically auto-tune the checkout for each merchant.
That's a neat idea.
Re: Stripe Checkout
#114Earlier quoted context omitted.
[Tl;dr on the below: the changes we make to Checkout are designed to increase our merchants' revenue. If a change doesn't do that, it will be reverted.] The confusion point you cite was our biggest concern in building the "Remember me" functionality. On the one hand, it's clearly good for our merchants* if customers don't have to constantly retype their card details. On the other hand, it'd be bad if we were scaring…
We do not have many returning customers, and our customers are not as tech savvy as Humble Bundle customers, by a long shot. We are using Stripe.js with our own form instead. It's not as nice as Checkout, and I really wish I could use Checkout instead, but as a developer I need to be in control of my user experience, and "Remember me" is not appropriate for my application.
I'm doing a monthly subscription, so it feels too weird to have a "Remember Me" button. If my customers are trying to sign up for an ongoing thing, why wouldn't I remember them?
Incindentally, this is a good article that tells how to do the credit card logo, just like they do in Checkout. So I don't look too bad....
https://yoast.com/checkout-field-validation/
But still I would like to have that time back again.
Re: Stripe Checkout
#115> We've been testing this for the past couple of months—our hypothesis was that it would increase conversion rates—and we're delighted that it has been confirmed. pc, do you know if the conversion rates increased for the majority of the subscription-based sites that you monitored? Our company has a subscription-based service that uses Stripe Checkout, and some of our customers have expressed confusion regarding the "…
> pc, do you know if the conversion rates increased for the majority of the subscription sites that you monitored? We did look at the effect on individual sites (rather than across all charges as a whole). But I generally agree with you that it'd be nice to have something better-tailored to subscription website flows. (I suspect that this product might look quite different to Checkout.)
For us, the big win was having a reasonably polished and ready-made form to get from zero to having a card token, which meant one fewer thing for us to worry about during integration (and building the rest of our site, of course). That seems just as valuable whether you’re accepting single payments or signing people up for a subscription.
Re: Stripe Checkout
#116Re: Stripe Checkout
#117Earlier quoted context omitted.
Thanks for the long and considerate comment. To briefly respond -- > So, we’re planning to dump Checkout for a few reasons, but first among them is that Stripe changed our users’ experience for the worse, without our knowledge or consent. When we first launched Checkout, we tried to emphasize that this was a canvas for Stripe to test out improvements. The last paragraph of the launch blog post[1] was: "Ultimately, we…
I know additional anecdotes aren't worth much, and I'm a very small fish, but the addition of the email address and the "remember me" checkbox was an unpleasant surprise for me as well and seems to have increased confusion/uncertainty for my customers. I'm the author of "Learn Java the Hard Way". My customers aren't interested in a "relationship" with me or my site. They just want my PDF. Since you implemented this c…
Re: Stripe Checkout
#118Earlier quoted context omitted.
That philosophy works fine with merchants who hope for repeat sales from the same customer. But what about subscription payments (what I use Stripe for). A remember me button doesn't make sense there, as they are never re-entering the data to make another purchase. Perhaps you didn't test it with enough variety of merchants?
We definitely tested it with merchants who take subscription payments. But, yeah, the considerations are different, I agree. The primary motivating use case for Checkout was "standard" checkouts rather than subscription flows (even though it works well for the latter). I suspect we'll take a look at redesigning that flow entirely at some stage, with a product that may look quite different to Checkout.
"worked well". Now everyone using Checkout for subscription flow has to do work to change it. You just cost your users a lot of hours work, and my site only brings in enough to pay for the hosting costs. Err, thanks?
Re: Stripe Checkout
#119Earlier quoted context omitted.
If the code is modular enough, would you mind open sourcing it (or blogging about how you developed it)?
The code has been specifically made for that particular animation and, to be fair, it wasn’t even modular enough for my own needs :D Joking aside, I’d love to blog about it and more generally about animations in UIs.
Re: Stripe Checkout
#120I'm particularly happy that iOS Chrome is now a "first class citizen". There were some shaky times before where it (provided you saved your form) showed the mobile view that Safari gets; then where it failed completely (with a JS alert()); where it showed the desktop modal (okay, but a bit janky) and finally where it had a made-for-mobile modal. I'm a big fan of Checkout otherwise: it's definitely simplified things f…