Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Some fancy websites show an error dialog when it is detected that an untrained shopper has entered a credit/debit card number as it is printed on their card with spaces. Is it possible in some way to write a Java web app that handles these numbers with spaces as if they were correct?
My view is that any Web app that rejects a credit card number with spaces isn’t doing its job. When you receive a credit card number, it’s easy enough to do:
to remove spaces and dashes (some use those too). Then validate the result. You’ll simply annoy your users if you force them to remove spaces you could just as easily do.
As for how to validate, well that depends on a lot of things, such as which Web framework you’re using and what validation options you’ve chosen. Struts 1 for example might or might not use Apache Commons Validator whereas Spring MVC will (probably) use Spring validation and so on. So I can’t tell you exactly how to validate but I can tell you what to validate.
The first thing is that a CC number with spaces should not be rejected. Most people will find:
much easier to read than:
which is really important if the user misses or mistypes a digit and needs to find why his or her credit card number failed validation. The replaceAll() at the top of this post covers this situation.
The second thing is that you display the credit card number (even when some of the digits are replaced with X for security reasons) in the correct way. I suggest you read through Anatomy of Credit Card Numbers.
That page gives you the rules for the number of digits and the valid prefixes. A robust Web application will implement these so you can tell if a credit card number is invalid before you try and use it. It can take up to 30 seconds (or possibly more) to submit credit card details to a payment gateway so you shouldn’t do it until you are sure as you can be that the payment will be accepted. To do otherwise is to provide a really bad user experience. There is every chance the user will give up if it fails 1-2 times rather than wait.
As for displaying them, that depends on the # of digits:
The credit card number should be verified according to the checksum algorithm mentioned in the page before submitting for processing as part of a standard validation routine. That page has a Java implementation of that routine.
Every website that accepts credit card payment should be doing all of the above as an absolute minimum or you’re simply throwing away business as a percentage of your users get frustrated.
So the short version is two simple rules: