4 ms·
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
by astrec 18y ago
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?
- LogicHoleFlaw 18y agoThe 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.
- RyanGWU82 18y agoBut your application server can strip out spaces and dashes before you send the number to the gateway. Right?
- astrec 18y agoOf course - We do it. Wondering if anyone uses a payment gateway which prohibits this..
- allenbrunson 18y agohow could they possibly even know you've already stripped out non-numeric characters?
- astrec 18y agoAudit. 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.