Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Stripe Checkout

stripe.com

Post reply on HN
Print view View original

121–130 of 214 posts

Re: Stripe Checkout

#121

Post by filearts »

pc wrote: post #62
thatthatis wrote: post #56

Earlier quoted context omitted.

Why isn't it removable? I know things about my customers that you couldn't. This is the single biggest thing that makes me question whether I trust stripe long term. If you're going to make netwok decision like this now, where's your limit? It stops feeling like payments for developers and starts feeling like a "PayPal that hasn't started fucking over their merchants... yet"

> Why isn't it removable? Well, I tried to outline the thinking above, but we're not absolutely attached to it either. If there is some reason it's bad for your customers, we'd love to talk. Can you drop me an email? I'm patrick@stripe.com.

What if you could request a semver range for the checkout js file? That way vendors could opt in to fixes, enhancements or major changes and be confident in the level of volatility in UX for their customers.

Re: Stripe Checkout

#122

Post by asenna »

pc wrote: post #80
downandout wrote: post #57

Now if they only did same/next day payouts. The founder once said this was possible if you emailed him. I emailed him and got zero response, from him or anyone else, so I'm guessing they are only doing this for super high volume merchants.

Oh no, I'm sorry. I've no idea what happened. Want to try my personal email? patrick@collison.ie.

Hi Patrick, is there any timeline for international payout support? I am currently working on a marketplace project and I'm looking for options other than PayPal.

Re: Stripe Checkout

#124

Post by skilbjo »

cmapes wrote: post #119
benjamindc wrote: post #109

Earlier quoted context omitted.

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.

You really should do a blog post about it, the first thing I did after admiring the animation was pull open the inspect panel to see how it was done haha. I would love to read more about it.

I did that as well! Beautiful stuff, good on the developer.

Re: Stripe Checkout

#125

Post by Chris_Newton »

pc wrote: post #108
Chris_Newton wrote: post #104

Earlier 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…

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

#126

Post by paul_f »

pc wrote: post #95
dirtae wrote: post #88

Earlier quoted context omitted.

Maybe, but I'm not sure that a test could change my mind, unless it resulted in a massive boost in revenue. Let's say that the vast majority of my customers do not want to use "Remember me", and that most of them examine the option and leave it unchecked, as is their desire. I've still introduced friction into my payment process, and possibly left a bad taste in the mouths of many of my customers. Maybe not enough th…

Any interest in coming by Stripe for lunch/dinner? I'd love to chat about this more and figure out a good way to accomplish this. (I.e., a product you'd be happy integrating that we iterate on over time.) I'm patrick@stripe.com.

It seems your customers are telling you EXACTLY what they want - an option to remove 'Remember Me'. You don't seem to want a conversation about it so much as a chance to sell people on it.

Re: Stripe Checkout

#127

Post by djtidau »

pc wrote: post #95
dirtae wrote: post #88

Earlier quoted context omitted.

Maybe, but I'm not sure that a test could change my mind, unless it resulted in a massive boost in revenue. Let's say that the vast majority of my customers do not want to use "Remember me", and that most of them examine the option and leave it unchecked, as is their desire. I've still introduced friction into my payment process, and possibly left a bad taste in the mouths of many of my customers. Maybe not enough th…

Any interest in coming by Stripe for lunch/dinner? I'd love to chat about this more and figure out a good way to accomplish this. (I.e., a product you'd be happy integrating that we iterate on over time.) I'm patrick@stripe.com.

It's this kind of proactive engagement and quest for a clear understanding of your users and their goals that has had me waiting so impatiently for Stripe to become available in Australia.

We're prelaunch right now, but are about to implement Stripe (what will likely be checkout) shortly, after having already settled with a local payments provider.

If you're ever this side of the pond be sure to look me up and we will grab a beer.

Re: Stripe Checkout

#128

Post by benjamindc »

cmapes wrote: post #119
benjamindc wrote: post #109

Earlier quoted context omitted.

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.

You really should do a blog post about it, the first thing I did after admiring the animation was pull open the inspect panel to see how it was done haha. I would love to read more about it.

So, the technical part isn’t that crazy tbh — as soon as you respect some pretty straightforward principles you should be fine (animate only transform/opacity, favour requestAnimationFrame over setInterval, transitionend/animationend events over setTimeout, …). The complicated part was mostly the “creative” process, ie. how fast should the animation run (some people read, others don’t), what's the appropriate bezier-curve, how make the play button “engaging” enough so people don’t feel like they’re gonna watch a billion-hour screencast, etc.

Re: Stripe Checkout

#129

Post by pseudoanon723 »

pc wrote: post #108
Chris_Newton wrote: post #104

Earlier 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 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

#130

Post by pc »

paul_f wrote: post #126
pc wrote: post #95

Earlier quoted context omitted.

Any interest in coming by Stripe for lunch/dinner? I'd love to chat about this more and figure out a good way to accomplish this. (I.e., a product you'd be happy integrating that we iterate on over time.) I'm patrick@stripe.com.

It seems your customers are telling you EXACTLY what they want - an option to remove 'Remember Me'. You don't seem to want a conversation about it so much as a chance to sell people on it.

I'm sorry that it comes across this way. Checkout is an optional product. I've tried to explain that 1) we'll remove it if we find data that suggests it's bad, and 2) we're in no way strongly opposed to removing it. I mean, we're not wedded to any particular aspect of Checkout -- we just want to stay true to the goal of making informed, data-driven decisions and reducing complexity for merchants. If it's bad, we won't just add an option to remove it -- we'll remove it for everyone. This goes for any change in Checkout.
Post reply on HN