Live data from Hacker News

Creditcard.js: a more usable credit card form

creditcardjs.com

21–30 of 112 posts

Re: Creditcard.js: a more usable credit card form

#21
post #13

$149 is a extremely high price-point for this with so many alternatives out there. I also don't see the value vs. the price. I've implemented http://jquerycreditcardvalidator.com/ with authorize.net with zero issues. Good luck selling this.

Demo doesn't show Amex but I presume it is supported?

If you're talking about jQuery Credit Card Validator, it supports Amex. https://github.com/PawelDecowski/jQuery-CreditCardValidator/...

Re: Creditcard.js: a more usable credit card form

#22
post #19

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.)

And you have a similar UI widget at

https://stripe.com/docs/checkout

Re: Creditcard.js: a more usable credit card form

#25
Typing 4321432143214321 results in 4321 3214 2143 1234 in Chrome. Works right if I type spaces, but I shouldn't need to do that. Also, let me type the expiration date in if I want to - I hate it when I can't complete a form by tabbing through fields.

Re: Creditcard.js: a more usable credit card form

#26

$149 is a extremely high price-point for this with so many alternatives out there. I also don't see the value vs. the price. I've implemented http://jquerycreditcardvalidator.com/ with authorize.net with zero issues. Good luck selling this.

It's $299 (that's the beta-price). But I don't think it's expensive. I think it's quite correct. If a developer value his time, he should probably buy it. That is if he finds that it has advantages over the free alternatives.

Re: Creditcard.js: a more usable credit card form

#27

I'd say that the ? for explaining the CCV should be a hover effect rather than a click. In every other CC form I've ever dealt with it's been a hover effect.

I have bad experience with the hover effect. Like showing up when I don't want it to show, and also it doesn't work quite well on tablets, phones and touch devices. I think the button is better approach.

Re: Creditcard.js: a more usable credit card form

#28
post #6

Interesting price point; it seems to be in a no-mans land where developers who can pay $300 would probably be in a position that they'd want to implement it themselves, yet it might be prohibitively expensive for smaller clients who'd better spend their efforts elsewhere and could use Skeuocard or Stripe.js for free. Surprised to see the 'one website' clause, as well -- as someone who spends a lot of time working wit…

I think it is probably the right move.

He has a way better chance of selling 100 licenses for $300 each versus 3000 licenses for $10 each.

The smart move would be to actually do some amount of outbound sales to sell licenses. There a ton of random vendors out there doing $100k+/year that have broken credit card flows. Find their checkout page, save it do disk. Spend 10 minutes integrating this verification into their own form, and cold-email the webmaster with the zip'd up demo and already done integration. Let's say it takes 6 hours to 40 of those. If 10% to convert, you're making serious money.

Re: Creditcard.js: a more usable credit card form

#29
"JavaScript libraries like jQuery aren't well equiped to handle form input, so Creditcard.js uses the more robust and comprehensive Google Closure Tools, the heavily tested JavaScript framework behind Gmail and Google Plus."

really? you're gonna do jQuery (+ all validation plugins) bashing for what? 5 fields + a luhn algo? please, take your snake oil elsewhere.

"the heavily tested JavaScript framework"? you must not follow jQuery's own pedantic development and testing, i would argue it is more heavily tested than Google's we-only-support-latest-2-versions-of-any-browser libs.

if anyone needs to do client-side cc pre-checks, there's a pretty up-to-date regex list [1] and a luhn implementation [2] which will get you 99.9% there. if you feel that the 0.1% (but probably much less) is worth a monthly licensing fee, you now have options :)

[1] https://github.com/Shopify/active_merchant/blob/master/lib/a...

[2] https://gist.github.com/ShirtlessKirk/2134376

Re: Creditcard.js: a more usable credit card form

#30
post #26

$149 is a extremely high price-point for this with so many alternatives out there. I also don't see the value vs. the price. I've implemented http://jquerycreditcardvalidator.com/ with authorize.net with zero issues. Good luck selling this.

It's $299 (that's the beta-price). But I don't think it's expensive. I think it's quite correct. If a developer value his time, he should probably buy it. That is if he finds that it has advantages over the free alternatives.

That's my point, there's not many advantages over an open source/free alternative (subjective). And it's contextual, there's no way I'm going to argue for my [insert superior here] at [insert agency, studio,etc here] to buy this when their tech savvy enough to seek other alternatives.
Post reply on HN