authorize.net transaction cannot be accepted

Now I'm trying to get the checkout to work with authorize.net but as soon as I get to the printscreen attachment and press the Process Payment button, I immediately get another screen as follows: https://secure.authorize.net/gateway/transact.dll

The following errors have occurred.

(103) This transaction cannot be accepted.

According to authorize.net support, they say I got the transaction key wrong, but I copy and pasted, and even tried typing in, and even changing the transaction key, and still no budge. I also got as far as modifying the following line of code in gateways.php (masking out the parameters):

// start gateway Authorize.Net
// start settings API Credentials
$WA_Authorize_Net_API_Credentials_TestMode = false;
if ($WA_Authorize_Net_API_Credentials_TestMode) {
$WA_Authorize_Net_API_Credentials_Login_ID = "525****GQ";
$WA_Authorize_Net_API_Credentials_Transaction_Key = "7S************NF";
$WA_Authorize_Net_API_Credentials_Merchant_Email = "pw******@************.com";
} else {
$WA_Authorize_Net_API_Credentials_Login_ID = "525****GQ";
$WA_Authorize_Net_API_Credentials_Transaction_Key = "7S************NF";
$WA_Authorize_Net_API_Credentials_Merchant_Email = "pw******@************.com";
}
// end settings API Credentials
// end gateway Authorize.Net

Can I get a copy of the confirm.php page to look at. I may be able to spot the problem.

attached as requested, wish to have been all finished by now, then to the look and feel of the site, etc...

Hi Ray, any chance have looked at this?

I verified that authorize.net AIM is already enabled and went to Payment Gateway Credentials visually verified that the transaction key is indeed the same as the one we copied and pasted when last requested key.

I tried setting $WA_Authorize_Net_API_Credentials_TestMode in gateways.php to true or false and still same thing. Debug mode is also already checked as well.

I just took a quick look at confirm.php in reference to the transaction key field:

<input id="x_login" name="x_login" type="hidden" value="<?php echo("".($WA_Authorize_Net_API_Credentials_Login_ID) .""); ?>" />
<input id="txnkey" name="txnkey" type="hidden" value="<?php echo("".($WA_Authorize_Net_API_Credentials_Transaction_Key) .""); ?>" />
<input id="x_fp_sequence" name="x_fp_sequence" type="hidden" value="<?php echo("".AuthNet_RandomID() .""); ?>" />

according to authorize.net, I'm seeing the following:
If you are using AIM, please make sure you are sending a valid Transaction Key along with your transaction request. The Transaction Key should be submitted using the field x_tran_key.

While I'm not so sure about the id="txnkey" part, am wondering if it should be "x_tran_key" instead.

As a further update, I tried to change all occurrences of txnkey to x_tran_key but that still didn't seem to work so I changed it back, am looking forward to updates as I should be around for the next few hours awaiting.

Hi Ray, for future reference, was needed to be fixed in the confirm.php page?

Hi Ray, I'm still curious what was causing my issue with the error message so we don't have to have this problem again when we do another shopping cart.

The hash hidden form element had: <?php echo([real code here]) ?> wrapped around the code that was already php. It may be a bug in the wizard, but I just had to remove that code wrapping the real code for it to work. I've logged a bug to look into this and test if we need to fix it for eCart.