Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Authorize.net (SIM) Payment Confirmation - Fails to return to cart


isidbos

Recommended Posts

Hi All --

 

I need a bit of help with the Authorize.net SIM payment module integration.  I think I have it properly configured, but there is a problem...

 

After completing the payment process on the Authorize.net website, the system fails to return to the cart, and instead immediately gives the error

 

An error occurred while trying to report this transaction to the merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card.

      This transaction has been approved.
It is advisable for you to contact the merchant to verify that you will receive the product or service.

 

 

Current settings include:

OSCommerce 2.3.4

Authorize.net Server Integration Method (SIM) [Test] v2.0

Have synchronized my Auth.net account and OSCommerce systems to use API 3.1, login ID, transaction key, and MD5 hash.

Pointed to the live server at Authorize.net

Set to use the 'Test Mode' for Authorize.net (no charges actually applied)

 

The error is so immediate, I'd be leaning towards a timestamp problem, but I've checked that, and the value is x_FP_Timestamp is correct.

 

I'm not sure what else to look into, except maybe an SSL issue.  Right now, the site is NOT on SSL, and, of course, Authorize.net is.  There's a minor note in the documentation that some issue with mixed SSL sites was fixed back in June 2014, but maybe it is still present....  Otherwise, I have no idea what I should do to get this working. 

 

Any help is appreciated.

Link to comment
Share on other sites

OK, some progress.

 

1) I can remove the error above by removing the realms authentication for the folder in which the cart exists.  (I had the realms on to try and prevent Google and other engines from linking to the cart before it was actually ready to use.)  Requiring a name & password to access the website shopping cart folder certainly blocks the relay response from Authorize.net.

 

2) Now we move on to yet another problem.  All orders with Authorize.net payments now give the error message
 

 

"There has been an error processing your credit card
The credit card transaction could not be verified with this order. Please try again and if problems persist, please try another payment method."

 

 

This happens regardless of the actual transaction approval or not.  I've tried this with TEST MODE = ON and TEST MODE = OFF, and still see the same error message from OSCommerce.  At least when I do it as a live transaction, I get to see what Authorize.net thinks about the transaction, and it thinks the transaction was APPROVED, but OSCommerce seems to know nothing about that at all.

 

Any ideas on how to fix this problem?  Or troubleshoot it?

Link to comment
Share on other sites

OK, further updates from the automated Emails I'm getting.  For every transaction on Auth.net, I got an "Authorize.net SIM Debug E-Mail" which uniformly show
 

 

$HTTP_POST_VARS:

Array
(
    [x_response_code] => 1
    [x_response_reason_code] => 1
    [x_response_reason_text] => (TESTMODE) This transaction has been approved.
    [x_avs_code] => P
    [x_auth_code] => 000000
    [x_trans_id] => 0
    [x_method] => CC

...

 

 

This is coming from the OScommerce system, so it's pretty clear that the cart knows the transaction is approved (and I get a customer recipet for each of these as well).  So, is the website behvior expected when using the 'Test Mode', or is there some problem with the way the module is working?

 

As a side note, I was able to go through the purchase process with the PayPal Express module set to use the PayPal sandbox, and it worked properly - the OSCommerce site  shows the correct 'thank you' message and the email receipt gets sent as well.  So, showing an error is not necessarily part of using a testing payment server.

 

Still looking for confirmation that this OSCommerce is working as expected or if not some ideas on how to fix it.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...