Creditcard.js: a more usable credit card form
91–100 of 112 posts
Re: Creditcard.js: a more usable credit card form
#92Earlier quoted context omitted.
We built some custom inputs just for handling number formatting (currency, percentages and separators) using AngularJS (directives) and I can say from experience it is much harder than anyone would imagine. The basic concepts are simple, it's always the implementation details, edge cases, browser quirks that will eat up your time. Bottom line, saving money vs. time isn't a good reason not to buy this. I still wouldn'…
Skeuocard ( http://kenkeiter.com/skeuocard/ ) was on the top page of HN a couple of months ago.
Re: Creditcard.js: a more usable credit card form
#93A mix of bugs and suggestions: - It is possible for the security code and card number fields to be green, indicating they have been filled out correctly, using a 3-digit security code for an American Express card number or a 4-digit security code for any other card number. - The security code help probably should not display the American Express case when no card type has been identified. - The security code field sh…
Click on security code question mark, then change type of the card - two "cards" appear for a second on the right than the old one disappears.
Re: Creditcard.js: a more usable credit card form
#94$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.
EDIT: Also, if anyone needs help with jCCV, get in touch at @PawelDecowski.
Re: Creditcard.js: a more usable credit card form
#95Re: Creditcard.js: a more usable credit card form
#96Earlier quoted context omitted.
We built some custom inputs just for handling number formatting (currency, percentages and separators) using AngularJS (directives) and I can say from experience it is much harder than anyone would imagine. The basic concepts are simple, it's always the implementation details, edge cases, browser quirks that will eat up your time. Bottom line, saving money vs. time isn't a good reason not to buy this. I still wouldn'…
OSS and credit cards have existed for every single day of the last ten years. Did the community just not notice that taking credit cards on websites is done by substantially every business transacting on the Internet? Or were they just hiding their well-tested well-designed decent-UX commercially-supported OSS options on localhost until someone tried to commercialize the niche, to now be unleashed on Github with grea…
I guess the marketing of the JS library would make a real difference: aim for management rather than developers?
Re: Creditcard.js: a more usable credit card form
#97A mix of bugs and suggestions: - It is possible for the security code and card number fields to be green, indicating they have been filled out correctly, using a 3-digit security code for an American Express card number or a 4-digit security code for any other card number. - The security code help probably should not display the American Express case when no card type has been identified. - The security code field sh…
Re: Creditcard.js: a more usable credit card form
#98Earlier quoted context omitted.
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…
If I was having a successful business that is doing $100k+/year I would think twice about integrating a new form with minified javascript from a cold email into my payment flow. It's definitely not a bad idea to do outbound marketing for this. I just think conversions would be a lot higher if the readable source is also present in the offer.
Re: Creditcard.js: a more usable credit card form
#99> 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.
Re: Creditcard.js: a more usable credit card form
#100Earlier quoted context omitted.
You'd be surprised how many people don't know how to tab through multiple fields. If the expiration date is broken into multiple text fields that creates more work as "regular" users need to switch between keyboard and mouse repeatedly.
How does it create more work? What do you mean switching between keyboard and mouse repeatedly? Aren't they already doing that when they are entering in the credit card number, the security code AND their name? LOL.
Seriously though, what makes you think people have to "scroll" through 11 months to get to December? 12 options can be comfortably displayed all at once on screen. Have you ever seen a dropdown?