The transaction flow is this:
First, you add something to your cart, and go through checkout. At the final Confirmation page on your site, you click the Confirm button, and you are redirected to the Authorize.net site.
Before sending you over to the Authorize.net site, this log file is generated, simply to record the details being submitted for the transaction. Hence the notation "Sent to Authorize.net:".
indy1725:
Checking in the cache folder, I find the new SIM_debug log, which reads thus:
"Nov-07-2010 08:53:30
Sent to Authorizenet: Array
(
[x_login] => *******
[x_amount] => 23.57
[x_version] => 3.1
[x_method] => CC
[x_type] => AUTH_CAPTURE
[x_cust_ID] => 33
[x_email_customer] => TRUE
[x_company] => Home
[x_first_name] => ******
[x_last_name] => ******
[x_address] => ******
[x_city] => ******
[x_state] => ******
[x_zip] => ******
[x_country] => United States
[x_phone] => ******
[x_fax] =>
[x_email] => ******
[x_ship_to_company] => Home
[x_ship_to_first_name] => ******
[x_ship_to_last_name] => ******
[x_ship_to_address] => ******
[x_ship_to_city] => ******
[x_ship_to_state] => ******
[x_ship_to_zip] => ******
[x_ship_to_country] => United States
[x_Customer_IP] => 24.20.44.193
[x_relay_response] => TRUE
[x_relay_URL] => ********/store-zen/index.php?main_page=checkout_process&action=confirm
[x_invoice_num] =>
[x_duplicate_window] => 120
[x_allow_partial_Auth] => FALSE
[x_description] => Website Purchase from Lunarbistro.com
[x_fp_sequence] => 22
[x_fp_timestamp] => 1289192010
[x_fp_hash] => 4c70e828cca7cfd88a8678b261c89167
[x_show_form] => PAYMENT_FORM
[x_receipt_link_method] => POST
[x_receipt_link_text] => Click here to complete your order.
[x_receipt_link_url] => ********/store-zen/index.php?main_page=checkout_process
[x_Test_Request] => TRUE
[zenid] => jv7ouf4pbkh64n5g8bj32c5i47
[url] => https://secure.authorize.net/gateway/transact.dll
)
Then ...
indy1725:
Using the test-Mastercard number provided by the module, I click Submit, and am brought to a page which reads only:
"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."
Normally if there are no communications problems with Authorize.net reaching your store to tell it of the completed payment (which happens by virtue of the URL you mentioned in the log file, and below), then you will be taken to the checkout_success screen of your site, after a moment of processing the returned response received by your store.
Instead, you're receiving a message which indicates that Authorize.net couldn't confirm that your store would acknowledge their payment notice. Thus they display the error message.
This problem is explained on the Authorize.net website and also in our FAQs here: https://www.zen-cart.com/tutorials/index.php?article=402
indy1725:
No order is generated at my store, however the receipt is emailed to me.
Naturally. Your store never received confirmation of the payment. Thus it has no order to generate.
However, since Authorize.net already accepted and authorized the payment before that earlier problem occurred, they still send out their own payment notice message as they normally do.
indy1725:
When I go to the 'x_relay_URL' in the SIM-debug report, I see the shopping cart page of my site, with the error message: "There has been an error processing your credit card. Please try again."
When I go to the 'x_receipt_link_url' in the SIM-debug report, I see the same.To be expected. The link only "works" if there is also returned data coming along with the visit to that link, which of course you don't have when using your browser to test it.
indy1725:
When I go to the 'url' at the bottom of the SIM-debug report, I see a page which says only:
"The following errors have occurred.
(13) The merchant login ID or password is invalid or the account is inactive."
That's to be expected, since you're only visiting their entry-point URL which can only process something if valid transaction data is being passed, which you're not doing when you're just putting that URL in your browser.> indy1725:
After viewing that page, a second SIM-debug file is generated, with this content:
"Nov-07-2010 08:59:30
Response Code: .
Response Text:
Results Received back from Authorizenet: Array
(
[HashValidationValue] => B9A2099503DACCA8B568E23D852986E0
[HashMatchStatus] => FAIL
[url] => https://secure.authorize.net/gateway/transact.dll
)
"In this case you're getting no usable data. The HashValidationValue is calculated from the returned data (which is blank), and thus the HashMatchStatus will certainly be FAIL because there's nothing to compare it to.
indy1725:
it looks like the whole thing is being triggered by a hashMatchStatus failure.
No. As I said above, that's a symptom caused by the lack of data received.
In short, your problem is that your site is not responding correctly when Authorize.net redirects the customer back to your store.
As per the FAQ, that can be caused by many kinds of things, including but not limited to bad .htaccess redirect rules, so-called SEO mods breaking proper functionality, bad return URLs, very slow webserver, broken sessions/cookies, and the list goes on.
