Live data from Hacker News

Stripe Checkout

stripe.com

191–200 of 214 posts

Re: Stripe Checkout

#191
post #119

Earlier quoted context omitted.

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

Great job, it's the best HTML5 animation I've seen so far that doesn't stutter like crazy on this (admittedly underpowered) laptop.

And it does a great job at actually communicating exactly what you wanted it to, which is also an uncommon skill.

Re: Stripe Checkout

#192
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…

Here's a suggestion - why not move the "remember me" checkbox to the screen that appears AFTER the user submits the form? If they don't fill the form out, there will be nothing to remember. And when they do, they've invested enough time and effort to WANT to save their work. Plus, they got to the finish line quicker and with less distractions.

In short, "remember me" should be done after the user presses a button to submit the form.

Re: Stripe Checkout

#193

Earlier quoted context omitted.

The canvas element is only used on Chrome as it has a hard time rendering animations above a big CSS radial-gradient. The whole animation is just using DOM elements, CSS transitions/animations and requestAnimationFrame. And yes, entirely handmade :)

If the code is modular enough, would you mind open sourcing it (or blogging about how you developed it)?

Probably not exactly similar to what Stripe did but I recently released a tool for creating demos http://www.castbin.com/

Would like to get feedback on what you really liked about Stripe experience and how to improve Castbin.

Re: Stripe Checkout

#194
post #155
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…

> We consider it our job to optimize the Checkout in order to maximize our users' revenue. Even if you ran a controlled study and determined that this checkbox increases conversion by 100x for 99% of your merchants, it is still quite possible that for someone out there with some business in some selected market it harms them (potentially enough to be devastating). There is a reason why PayPal has tons of tiny little…

No, PayPal is fucking incompetent. That's why they have like 4 APIs that do the same thing, except they don't have feature parity and you need a feature from the Pay API and another feature from Express Checkout and you can't do either one of those because PayPal sucks.

Re: Stripe Checkout

#195

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"

Would hiding via CSS work?

It's in an iframe, so no.

Re: Stripe Checkout

#196

Earlier quoted context omitted.

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.

Incorrect! You can now use Knoxpayments.com and micro-transactions are free - enjoy!

Looks pretty good. Except I assume it's only for US customers? We're based in Germany, where bank payments are more common than credit cards (because only relatively few people actually have credit cards).

Re: Stripe Checkout

#198

The demo of checkout available at https://stripe.com/checkout uses a canvas element for the demo animation. It's a really well done walkthrough. Was it entirely custom-coded or done using a framework / tool to help?

The canvas element is only used on Chrome as it has a hard time rendering animations above a big CSS radial-gradient. The whole animation is just using DOM elements, CSS transitions/animations and requestAnimationFrame. And yes, entirely handmade :)

Best HTML5 animation ever. Really good job guys, completely immersive.

Re: Stripe Checkout

#200
post #119

Earlier quoted context omitted.

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

I wanted to read more of the screens, a way to pause it would have been nice.
Post reply on HN