Stripe Checkout
141–150 of 214 posts
Re: Stripe Checkout
#142Earlier quoted context omitted.
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.
Yes, this could be the right approach -- we should perhaps have something like HEAD and STABLE.
Re: Stripe Checkout
#143Re: Stripe Checkout
#144I wish someone would make something that is as easy to use as Stripe but also offers Paypal. The few I've seen are still everything and the kitchen sink, not just a simple stripe + paypal combo.
Re: Stripe Checkout
#145Earlier 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…
I think this is an excellent, well thought-out reply. It still doesn't matter if Remember Me is better for merchants or not. What matters is whether the merchant wants to be able to hide that feature or not. If they choose to shoot themselves in the foot, it should be their choice. There are only a few actually plausible reasons why a service would prevent turning this feature off. A nanny mentality (we know what's b…
Re: Stripe Checkout
#146Earlier quoted context omitted.
That's a neat idea.
If recurring vs not is important to how Remember Me is perceived, and you've been a/b testing it, you could probably test this particular hypothesis easily.
Re: Stripe Checkout
#147From 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
#148Re: Stripe Checkout
#149From 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..
Whatever API they are using the get the phone number without the user entering it on mobile is probably easy to spoof. It may not even work on all platforms and the user may have to type a phone number in that case. Would you trust a phone number handed to you by a PhoneGap JavaScript method, for example? It would be pretty easy to tweak to return whatever is needed.
Re: Stripe Checkout
#150Earlier 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)?