51–60 of 112 posts
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.
For a simpler, open-source alternative, check out Skeuocard [1], I believe it was posted on HN previously. [1] http://kenkeiter.com/skeuocard/ Edit: here's the original post - https://news.ycombinator.com/item?id=6143604
To put the price in perspective, HighCharts, an extremely complex charting library, only charges $90 for a single website license.
I'd make the expiration dates text fields. Having to scroll through a list of numbers in a drop-down is a pain.
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.
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.)
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…
Who pays to beta test software ?
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.)
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…
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.