- This topic has 1 reply, 2 voices, and was last updated 8 years, 6 months ago by .
Viewing 2 posts - 1 through 2 (of 2 total)
Viewing 2 posts - 1 through 2 (of 2 total)
- You must be logged in to reply to this topic.
Support site for Tips and Tricks HQ premium products
by
Tips and Tricks HQ Support Portal › Forums › WP eStore Forum › WP eStore Troubleshooting › Paypal is highjacking authorize.net checkout
Tagged: authorize.net
a) What part of the product isn’t working? The checkout process for Authorize.net
b) What are you trying to achieve? – I want customers to be able to use authorize.net as the gateway for processing credit cards
c) What causes the error to show up? – Selecting “proceed to checkout” for authorize.net option
d) What version of the plugin are you using? – Version v7.1.9
e) Provide a link to the exact page where the problem is seen – [http://thoruptutoring.com/make-a-payment/]
f) Which product you are using (example: eStore, WP Affiliate Platform, eMember, PDF Stamper etc…)? WP eStore
g) Did you modify the plugin code? – Not to my knowledge. I just repurchased the plugin so I could have access to this forum to figure this out as the previous web developer did not forward the purchase details to the client.
I review solutions in these two threads – one included no solution https://support.tipsandtricks-hq.com/forums/topic/estore-using-single-payment-gateway-authorizenet-but-customer-used-paypal#post-79496 and one did not work for me: https://support.tipsandtricks-hq.com/forums/topic/how-to-use-gateway-specific-buy-now-type-buttons
Hi, Authorize.net is showing this error when I go to payment page:
(14) The referrer, relay response or receipt link URL is invalid.
This is an issue with your authorize.net setup. Please take a look at this post which has some solutions to this issue:
https://support.tipsandtricks-hq.com/forums/topic/e-store-not-working-with-authorizenet
Please make sure to load a fresh new copy of eStore also:
https://support.tipsandtricks-hq.com/forums/topic/re-install-or-load-a-fresh-build-of-the-plugins
Clear your browser cache and then do a test after that and let me know if the same issue is still there.