Live data from Hacker News

Why is this shameful practice so common?

unixwiz.net

1–10 of 40 posts

Re: Why is this shameful practice so common?

#2
I've often wondered this myself, however, I have also thought about it from the opposite angle.

There are many sites that give no instruction as to how we are supposed to enter our credit card info. One can assume two possibilities: 1) The programmer of the site was ready, willing and able to parse multiple input types and simply strip out spaces, dashes, etc, or 2) I'm going to enter my credit card number into this page in a fashion not expected by said programmer and my much coveted Scarface Special Edition DVD will never show up at my door...

Just tell me what format you want so I can have some peace of mind and not have to decide which method is the best.

Re: Why is this shameful practice so common?

#3
Prompting the user e.g. ("no spaces") is a nice cue of the same fashion as an asterisk (*) for required form fields - both reduce user frustration.

However, it would be nice to think that we could automagically correct spaces/dashes etc. in CC numbers and transition directly to a confirmation page.

I wonder if translation of CC numbers is verboten by any payment gateways?

Re: Why is this shameful practice so common?

#4
post #3

Prompting the user e.g. ("no spaces") is a nice cue of the same fashion as an asterisk (*) for required form fields - both reduce user frustration. However, it would be nice to think that we could automagically correct spaces/dashes etc. in CC numbers and transition directly to a confirmation page. I wonder if translation of CC numbers is verboten by any payment gateways?

The payment gateway software I've interfaced with is very specific about what formats it accepts. There's an xsd schema for it. Basically just numbers. The gateway still does a lot of validation and will throw all sorts of errors on insufficiently cleaned up data.

Re: Why is this shameful practice so common?

#6
post #3

Prompting the user e.g. ("no spaces") is a nice cue of the same fashion as an asterisk (*) for required form fields - both reduce user frustration. However, it would be nice to think that we could automagically correct spaces/dashes etc. in CC numbers and transition directly to a confirmation page. I wonder if translation of CC numbers is verboten by any payment gateways?

The payment gateway software I've interfaced with is very specific about what formats it accepts. There's an xsd schema for it. Basically just numbers. The gateway still does a lot of validation and will throw all sorts of errors on insufficiently cleaned up data.

But your application server can strip out spaces and dashes before you send the number to the gateway. Right?

Re: Why is this shameful practice so common?

#7

Earlier quoted context omitted.

The payment gateway software I've interfaced with is very specific about what formats it accepts. There's an xsd schema for it. Basically just numbers. The gateway still does a lot of validation and will throw all sorts of errors on insufficiently cleaned up data.

But your application server can strip out spaces and dashes before you send the number to the gateway. Right?

Of course - We do it.

Wondering if anyone uses a payment gateway which prohibits this..

Re: Why is this shameful practice so common?

#9
I think it's just a case of programmers thinking like programmers and not like users. They think "I want this to not have numbers or spaces, so why would I let the user put in numbers and spaces?"

You see errors like that everywhere you look on the web, though much more at big corporations than at startups. Startups tend to eat their own dogfood, which greatly reduces that, though not entirely.

Post reply on HN