Tips and Tricks HQ Support Portal › Forums › WP eStore Forum › WP eStore F.A.Q/Instructions › Authorize.net SIM – Most Common Causes of the "Thank You" Page Redirect Error
Tagged: authorize.net, authorize.net errors, relay response
- This topic has 0 replies, 1 voice, and was last updated 12 years, 3 months ago by admin.
-
AuthorPosts
-
June 21, 2012 at 6:44 am #6629adminKeymaster
Authorize.net is very picky about a few things (specially if you are not using HTTPS for your “Thank You” page).
Here is a list of other most common issues that triggers an error from authorize.net when it tries to redirect to the “Thank You” page after a payment.
Try the following tweak first
Open the “eStore_advanced_configs.php” file and find the following line:
define('WP_ESTORE_USE_AUTH_NET_ALT_REDIRECTION', '0');
Once you find it change it to the following:
define('WP_ESTORE_USE_AUTH_NET_ALT_REDIRECTION', '1');
Now do a transaction and you shouldn’t see that previous issue as authorize.net will do the redirection slightly differently (when the user clicks the button after the transaction).
Check the following if the above tweak doesn’t fix the issue
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 typo 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).
iv) You might have a problem caused by an invalid or improperly configured SSL certificate on your site. Thus, if Authorize.net is attempting to respond to your site and your site has problems in SSL mode, then Authorize.net will be encountering either an error message or delayed response and trigger this error.
v) You might have invalid rewrite rules set as a result of creating or adding an .htaccess file to rewrite URLs as part of so-called “seo” addons, or installed such an addon. Many times such addons fail to properly handle all returning responses from external systems properly, resulting in serious system problems.
vi) Your site is too slow in responding to Authorize.net’s attempt to return the customer to your site and/or send back transaction authorization to your site. Maximum 10 seconds is permitted. so if your site takes longer than 10 seconds to load then you need to address that first.
vii) Copy the value that you specified in authorize.net’s receipt default page field and paste it in the eStore’s “Return URL” field setting. Basically, match both these URL values.
-
AuthorPosts
- You must be logged in to reply to this topic.