News for hackers. Stuff that matters.
Re:Stripe Checkout by Chris_Newton on Wednesday March 05, 2014 @05:27PM (#7350393)
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 start with my usual caveat that while I’m discussing negatives here in the hope of promoting improvements, we’re generally positive about Stripe, and I’ve waxed lyrical about checkout.js specifically in the past. This appears to have been a blip and hasn’t particularly shaken our general confidence as Stripe customers.

I should also acknowledge that I did promise to send the information below to one of Stripe’s people who replied to my e-mail several weeks ago, and I haven’t; mea culpa. I might as well put it here for general discussion at this point.

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. That simply shouldn’t happen. I appreciate the desire to incrementally improve things, but not everyone will share the same views on what is an improvement, so pushing changes to our user experience in an uncontrolled way is not really acceptable to us.

For example, our customers typically sign up once for a subscription and then never enter their card details again, so the remember-me changes do absolutely nothing positive for them or us. On the other hand, almost the first customer we had sign up after the changes went live then contacted us to say he’d put in an incorrect phone number and could we please change it to a different one he mailed to us. Our first reaction was that we didn’t collect phone numbers. This is how we discovered Checkout had been changed. Then we looked on the Stripe dashboard to see how to update the information, and it’s not there, so all I can do is mail the Stripe support team to ask for help (and, to be fair, they did, very quickly). So now I’ve gone from having a reasonably streamlined sign-up process to having a paying customer who is distressed because they’ve made a mistake and I can’t even fix it for them. Epic fail.

We had similar reactions to the prompt for an e-mail address, when we had chance to watch some users signing up in person a few weeks ago (not watching them actually enter their card details, of course). They’d just entered their name, postal address and e-mail address on our create-account form, clicked through to pay by card, and now the next thing they get is a prompt for much the same details again! I think every person who signed up that day challenged something at this stage in the process, several being suspicious of spam.

Perhaps the most surprising thing to me, as someone who’s seen overwhelmingly positive views of Stripe on forums like HN, is that the Stripe brand was a clear negative in the sign-up process. In the UK, Stripe is not a well-known organisation in the way that say a high street bank is, and we appear to be losing some level of business immediately because of the branding. For example, someone mailed us essentially asking why we’d let this Stripe organisation hijack our site. There was clearly some general uncertainty from that particular user — they also thought the Stripe form was not secure, because on their iPad it popped up in a separate tab and they didn’t see the padlock icon in the usual place — but uncertainty is to be expected from non-technical customers.

I wanted to send them links to authoritative sources to prove that Stripe was legitimate, but this proved surprisingly difficult. Googling any likely variation of “Stripe PCI” or “Stripe security” turned up more negative links than positive ones on the first SERP (justified, correct, or otherwise, there they were). When I searched for “Stripe hack” I found numerous links to a site called Hacker News, which of course is no surprise to us but more so for our non-geek customers. When I went to look up Stripe’s entry in the Visa Global Registry, as linked from their own site (https://stripe.com/gb/help/faq#pci-compliance), it only showed them as operating in the US and Canada, but both we and our customer were in the UK.

So the bottom line is that we’re going to move away from both Stripe-controlled UX (where the changes have been a clear negative in our case) and the Stripe branding that comes with Checkout. It’s a shame, because the idea is still a great one and obviously it’s more work for us to redo the integration, but when 100% of the customers you’re watching sign up don’t like something about your sign-up process...

Re:Stripe Checkout by pc on Wednesday March 05, 2014 @05:37PM (#7350446)
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 think the structural shift is most important. Normally, you build a payment form and move on. Maybe you eventually get time to revisit it a year later. By integrating Stripe’s payment form, your checkout is continually improving. As we refine and iterate over time, we’ll be able to immediately pass enhancements on to anyone who uses it. We’re looking forward to seeing what you build, and to doing our part to help improve commerce on the web."

Still, I apologize that it was surprising -- and, especially, that it caused any issues for your customers. I think we likely made a mistake not emphasizing this even more than we have. Checkout is very much an ongoing work.

> For example, our customers typically sign up once for a subscription and then never enter their card details again, so the remember-me changes do absolutely nothing positive for them or us.

Well, the goal isn't just to store card details for your customers -- the idea is also that people don't have to type details on your site if they've already typed them on some other site.

Your points on the flow are well-taken (we now enable you to pre-fill email addresses nicely), and you're right that we should probably create a customer-facing "Why you should trust Stripe" page.

While Stripe.js will always be a first-class citizen on Stripe, and you're obviously very welcome to use it, my sense after reading your comment is that most of your issues are likely solvable. If you've any interest in talking more, I'm [email protected].

[1] https://stripe.com/blog/stripe-checkout

Re:Stripe Checkout by pseudoanon723 on Wednesday March 05, 2014 @06:32PM (#7350765)
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 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).

Re:Stripe Checkout by teach on Wednesday March 05, 2014 @05:47PM (#7350512)
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 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 by pc on Wednesday March 05, 2014 @05:51PM (#7350549)
Hm, could you email me? [email protected]. 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.
Re:Stripe Checkout by natemcguire on Wednesday March 05, 2014 @10:19PM (#7351658)
So, I as a user see the remember me option ONCE, and it's only the first time I check out with stripe, right? Then in theory I go to some other site and it increases conversion on site b because it pre-fills my saved CC info, etc. It seems plausible that change will increase conversion on the second site, but as appears to be the case anecdotally, the change can decrease conversions on the first site. Seems like this could be painful for a site with one-time sales. Could it instead be a dialogue that pops up with clear stripe branding that asks if you want to remember the card for future visits on the web and explains what it is?

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.

Re:Stripe Checkout by sroussey on Thursday March 06, 2014 @01:36PM (#7355647)
The important thing to see, I think, is that the gains will come not on the first day this rolled out, but over time. One tiny merchant on a single day as the only data point is a sad sample to base decisions on. Particularly for said tiny merchant. Their pick up in sales will not happen immediately, but with time. Removing the "Remember Me" in freakout mode will likely be just shooting themselves in the foot, in a very short term way. But then again, even big companies only worry about the next quarter's financials, and the government so longer invests in infrastructure, so I guess this is the new normal.
Re:Stripe Checkout by teach on Thursday March 06, 2014 @04:48PM (#7356857)
I'm not talking about a change in a single day. The change in question happened in late December, so I do have SOME data.

If I lose sales for two years and then EVENTUALLY get a bump, that's two years of network effects and word-of-mouth that I've missed out on.

Re:Stripe Checkout by Chris_Newton on Wednesday March 05, 2014 @06:22PM (#7350715)
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

For anything it’s worth, I had never come across the idea of Checkout as a test platform before this discussion, nor seen that blog post. We first discovered Checkout while looking through the basic integration documentation on your site as it was at the time (probably about a year ago) and it seemed like the obvious way to go rather than having yet another form to implement manually and then use stripe.js.

If that has always been the policy, perhaps we should have known and somehow we missed it. In any case, while you’re almost certainly right that most of the issues I mentioned are fixable, it seems like an even clearer decision to move to stripe.js now, because the one issue that it seems won’t be fixed — because it’s already working as intended from your point of view — is ensuring stability in our UX.

we should probably create a customer-facing "Why you should trust Stripe" page

I could not agree with this more strongly. If I could have directed my hesitant prospect to a single page setting out Stripe’s credentials, preferably linked to reputable independent sources for verification, then if nothing else it would have saved us a lot of time trying to figure out what to say and then probably coming up with much the same answer as 1,964 other businesses who use Stripe anyway. :-)

Re:Stripe Checkout by saurik on Wednesday March 05, 2014 @07:56PM (#7351128)
> Perhaps the most surprising thing to me, as someone who’s seen overwhelmingly positive views of Stripe on forums like HN, is that the Stripe brand was a clear negative in the sign-up process. In the UK, Stripe is not a well-known organisation in the way that say a high street bank is...

I am pretty shocked this came as a surprise... customers are not developers: Stripe is just a credit card processing company, providing no user-focussed services (as does your bank, PayPal, or Square, all companies a user might plausibly have heard of and could theoretically have some positive trust associated with: of course, one would also be surprised if a user recognized "Square" even if they use one every day at some restaurant, and depending on your target market they might also not have heard of "PayPal", and while large banks tend to have a lot of brand recognition, it tends to be tied to local regions where the bank operates).

Re:Stripe Checkout by cvburgess on Wednesday March 05, 2014 @08:38PM (#7351278)
I've experienced this first hand. Stripe is great, and so (was) checkout, but the silent iteration is terrible as a developer. You wind up with support calls saying "why does this look different" and you have no idea anything changed. It's tiring.