Live data from Hacker News

Creditcard.js: a more usable credit card form

creditcardjs.com

11–20 of 112 posts

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

#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?

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

#15
You minified half of the Closure Library for a modest product. 50kb of inline JS for card processing, just to obfuscate. This is terrible, you need two libraries doing the same thing.

Very high price point, developers who can afford to buy it can likely code it themselves.

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

#16
post #5
post #3

> Creditcard.js avoids these design mistakes, providing an HTML/CSS/JS solution compatible with any payment form. If it requires JS, then it isn't compatible with any payment form.

When JS is not available, this becomes a regular HTML form with inputs and selects.

Does not support 1Password, though

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

#20
Doesn't work under Chrome/Linux (older version 26.0.1410.63). The first group of digits in the card number field show up correctly, but then something goes wrong when the script tries to insert a space for formatting.

The first digit in the second block shows up correctly, but then the cursor is positioned before the first digit/second block, so that the remainder of the block gets inserted in front of the first digit, completely messing up the card number.

Post reply on HN