Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Authorize.net ADC and the new checkout process


Guest

Recommended Posts

I am having trouble getting the Authorize.net ADC Connection to work with the new checkout procedure. I have carefully upgrade the new authorizenet.php file so that it includes your modifications in the new file. Also, I have made sure to add the ADC lines in the new checkout_process.php file. However, I am getting a strange error (really, no error at all).

 

I get to the checkout_confirmation.php page successfully. The credit card has been accepted by the js functions on the payment page and we are ready to submit the order. The confirmation page shows the delivery information, billing information, products, totals and payment information, including the card and exp. date. When I press on "Submit" it returns the same page (without any errors) and the only thing that is different is the Payment Information (including cc card, etc.) are gone.

 

Do you know how I can debug this? Or am I missing something obvious?

 

Thanks in advance!

Zac Smith

Link to comment
Share on other sites

Hi Zac Smith,

 

Let me clarify the problem again, so you are being redirected to the checkout_confirmation.php page when you click on the 'Submit' order button ? You should have been redirected to checkout_payment.php if there is any error occur.

 

Did you replace your file catalog/includes/modules/payment/authorizenet.php to from my contribution file catalog/includes/modules/payment/authorizenet.php ? If you manually make changes, please make sure you have changed this.

 

$this->form_action_url = 'https://secure.authorize.net/gateway/transact.dll';

 

change to

 

$this->form_action_url = tep_href_link(FILENAME_CHECKOUT_PROCESS, '', 'SSL', false);

 

This should solve your problem. If it does not, can you send me the link so that I can take a look at ?

 

Regards,

Bn

Link to comment
Share on other sites

Bao,

 

Thanks for your feedback. I found that the <form> tag had been altered. This was not a problem with the OSC update but one of my own.

 

The module is working great now with the new order process.

 

Thanks!

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...