News for hackers. Stuff that matters.
Re:Why is this shameful practice so common? by astrec on Monday May 12, 2008 @12:20AM (#187275)
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? by LogicHoleFlaw on Monday May 12, 2008 @12:51AM (#187294)
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? by RyanGWU82 on Monday May 12, 2008 @01:30AM (#187307)
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? by astrec on Monday May 12, 2008 @02:09AM (#187323)
Of course - We do it.

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

Re:Why is this shameful practice so common? by allenbrunson on Monday May 12, 2008 @03:14AM (#187366)
how could they possibly even know you've already stripped out non-numeric characters?
Re:Why is this shameful practice so common? by astrec on Monday May 12, 2008 @09:30AM (#187544)
Audit. Our code is audited and certified by a security firm contracted by our merchant service provider (read bank). They don't have any such anti-transformation provision, but I'm curious to know if any payment gateway does.