Earlier quoted context omitted.
That's a far cry from Make your credit card form better in one line of code and With one line of code.. $('form').card({ container: $('.card-wrapper') }); You get.. Animations for 4 different card types An intuitive experience for your users Pure CSS, HTML, and Javascript (no images) 100% free and open source Which certainly could be used by someone who doesn't understand all this. All I am saying is that for us as d…
If somebody who doesn't know what they're doing is writing a CC form, you've already lost. Making app development easier isn't "dangerous" because it allows less experienced people develop applications. You will always have people making mistakes and screwing up security, regardless of the actual ease of development. The more the developer has to do, the more they can screw up.
That doesn't mean the customer won't conclude it is legit, or that we don't conclude the same thing.
Recall that I had responded to,
>Looks gorgeous. I can't help but wonder if people unfamiliar with technology and ecommerce would be deterred by such a form?
Certainly I personally would be deterred (to an extent) from using this form without at least a cursory audit and verifying the identity of the person who wrote it.
This will naturally be less and less important the more eyeballs this sees. But as a simple tool, perhaps it is not that many.
Do remember that if I were wanting to get my hands on people's credit cards, getting developers to use this kind of script while having a well-hidden side channel (perhaps quite well-hidden - it could somehow encode cc details in the timing delays to a different server, potentially, so that it is not at all obvious that the delays even correspond with the data, it could just look like visualizations getting loaded as the person types) -- then this would be one of the more clever ways I could go about doing so.
I don't see how we're 'arguing' about this? We need to check what we are using, just like customers need to check that this is legit.