Tips and Tricks HQ Support Portal › Forums › WP eStore Forum › WP eStore Troubleshooting › eStore- after checkout with authorize.net get Error: this trans can not be accep
- This topic has 11 replies, 4 voices, and was last updated 12 years, 5 months ago by admin.
-
AuthorPosts
-
June 20, 2012 at 9:48 pm #6624kpaullMember
Using authorize.net once form is filled out and submitted the following error occurs, BUT credit card is billed and thank you email is sent?!
Error:
This transaction cannot be accepted
Also, “this page has insecure content” is shown while using Chrome browser.
This page worked in the past, began not working after Premise plugin was added. Deactivated Premise and still have a problem.
page link: [http://directlysuccessful.com/hire-me/]
other “shop” page has been set to private for now.
thanks in advance for any help!
Kelly
June 20, 2012 at 11:24 pm #46306PeterMemberPlease see this post which might explain why you’re seeing this problem:
https://support.tipsandtricks-hq.com/forums/topic/authorizenet-error-99
June 20, 2012 at 11:42 pm #46307Surfsupjoe125MemberHi Peter,
I have this same thing going on as well. I posted to the forum. It is really strange. I am working with A.net trying from that end as well. The transaction goes through but instead of the customer seeing the “thank you page” configured in estore settings, it goes to blank page with the error. The response/receipt URL is correct but it does not get called up.
Pullin my hair out!!
June 21, 2012 at 12:11 am #46308adminKeymasterYou usually get the following error when you include static content using the “http” keyword on a secure page (HTTPS)
This page has insecure content
Are you using HTTPS pages? Do you have a plugin that doesn’t work with https? If a plugin doesn’t work with HTTPS page then it will add scripts using “http” and that will cause this error too.
June 21, 2012 at 12:15 am #46309adminKeymasterThe
"This transaction cannot be accepted"
error that you are seeing from authorize.net usually happens when you use an incorrect Transaction Key in your auth.net Gateway settings in the eStore. Please contact Authorize.Net for the API Login and Transaction Key. Then go to the auth.net settings area under the payment gateway settings tab of eStore and update the values and save the settings.June 21, 2012 at 12:46 am #46310Surfsupjoe125MemberHi Key Master,
Maybe i wasn’t clear. The transactions do post and clear. The funds are taken from the customer even though this error and blank page appear instead of the receipt/return URL path to the Thank you page. If the API and Trans key were invalid, incorrect, etc. the transaction would not process. Everything is doing exactly what it is suppose to with the exception of the Thank you page that is configured in estore and A.net not coming up to finish the transaction.
Any other ideas or suggestions?
Thanks
Joe
June 21, 2012 at 6:46 am #46311adminKeymasterHi Joe, That error is happening while you are still on the authorize.net site so they will be able to tell you exactly what is wrong. All I can tell you is that authorize.net checkout on a proper setup works fine with eStore.
Without the details form authorize.net I can only try to guess the most common causes that I have seen other users face with their site. Please check this list:
Do you have an exact error code for the error you see?
June 21, 2012 at 5:39 pm #46312kpaullMemberThe error that I see is this:
Error
Transaction can not be completed
The transaction DOES go through and the email is sent to the client.
I went in and re-set the url for a successful transaction in the eStore settings
then also reset in the a.net site the Response/Receipt settings and cleared cache (using Chrome)
The next transaction went through, took me to my Thank You page, but alerted to insecure web page, when I click load anyway, it took me back to the blank payment page with the Error Transaction can not be completed at the top??
Kelly
June 21, 2012 at 11:03 pm #46313Surfsupjoe125MemberHi Key master,
I ahve spoken with a.net again. They say that after the transaction the URL that is loaded in the settings for a successful transaction in estore is where the problem lies. So I checked the return URL value… the spelling is correct and the URL can be placed in a browser and work perfectly. Does the version of estore matter? Should it be upgraded? I am sure this is an easy fix but I can’t find it. Do you have folks that can be hired to look at things like this? We are falling horribly behind for other customers working on this. I just want someone familiar with estore and a.net to take a look. Any takers?
Thanks
June 21, 2012 at 11:28 pm #46314Surfsupjoe125MemberHello again,
I just spoke with a.net and I finally was told that if x_relay_response is set to FALSE
it will default to a.net receipt. Can anyone please direct me to the correct file so I can do this?
Any assistance would be greatly appreciated
Thank you
June 21, 2012 at 11:37 pm #46315adminKeymasterThat is something you set in your auth.net merchant account profile. I have sent you an email to get access and I will check everything up for you.
June 23, 2012 at 3:09 am #46316adminKeymasterThis turned out to be an issue with the improperly configured SSL page related issue explained here:
The “Thank You” page was using SSL (https) but had security warnings on it, so authorize.net was failing to redirect properly.
-
AuthorPosts
- You must be logged in to reply to this topic.