61–70 of 112 posts
I can't stand credit card forms that split the credit card number into 4 inputs ("[XXXX] [XXXX] [XXXX] [XXXX]") because I can't paste my number in (the first box has a maxlength of 4 usually)
Yet, for people who are typing in the number (vs pasting it), the 4 sections makes it easier.
This form is the best of both worlds.
Earlier quoted context omitted.
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 review…
"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.
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.)
I'd make the expiration dates text fields. Having to scroll through a list of numbers in a drop-down is a pain.
What browser/OS doesn't let you type to select in dropdowns?
However, if you are going to claim that it has 'Accurate Card Type Detection', you need to make sure that you cover common cases.
E.g. I live in NY and my Amex starts with 3723 and the input form doesn't recognize it.
As a developer, I understand that there are bugs in software. But if you are selling me a component which can not handle my own card, I would really wonder how comprehensive your card type detection is. They link to this page http://en.wikipedia.org/wiki/List_of_Issuer_Identification_N... which lists 37 as a valid Amex number. I think they need to go through their code and make sure all those numbers are handled correctly.
i start typing in a known prefix for master card
514101
and after i type the `0` the cursor (for who knows what reason) jumps to before the 0 and i end up with
5141 10
(note the 0 and 1 swapped)
works fine in firefox; breaks in chromium