3 ms·
If at any point in the process they need to bill you for something, they have to ask for your first and last name because that's exactly what the credit card co
by jhall1468 11y ago
If at any point in the process they need to bill you for something, they have to ask for your first and last name because that's exactly what the credit card companies require. So there are use cases.
Personally, I don't see why any company is asking for a name if they aren't billing you for something or they aren't a social network.
- lostlogin 11y agoI've had a Google, but can't find Zuckerbergs answer to this. Any idea?
- takno 11y agoI've never seen a credit card company ask for separate first and last names.
- jhall1468 11y agoSometimes I think Hacker News forgets the world doesn't start with LA and end with Miami. http://developer.authorize.net/api/reference/ http://developer.authorize.net/api/reference/ firstName First name associated with customer’s billing address. Required only when using a European Payment Processor.
- gnaritas 11y ago> they have to ask for your first and last name because that's exactly what the credit card companies require No they don't, they ask for a single field, name on card which is a single string containing everything on the card.
- jhall1468 11y agoSometimes I think Hacker News forgets the world doesn't start with LA and end with Miami. http://developer.authorize.net/api/reference/ http://developer.authorize.net/api/reference/ firstName First name associated with customer’s billing address. Required only when using a European Payment Processor.
- Marazan 11y agoNo they don't, they ask for the full name on the card in a single free text field.
- jhall1468 11y agoSometimes I think Hacker News forgets the world doesn't start with LA and end with Miami. http://developer.authorize.net/api/reference/ http://developer.authorize.net/api/reference/ firstName First name associated with customer’s billing address. Required only when using a European Payment Processor.
- zimpenfish 11y agoThat would require the user information to exactly match the credit card information - which is dumb because it blocks a whole swathe of use cases (multiple payment methods, different person paying, paying by Paypal, paying by Apple Pay, etc.)