June 12, 2012 at 10:17 pm #email@example.comMember
Hello, I’ve seen various topics similar to this on the board but am just not finding the answer I need. When someone checks out on my site using the wp eStore plugin and Authorize.net, they are taken to the Authorize.net page and able to successfully enter their info. The repsonse that is returned is:
“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.”
I’ve setup a valid Return URL per many of the other replies and enabled debugging. After enabling debugging, I attempted again and go the same response from Authorize.net. These were my details in the debug file:
[06/12/2012 10:06 PM] – SUCCESS :Handling payment data from: authorize
[06/12/2012 10:06 PM] – SUCCESS :Retrieving order details… Key: xxxxxxxxxxxxxx Gateway: authorize
[06/12/2012 10:06 PM] – SUCCESS :Retrieved Item Details: 7|Test|1|1||ip=184.108.40.206
[06/12/2012 10:06 PM] – SUCCESS :Order Received… verifying payment data.
[06/12/2012 10:06 PM] – SUCCESS :Performing post payment processing tasks.
So it looks like everything is successful. Why am I still getting that response?June 12, 2012 at 11:21 pm #46123adminKeymaster
Is that the full debug data from the “eStore_post_payment_debug.log” file?
Try the tweak mentioned in the following page:
Most Common Causes…
This error usually happens for one of the following reasons:
i) The return URL value you have specified in eStore has a typo and it is resulting in a 404 error.
ii) The correct relay response URL need to be specified in your authorize.net merchant profile. So make sure there is no type in that URL and you can access this URL freely (if it is behind a password protection then it won’t work).
iii) Authorize.net failed to send the payment notification to your server (example causes: server’s firewall blocked it, your server didn’t reply with the usual “OK” message).
Authorize.net also has an article explaining why this happens:
Here is a link to another post where another user had this same error:
- You must be logged in to reply to this topic.