Description: ------------ The private method AuthorizeNet::_handleName() assumes the name is set as "firstName lastName" in the "name" property. This will easily break on first names that have spaces in them. I'll look deeper in the code for a better understanding of the "name" property but the assumption above is plain dangerous. I'll post a fix when I have one. -Philippe

I wouldn't exactly call this "dangerous". How common are two word first names and how would you possibly know which words comprise a first name and which ones make up the last name? eg. How would you decipher the following: Joseph C. Stump Joseph Carl Stump Mary Kate Olsen I think the real problem here is the AN asks for them as two fields instead of one. Have you seen AN fail on names not broken up properly? I guess I always assumed that AN was imploding f/lnames into a single string on their end. Might be worth an inquiry.

I see your point, and I know it's confusing from AuthorizeNet to ask for first and last names, when usually for a credit card, the customer is asked to put the name as printed on the credit card... Yes, probably will have to ask Authorize.Net some clarification on that... -Philippe

I am now using Payment_Process in production... This name split is not that dramatic of a problem with credit cards, but it could be with eCheck. Since we are not accepting eCheck at this moment, I can't tell you if this is a real issue. However, the name split on first space does cause some minor trouble when looking up transaction information on the Authorize.Net control panel. Case in point is people's who have their middle initial in their credit card name: i.e. John B Doe. An invoice administrator would have to look up the last name as "B Doe" which is counter-intuitive. All this being said, I am not sure if there is a 100% good solution to this problem. To be continued... -Philippe

Philippe, I've looked this over and decided that, as of now, there's nothing we can do about this. I've used AuthorizeNet in production since it came out for both eCheck and credit cards and haven't had any complaints from our invoice people here. I can see your point, but as we both agree it's difficult to implement a fix for this (we can thank Authorize.net for this). It's also interesting to note that AN doesn't even require a person's name according to their docs for a "minimum cc transaction via AIM".

Most merchants prompt their users for a single text value: "Cardholder name". How do merchants typically split this value into first and last name before submitting to AN?