|
EastBayDev
|
February 23, 2018 at 5:19 pm
I am getting the following error: The following errors have occurred.
(14) The referrer, relay response or receipt link URL is invalid.
The event is created. The cart items show up but after I select the payment type. I get the above error message.
Any suggestions as to the cause or fix?
|
|
Tony
|
February 26, 2018 at 3:07 am
Hi there,
That error is directly from Auth.net themselves, you’ll find details here:
https://developer.authorize.net/api/reference/responseCodes.html
Type 14 in the search bar and press enter.
—
If you login to your Merchant Interface at https://account.authorize.net/
Click Settings in the main left side menu
Click Response/Receipt URLs
Do you have any URL’s set there?
|
|
EastBayDev
|
February 26, 2018 at 12:35 pm
Yes, I have URLS set for https://ebwn.org/ but now I am getting error code 99
Here is the information that I found in Authorize.net amount need 2 decimal for the x_fp_hash. so on your example need to be 75.00
If you still getting Error 99 that use the https://developer.authorize.net/tools/responsecode99/ to make sure the timestamp is correct.
|
|
EastBayDev
|
February 26, 2018 at 12:53 pm
By the way, I am using Authorize.Net SIM
|
|
Tony
|
February 26, 2018 at 1:20 pm
Error 14 is only applicable to SIM so I guessed you were using that 🙂
Can you link me to a test event so I can view this, please?
|
|
EastBayDev
|
February 26, 2018 at 1:34 pm
Yes, here is a test page: https://ebwn.org/events/tumikias-test-event/
|
|
Tony
|
February 26, 2018 at 1:53 pm
With regards to:
Here is the information that I found in Authorize.net amount need 2 decimal for the x_fp_hash. so on your example need to be 75.00
The value sent in x_amount is already in 2 decimal places, like this:
name="x_amount" value="1.00"
Looking through the payment just before its sent to auth.net it all looks correct and matches my site when making a test payment.
Your currently submitting payment to the ‘live’ server, so are you using live credentials?
Have you ran through the tool here and provided the details from one of these payments to see what error is shown?
https://developer.authorize.net/tools/responsecode99/
|
|
EastBayDev
|
February 26, 2018 at 1:58 pm
Authorize.net referred me to this tool, but no, I am not sure how to use it.
For example, where do I get this information?
Also, I am thinking about switching back to EE3 temporarily as our event is fast approaching. Will I lose the EE4 information and will the EE3 set up be available?
EE3 was connected to PayPal
|
|
Josh
|
February 26, 2018 at 2:00 pm
Hi there,
You will lose the EE4 information if you downgrade to Event Espresso 3. You could use PayPal Express with EE4 and use the same PayPal account you used when you had EE3.
|
|
Tony
|
February 26, 2018 at 2:07 pm
For example, where do I get this information?
The easiest way to find that information is in the payment logs:
Event Espresso -> Payment methods -> Logs.
Find a payment made by auth.net, you’ll likely have a log entry for each individual payment attempt that has been made.
One of those entries (click the Log ID number, not the ‘view txn XX’ link) should look like this – http://take.ms/bAkCe
Thats all the info you need for the tool with the exception of x_tran_key, thats the ‘Transaction Key’ you set in the payment method settings.
|
|
EastBayDev
|
February 26, 2018 at 2:23 pm
Good to know. PayPal Express Worked! We can use it temporarily.
|
|
EastBayDev
|
February 26, 2018 at 6:42 pm
Thanks Tony and Josh for all your help. The site is now connected to PayPal and Authorize.net
For Authorize.net I had to create a new transaction key. It works fine now.
Thanks.
|
