Hacker News Reader

Comment by maccman | Hacker News Reader

Looks good, and I like the mistakes and solutions section.

However, it's pretty much all covered by Stripe's open source jQuery.payment, which is also agnostic to your payment gateway.

https://github.com/stripe/jquery.payment

(Disclaimer - I built it.)

View on HN

The presentation of Creditcard.js is great in terms of styling, and I'm sure the practical example goes a long way in selling something like this to non-developer decision makers. This is probably the market they are aiming for.

Personally, I would much rather use the MIT-licensed jQuery.payment by Stripe. I think $300 or even $149 is prohibitively expensive, and would prefer a script that is actively used and reviewed in public by many developers.

Thanks Alex!

Agreed. I wouldn't be opposed to paying $150 for a form that would take me a while to build, but there's already a lot of good open-source solutions for card inputs.

"prohibitively expensive" ?

Surely if you're a business of any merit – making even $500/month – $300 for a javascript library that'll remove bumps in the checkout process is worth it?

I fail to see why this cannot co-exist alongside the Stripe alternative library. Heck, just taking the stripe library and offering commercial grade support, and charging $300 seems like a pretty good business.

Try checking out -- they're are still plenty of bumps in their checkout process...

Can you explain how commercial-grade support for a library that hasn't been tested by many people is better than a community of people who have run and tested a library? What exactly are they going to do for the support?

I'd also argue that a library developed and used by Stripe is pretty commercial grade too.

>I fail to see why this cannot co-exist alongside the Stripe alternative library.

It certainly can, anyone is more than welcome to pay for something done by open source software available for free.

>Surely if you're a business of any merit

Just because you're a business doesn't mean you should pay for things that you can do cheaper.

The point is that a decent web developer could recreate that form in 20 minutes with jquery.payment and a little bit of CSS, so why should you pay $300 for the same thing?

Thinking price point, 300 is about a couple of hour's worth of work which they save your developers. Not a big deal.

And you have a similar UI widget at

https://stripe.com/docs/checkout

Lol, that looks exactly the same to me!

It's pretty hard to make the most minimal form look any different.

From the initial docs of jQuery.payment, it looks like a lower-level tool -- the OP provides the promise of "you just drop it in, and you get these things, designed for you." jQuery.payment looks like "Here's a toolset you can use to do whatever you want!"

But I don't want to spend time figuring out what I want and putting it together. I also don't want to spend $150/year on it though. :)

If you built a higher-level abstraction on top of jQuery.payment, that made the good design choices for the developer, so the developer could just 'insert form here'....

You guys at Stripe are amazing. I love you guys.

Reply on news.ycombinator.com