171–180 of 214 posts
I'll try to offer a slight variation on what others have already mentioned regarding checkout. Like many of them I find Stripe to be very well thought out and easy to implement. As far as Checkout goes, the idea is great but it might need some updates in order to make it more useful to a wider audience. As other mentioned, the "Remember me" function was enough for me to not use Checkout. It is confusing, perhaps because it introduces a mental shift in the user's mind, where out of a sudden they need to understand how this other company "Stripe" will magically keep their info across devices. A way to hide that field wouldn't harm anyone (other than Stripe's ability to do branding). It would also be nice to allow style customization of the form.
Now you're asking people to blindly punch information into a box and hit send?
Paypal really needs a new leadership team that promotes innovation. Stripe is cleaning up, and I'm about to take a lot of business to Stripe...
Earlier quoted context omitted.
Incorrect! You can now use Knoxpayments.com and micro-transactions are free - enjoy!
Yeah, no. Does that site support credit/debit card transactions? Nope. ACH / bank transfer payments are a non-starter for many people and sites, and conversion rates are much lower. I'm pretty sure the OP was referring to credit/debit transactions...
I think Knox with a fallback to Amazon Payments is a great stack for Micro if you want my opinion.
I'm probably going to try this in Bingo Card Creator in an A/B test against my existing purchase flow at some point. I'll be honest: the likelihood of the average English teacher knowing Stripe does give me a bit of pause with regards to the UX and the prospects of my VA having to answer a lot of "Who is Stripe and why are you telling them my credit card number? Did your Googles get a virus?" emails. Still, seems like it is worth testing. Worse comes to worse, all you do is go back to the pre-existing checkout flow, like whatever Stripe.js integration you're using right now, and then you have full control over the experience.
I have seen and supervised successful redesigns of purchase experiences before. They print money. BCC got a 60% or so lift in purchases using a Stripe-powered checkout back in the day, after some hillclimbing, discovery of synergistic effects, and burning the kinks out of my integration. I think there's likely motivational numbers hiding in a lot of your businesses. You should absolutely be testing them on a regular basis yourselves, but this seems to be a decent stab at a way of doing testing without requiring focus/bandwidth or major traffic [+], which are two major reasons people give me for not testing.
[+] I have noticed many people suggesting "You could do per-account multivariate testing on e.g. whether the Remember Me button is a win or not", and feel obligated to point out "That will probably only work for accounts which are doing, minimally, thousands of transactions a month." The great thing about this is that if you've got only 2k visits a month and 40 purchases if we assume that systemwide performance is a good proxy for your performance (and n.b. that's an assumption which is tractable to measurement) then we can still get solid test results by using the other millions of visitors and hundreds of thousands of transactions flowing through the system every $PERIOD.
Earlier quoted context omitted.
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…
Hm, could you email me? patrick@stripe.com. I suspect that this is an anomaly, as you say (almost all small samples will randomly skew in one direction or another), and our data strongly suggests and testing suggests that this increases sales -- but if you're right, not only will we add the option to hide it, but we'll proactively do it ourselves.
We roll our own stripe forms, so this hasn't caused us any issues. Knew that checkout was not something we would use for this reason.
This is a really bright idea, in that almost all companies do an absolutely bloody abysmal job of implementing their checkout flow. The median testing budget for it is generally zero, unless you scope the population to "large, savvy ecommerce providers." I love the idea of being able to basically take advantage of the herd effect for optimization, and clearly there are non-linear advantages to the Stripe ecosystem, b…
Here are some ways this manifests:
- longer dev cycles/increased difficulty in testing/more frequent release rollbacks
- higher merchant support costs
- harder to innovate
- a need to support dozens of legacy use-cases that only some merchants use
- harder to onboard new merchants
- more complex sales process
- inconsistent user experience for customers
- higher staff training costs/time
- impossible to optimise conversion for the majority, as each merchant is showing a different checkout.
It all starts with 1 option, but it's a slippery slope.
In summary, I think Stripe are probably taking the right approach here, and I wish them the best of luck.
I'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…
I'm trying to understand why Stripe didn't send out an e-mail to all merchants before making this change. I, too, was blindsided.