Stripe Checkout is nice, but unfortunately it's not suitable for us, since the "Remember me" checkbox cannot be hidden.<p>"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.<p>I'm surprised that the "Remember me" checkbox can't be hidden, given how focused on their customers Stripe normally is. The "Remember me" checkbox feels like something Stripe is pushing on me to help them with their business objectives, which isn't the vibe I usually get when dealing with Stripe.
The demo of checkout available at <a href="https://stripe.com/checkout" rel="nofollow">https://stripe.com/checkout</a> 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?
This is a really bright idea, in that almost all companies do an absolutely bloody abysmal job of implementing their checkout flow. The median testing budget for it is generally zero, unless you scope the population to "large, savvy ecommerce providers." I love the idea of being able to basically take advantage of the herd effect for optimization, and clearly there are non-linear advantages to the Stripe ecosystem, because getting credential/CC pairs into the system most probably increases systemwide spend on them and that is how both merchants and Stripe make their money.<p>I'm probably going to try this in Bingo Card Creator in an A/B test against my existing purchase flow at some point. I'll be honest: the likelihood of the average English teacher knowing Stripe does give me a bit of pause with regards to the UX and the prospects of my VA having to answer a lot of "Who is Stripe and why are you telling them my credit card number? Did your Googles get a virus?" emails. Still, seems like it is worth testing. Worse comes to worse, all you do is go back to the pre-existing checkout flow, like whatever Stripe.js integration you're using right now, and then you have full control over the experience.<p>I have seen and supervised successful redesigns of purchase experiences before. They <i>print money</i>. BCC got a 60% or so lift in purchases using a Stripe-powered checkout back in the day, after some hillclimbing, discovery of synergistic effects, and burning the kinks out of my integration. I think there's likely motivational numbers hiding in a lot of your businesses. You should absolutely be testing them on a regular basis yourselves, but this seems to be a decent stab at a way of doing testing without requiring focus/bandwidth or major traffic [+], which are two major reasons people give me for not testing.<p>[+] I have noticed many people suggesting "You could do per-account multivariate testing on e.g. whether the Remember Me button is a win or not", and feel obligated to point out "That will probably only work for accounts which are doing, minimally, thousands of transactions a month." The great thing about this is that if you've got only 2k visits a month and 40 purchases if we assume that systemwide performance is a good proxy for your performance (and n.b. that's an assumption which is tractable to measurement) then we can still get solid test results by using the other millions of visitors and hundreds of thousands of transactions flowing through the system every $PERIOD.
TL;DR: +1 on making the "Remember me" checkbox optional.<p>I'll try to offer a slight variation on what others have already mentioned regarding checkout. Like many of them I find Stripe to be very well thought out and easy to implement.
As far as Checkout goes, the idea is great but it might need some updates in order to make it more useful to a wider audience.
As other mentioned, the "Remember me" function was enough for me to not use Checkout. It is confusing, perhaps because it introduces a mental shift in the user's mind, where out of a sudden they need to understand how this other company "Stripe" will magically keep their info across devices. A way to hide that field wouldn't harm anyone (other than Stripe's ability to do branding).
It would also be nice to allow style customization of the form.
At CircleCI, we've been using Stripe Checkout for quite a while. It was increadibly easy to set up and very high quality (we replaced a hacky ugly checkout page with it), and it looks really professional. That professionalism is really important at the final stage of the funnel.<p>One of the things that's really interesting about Checkout is that Stripe is actively focusing on increasing the conversion rate for us. Their new layout (with the phone number) has a 20% high conversion rate than the previous version.
We've been using Stripe Checkout at Humble Bundle for quite a while and it has been awesome. It is really easy to set up and once a customer has used it, it's incredibly easy to checkout in the future. Every couple weeks I hear about a new A/B test that is running to try to make it even better.
First off I'm a huge stripe fan I recommend them to clients daily.<p>I contacted stripe about an option to disable remember me on an existing stripe checkout form at the request of a client.<p>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.<p>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.<p>But for it to be required doesn't seem friendly.<p>Being developer focused I would expect stripe would appreciate having control over the look and feel of your checkout process.<p>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.<p>Thanks again for a great product.
> We've been testing this for the past couple of months—our hypothesis was that it would increase conversion rates—and we're delighted that it has been confirmed.<p>pc, do you know if the conversion rates increased for the majority of the subscription-based sites that you monitored?<p>Our company has a subscription-based service that uses Stripe Checkout, and some of our customers have expressed confusion regarding the "Remember me" feature. Even the CEO of our company expressed confusion initially, and he requested that I ask Stripe for the option of hiding the "Remember me" field.<p>From their perspective, there's no reason why their payment information should be remembered because they have no reason to enter their payment information again in the future since our service is subscription-based.<p>I think the "Remember me" feature would be less confusing at an e-commerce site where customers may make additional purchases in the future.<p>Also, we'd like to be able to hide the customer's email address in Stripe Checkout, not just disable the email address field.<p>So essentially, we want the old Stripe Checkout that only requested payment information.
We set it up over here @Patreon and it was EZPZ. One issue that wasn't clear from the documentation -- the "custom" setup (<a href="https://stripe.com/docs/checkout#integration-custom" rel="nofollow">https://stripe.com/docs/checkout#integration-custom</a>) is preferable for so many reasons (and it's no harder to setup, not sure why it's not just the only option) -- it doesn't "take over" the form so that a credit card is required on submit and it also returns a bunch more relevant info like the last 4 digits of the credit card, the expiration date, etc. so you can save and display the card info for future checkouts.
Hot damn. The design and experience I felt from this page is overwhelmingly great. I've always loved stripe's design and they continue to blow me away. Really excited to activate our account any day now.
This is seriously awesome!<p>I don't want to detract, but it's a shame that your <a href="https://stripe.com/checkout" rel="nofollow">https://stripe.com/checkout</a> page isn't optimised for mobile. I wanted to have a look at the demo on my phone as well as on my desktop.
Interesting move by Stripe, and I guess it explains why WePay and Balanced choose to focus on the API and not their d2c offerings.<p>With the 'remember me' feature, Stripe has chosen to impede upon the territory of their developers, which greatly concerns me.<p>I love their product, but one of the reasons I choose to use them is because of the options that their API provides. Is this a back-end play to eventually cut out developers, or is it designed to help them sell more product? I'm sure Stripe staffers will say that it's the latter, but if that's the case, who is the primary customer for this offering?
So couple of comments on stripe checkout.<p>2 big issues.<p>First off, the entering of email addresses and remember me stuff is confusing for my customers. We sign up people for a free trial and take their credit card details before we sign them up as users. Even quite technical people have dropped out of the flow after signing in with stripe thinking "I've given them my email" and so people haven't properly finished the signup process because of this (I'm guessing I can probably get this email, however I'd still need to prompt them for a password).<p>The second big issue is that the constant changing of the form kept breaking various integration/acceptance tests that I had written. This was pretty frustrating as it seemed that I would get a different box from time to time and my tests would start failing.<p>I get the desire to A/B test, and the desire to build a network of users who have already given their credit card details (obviously amazing for mobile) but it would be nice for us customers if we had a flag where we could switch it off.
Ask HN: I run a tiny home business making widgets. My web page, including order form, is pure HTML.<p>From what I can tell (looking at page source for the Watsi example), at the very least in order to use Stripe, I have to add some JavaScript to my web page, and of course test it.<p>Granted, that shouldn't be a big problem for a skilled web developer, but I'm not one.<p>Am I understanding it right?
Have been using Checkout on <a href="https://deployer.vc" rel="nofollow">https://deployer.vc</a> and <a href="https://zoned.io" rel="nofollow">https://zoned.io</a> - it's absolutely excellent: very easy to integrate, and looks really good. Will be switching over the other products as well over from PayPal.
May I ask a honest question: why did you add email and remember me? It looks something like VCs will suggest. This makes me no to trust Stripe as platform.<p>Somebody smart said: the incumbent are wounded by the first disruptor and that disruptor eventually becomes the same as the incumbent and, then, both are killed by the real disruptor.
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.
I'm particularly happy that iOS Chrome is now a "first class citizen". There were some shaky times before where it (provided you saved your form) showed the mobile view that Safari gets; then where it failed completely (with a JS alert()); where it showed the desktop modal (okay, but a bit janky) and finally where it had a made-for-mobile modal.<p>I'm a big fan of Checkout otherwise: it's definitely simplified things for me. I'd just like to see more communication regarding changes: I discovered most of those myself from my staging site.
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..
Stripe Checkout is amazing. Used it for a few months and it's worked extremely well. Glad they are constantly updating it. Looks even better than it did before.
We use Stripe checkout at <a href="http://leaddyno.com" rel="nofollow">http://leaddyno.com</a> for subscription signups using the custom integration features of the checkout widget. We also use it in our app for customers to update their billing information. Its great they made such an awesome widget and ALSO made it very easy to customize and integrate programmatically! We love it!
PC is this cross merchant? That is, if one end user of a Stripe merchant stores their card and then that same end user visits another Stripe merchant are they remembered? I see "Stripe stores your card for this site and others" or wording like that.
Nice, Checkout is great for Ad-hoc payment. I'm using WordPress Easy Digital Download plugin that already has Stripe support. EDD automatically creates user account, and tracks usages, and sends confirmation and download emails to buyers.
Now I'd just love for you all to make capable of having products attached to it and operate like a shopping cart ;) -- But seriously your designs look so good, I'd actually want that.
Stripe checkout is great, but I really miss the ability to add custom fields to the form, such as VAT number and Company name.<p>I realise that allowing to add a whole bunch of fields can hamper usability, but I have to collect the VAT number in order to figure out how much to charge the customer.<p>Does anyone have a recommendation about what to do here? Roll our own form and lose all the nice stuff from Stripe Checkout?
Display a new form for VAT after displaying checkout, and charge after that?
I use Stripe Checkout at postperfect.co. The only thing I really wish it could handle was a discount code implementation, which I had to do myself unfortunately.
I still don't completely understand how Stripe can be so cheap. How do they pass charges onto payment processors without incurring some sort of fee that is not equal to the market rate for all other transactions? Is there some sort of fee scale on the processor side that decreases as the transaction amount increases?
Very interesting. Since Checkout brings in an element of the developer contributing a user to Stripe via 'remember me', I'd love to know the tradeoff here.<p>What is the probability today, that when a user of my app hits Checkout, they will already have a credit card saved which makes signup faster?
Checkout is a great way to get started fast (like, in <15 mins).<p>Multilingual support would be great, and also a more customer friendly interface for those who might not be familiar with things like CVCs. Those two things are reasons I had to stop using checkout and use stripe.js instead.
Looking back at my sales, too many customers use Paypal to simply go to Stripe only.<p>I 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.
If you need a more advanced shopping cart, there is Snipcart that can connect to Stripe, <a href="https://snipcart.com" rel="nofollow">https://snipcart.com</a><p>The cart is fully responsive so it works on mobile as well!<p>I am one of the founders, let me know if you have any questions.
While this is admirable, it flies in the face of security-based UX. For years we've taught people to only send sensitive information over SSL, and to look for the lock, green bar, etc.<p>Now you're asking people to blindly punch information into a box and hit send?
Carl Icahn's "request" to spin Paypal out of Ebay is probably looking better with this announcement.<p>Paypal really needs a new leadership team that promotes innovation. Stripe is cleaning up, and I'm about to take a lot of business to Stripe...
Stripe is pretty sweet, and we're in their beta to receive funds in two days. Any idea how they actually do this? Two is certainly faster that the normal seven days, and I'd love any insight or theories from the HN community.
I am getting ready to launch a product. I was using Wepay until they eliminated their checkout form. Switched to Stripe, read up on the API, and implemented the form. Now you tell me their is a simple checkout widget available. Sigh.
ASK:<p>I love the UX for the stripe checkout. It seems like the integration script creates a full page iframe allowing the widget to have full control over the UX. Is there any guide to building a similar full page iframe widget for other applications?
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 has existed for a while, and I'm using it on my site. Didn't know it was "beta." Works great. (Still in test mode though, have not yet exited beta so I'm not taking anyone's money yet.)
I'm not a fan of the payment input in a separate window, although I'm not sure if that's just a browser quirk on my end. Much preferred the old modal dialog on the same page.
My name being Ben and a stripe, dribble & humble bundle user, I had to open in an incognito window to double check that it wasn't scraping my name somehow..
so how do I integrate this to my website ? I am currently using <a href="https://www.paymentiframe.com/" rel="nofollow">https://www.paymentiframe.com/</a> because the form looks really nice like a credit card form.