X-Cart forums

[jharwood]

I'm just working on my first modifications with the v4 xcart (4.0.1) and want to make the checkout as simple as possible but there are additional customer first and last name fields in v4! Who wants to enter their name twice? At least in 99% of the cases I can think of, these fields are simply useless. Unless maybe someone stole a credit card and wants to give the real name first and then the billing name as the victim!

Anyway, can I get rid of one set of these fields without messing up the checkout or negating customer data that is really needed?

The results of testing orders through my gateway using a "test" first name and test card number yields odd results (iTransact). The "Personal Info" first name field seems to be used for the processing. At least, if it isn't correct (doesn't match my test first name in the gateway system) the order won't go through in test mode and it doesn't matter if it is entered correct in the Billing first name or in the Cardholder's name fields. The Personal Info name seems to take precedence.

Yet the Billing first name field passes the data (with the last name) to the Cardholder's name field. Thus I am curious if anyone else has learned a bit about this before I unleash the hounds! Or, maybe provide a good reason that xcart made the checkout in v4 even more complicated for the user.

Thanks
John

[pmstudios]

They may be useless fields most of the time, but other times there may be family members or friends who share cards, so the name of the cardholder will be different from the customer actually registering.

I'm not sure about which processor you're using, but I believe the name issue was fixed in a later version. You could always edit the processor file you use (example: payment/cc_verisign.php) and make sure the FIRSTNAME and LASTNAME use b_firstname and b_lastname by default.

You can disable profile fields or set those you don't require through General Settings > User Profile Options (from the quick tools dialog up top)

[jharwood]

That is about the only valid "need" for making a customer type in their name twice but it would come to play so very seldom. Seems like punishing the many for the few.

I'll definitely look into making any corrections needed in the processor file and then see if I can make the b_firstname/lastname data be used everywhere that the other fields are used so I can take them off of the ordering process.

I'll also see what kind of issues will arise with the mods I have made to date if I update the version.

Thanks
John