Live data from Hacker News

Stripe Checkout

stripe.com

41–50 of 214 posts

Re: Stripe Checkout

#41
post #12

Anyone know if they are they using an open source tool to run the intro animation? Can't tell from the minified source.

We coded it from scratch.

Looks great. Broadly speaking, can you talk about what you used? Just raw CSS animations / transitions?

Re: Stripe Checkout

#43
post #39
post #29

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

It's awesome that you've tested Checkout and are confident that it helps conversion. Would you guys consider releasing the experiments that your ran? I think it'd be a great lesson in testing out products pre-launch.

Yes, we'd love to write a blog post about this, and have considered doing something along these lines. Look out for more on this front.

Re: Stripe Checkout

#44
post #29
post #23

Stripe Checkout is nice, but unfortunately it's not suitable for us, since the "Remember me" checkbox cannot be hidden. "Remember me" is confusing for users. What is being remembered? By whom? When you're dealing with users who may already be concerned about whether it's secure to enter their credit card number into your website, I feel like the "Remember me" box is just adding another layer of confusion and concern.…

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

I think the trap here, a function of scaling any business, is that what's best for most of your customers isn't necessarily best for all of your customers. Another perspective is that what's right for your 2013 customers isn't necessarily the right thing for your prospective 2014 customers.

One possible outcome of your decision is that you're optimizing for customers who have repeat business and against customers with one-off business. That may well be right thing for Stripe.

I am a strong supporter of opinionated software but I think that view has to be colored with "this solution will be wrong for some customers" and "we are not building a solution for every customer". I imagine these assumptions are implied in your explanation above.

Re: Stripe Checkout

#46
From your video, I noticed that on a smart phone, you authenticate user by sending a code through text. Isn't that redundant? Whoever has that phone will get that text..

Re: Stripe Checkout

#48

The checkout on mobile app looks great. Too bad this cannot be used to unlock functionality in the app after payment, it will be rejected by Apple.

That was my initial thought too. "How would this work on mobile if it's not giving Apple a 30% cut?" Turns out "mobile" means "mobile web", not to be used in-app.

Re: Stripe Checkout

#49

I really want to use Stripe but it would be great if they had a more favorable pricing structure for microtransactions. Paypal, for example, will charge 5%+$0.05 or 2.9%+$0.30 (whichever is lowest) for digital goods transactions.

This. You basically have to use PayPal or Amazon Payments when you're dealing with microtransactions if you don't want to lose up to 40% just in processing fees.

The workarounds with bundling transactions don't really work for my use case.

Re: Stripe Checkout

#50
First off I'm a huge stripe fan I recommend them to clients daily.

I contacted stripe about an option to disable remember me on an existing stripe checkout form at the request of a client.

I was very surprised stripe said that wasn't going to be an option. They said we tested it and it will increase your conversions so it's not going to be optional.

Not very stripe like at all. I can understand it being on by default to move things toward their business goals. And it even looks like a nice feature.

But for it to be required doesn't seem friendly.

Being developer focused I would expect stripe would appreciate having control over the look and feel of your checkout process.

I'd like to hear an explanation of the issue it would cause stripe if it was on by default but they provided a flag to turn it off like some of the other checkout fields.

Thanks again for a great product.

Post reply on HN