QuickTip Sundays: Not Allowing Dashes In Credit Card Numbers
Take the extra 15 minutes with the developers and write a regular expression to take out the dashes and spaces
Somewhere in America, there’s a product manager or client talking to a programmer, and the programmer is telling them, “Yo, it’s going to take an extra day or so to make it so the users can enter in credit card numbers with dashes. Let’s just put in a help message telling them they can’t do it.”
And that client is saying, “Uh, sure. It must be really hard.”
Developers say all sorts of things, and this has to be one of the most insane comments. That’s like saying at a cash register, “You can only use the card this way, and if you don’t, we won’t take your money.”
As bad as conversion rates are, this is one of the worst reasons to limit them. How prevalent is it? There’s a Hall of Shame dedicated to it.
Write the regular expression.
Anything that limits the user from completing a form means less revenue, and less revenue means less pay for anyone. Conversion is sometimes about the little details, and this is one of them.
$99 Tough Love Resume and Portfolio Review
Tough love. Great Advice. Receive an one hour portfolio review and career coaching session online, or in person if you're in Seattle.
Other Posts On Usability Counts
- QuickTip Sundays: CNN, Google And Business Needs Getting In The Way Of User Needs
- How Much Should Designers Ask About The Business Model?
- QuickTip Sundays: Sharepoint Blogs
- Recessions Are A Perfect Time To Rethink Application Usability
- MySpace Mondays: You Want Your Applications To Be Viral? Design Great Applications.