|
Yuan Yuan
|
February 1, 2017 at 2:47 pm
I am trying to set up an Event using the Authorize.net SIM plugin for payment on our new website (fordhamipinstitute.com), and am receiving an error 14 stating:
The following errors have occurred.
(14) The referrer, relay response or receipt link URL is invalid.
I spoke to two people at Authorize.net who helped troubleshoot the issue. We confirmed that the Authorize API login ID and Transaction Key are correct. They believe the issue has to do with Response/Receipt URLs. I updated the Default Receipt URL from one on our old website fordhaminconference.com/thankyou to our new site thank you page: http://fordhamipinstitute.com/thank-you. I tried to update the Default Relay Response URL from fordhaminconference.com/?page_id=674 to http://fordhamipinstitute.com/?page_id=0. However, the Authorize representative said we need to know what that number should be at the end of “?page_id=0” I tried both 0 and 674, but neither works. They suggested I look through the website pages in WordPress for anything related to Response/Receipt URLs, but I see nothing there. So they suggested we contact Event Espresso.
|
|
Josh
|
February 1, 2017 at 4:19 pm
Hi Nick,
You actually need to unset the Response/Receipt URLs in your Authorize.net account. The SIM add-on for EE4 will take care of setting those.
|
|
Yuan Yuan
|
February 2, 2017 at 8:24 am
Hi Josh,
I removed the links from the Response/Receipt URLs in mu Authorize.net account, and reattempted with no success. Please advise on next steps/additional troubleshooting.
Thanks,
Nick
|
|
Josh
|
February 2, 2017 at 8:40 am
Are you still getting the error that says:
The following errors have occurred.
(14) The referrer, relay response or receipt link URL is invalid.
Or is it a different error?
I can try using some of our sandbox credentials on your site and do a test payment if that works for you.
|
|
Yuan Yuan
|
February 2, 2017 at 9:10 am
Yes, I am still getting that error (14).
Please go ahead and run the test payment. Let me know if you need any additional info from me. Happy to discuss if that is helpful. Thank you!
|
|
Josh
|
February 2, 2017 at 9:34 am
OK the test transaction works when I use my Authnet Sandbox/Developer account.
https://www.evernote.com/shard/s4/sh/a9bbb9c6-979a-4fd5-8912-d80cfce520a3/143d4f4f8e82d462bd22c7ad25dffe98
Can you log into your Authnet account and double-check that no Response/Receipt URLs are set under Transaction Format Settings?
|
|
Yuan Yuan
|
February 2, 2017 at 9:44 am
Thank you for running the test. I wiped even the inactive Response/Receipt URLs and now get a different error:
The following errors have occurred.
(99) This transaction cannot be accepted.
Please advise. Thanks, Josh.
|
|
Josh
|
February 2, 2017 at 9:54 am
The (99) error indicates that the values you entered in the “Authorize.net API Login ID” and “Authorize.net Transaction Key” fields in the EE > Payment method settings do not match the ones in your Authorize.net account.
Can you check this values again please and make sure you don’t have any space at the start or end of those values?
|
|
Yuan Yuan
|
February 2, 2017 at 11:39 am
I reset the API Transaction Key and used the new one, and now it works! Thank you, Josh. I will let you know if I encounter any further issues with EE4, but hopefully we are all set for registration. Best, Nick
|
