Authorize.net AIM module passing billing names, not cardholder name

[David R]

Authorize.net AIM looks for a First name and Last name as separate submitted fields.

The checkout pages are presenting a single complete cardholder name entry field, and passing the result to the authorizenet_aim.php module. (authorizenet_aim_cc_owner)

It gets used in different places, but it's not submitted to Authorize.net.
Instead, the order billing first and last name fields are passed.

So if "Jane" "Smith" places an order, and uses Mike Smith's credit card to pay, Jane will enter "Mike Smith" during checkout, but what will be sent to Authorize.net as the cardholder name is "Jane" first name and "Smith" last name.

'x_first_name' => $order->billing['firstname'],
'x_last_name' => $order->billing['lastname'],

Is there a reason it is being done this way, instead of capturing first and last names for the cc owner during checkout and passing them through?

Before I muck with something that has been around for years now, I thought I should ask for some guidance.

Thanks!

[carlwhat]

i always find the splitting of names problematic....

with regards to this specific situation, the interesting thing is that it looks the cc_owner is getting populated as well as validated. i suppose the easiest thing would present code such as this as the start of the before_process function:

$order->info['cc_owner']   = $_POST['cc_owner'];

$parts = explode(" ", $order->info['cc_owner']);
$lastname = array_pop($parts);
$firstname = implode(" ", $parts);

you can then use the $firstname and $lastname variables later in the function. note that firstname will contain everything but the last word in cc_owner. and last name will contain the last word.

as to why the code is the way it is, your guess is as good as mine. but clearly, it does not look correct as you have accurately pointed out.

[David R]

Thanks for taking the time to look at it. I think you're right. The beauty of Zen Cart is that it is so accessible.