3 ms·
This is the reason why I don't like doing any client side validation of card data (beyond the basic check for empty fields). I would much rather incur a 2-3sec
by ux-app 14y ago
This is the reason why I don't like doing any client side validation of card data (beyond the basic check for empty fields).
I would much rather incur a 2-3sec browser roundtrip by posting raw payment details to my bank/gateway and allowing them to do the validation (they're presumably much better at it than I am).
Doing client side validation is too error prone, and considering that accepting card data is done so rarely, the (minimal) performance gain of JS validation isn't worth the risk of rejecting good data by accident.
- alttab 14y agoYou, but whatabout a laymen user who doesnt care ehat your justifications are? They want people to build snappy mobile web apps. This creates competition and legitimacy for them
- ux-app 14y agoNot really sure what point you're making. Validating on the server will incur a 2-10sec penalty once when entering payment data... the rest of your app is unaffected.
- reaclmbs 14y agoYou have to pay for failed authorization attempts