|
MIAQC
|
February 3, 2017 at 9:18 am
I’m trying to get our payment portal set up. Put the system in test mode to try it out (authorize.net SIM). Got an error message (14) referrer, relay, or receipt link is invalid. Please help. Would also like to get invoice option up and running. I’m not a tech person and my web designer does not have time to do this right now – and I need it done ASAP. Thanks.
|
|
Josh
|
February 3, 2017 at 9:50 am
Hi there,
You can prevent the error message (14) by logging into your Authorize.net account and removing all of the Response/Receipt URLs set in your Authorize.net account. The SIM add-on for EE4 will take care of setting those.
We can take care of setting up the Invoice option up and running with the information you sent in the redeem a support token form. We’ll let you know when that’s ready.
|
|
MIAQC
|
February 3, 2017 at 9:58 am
I’ve been to my authorize.net account several times over the past few days. There are no response/receipt URLs currently listed in my account settings. What am I missing?
|
|
Josh
|
February 3, 2017 at 10:02 am
So after you og into the Merchant Interface at https://account.authorize.net.
You click Account from the main toolbar.
Then you click Response/Receipt URLs under Transaction Format Settings.
|
|
MIAQC
|
February 3, 2017 at 10:05 am
Yes, I know. There are no URLs listed there. Nor have there been since I received the error message.
|
|
Josh
|
February 3, 2017 at 10:52 am
OK then, so the problem may be that you put the payment settings into test mode, and you tried to use test mode with non-testing (live) Authorize.net API credentials.
You can use your live Authorize.net API credentials for testing, but set the “Send Test Transactions” to Yes, and you set “Debug Mode On?” to No. You set these in Event Espresso > Payment Methods > Authorize.net SIM before you do a test. After you’re finished testing, you set “Send Test Transactions” to No.
With regards to the Invoice option, do you have specific instructions for how to pay included on the Invoice?
|
|
MIAQC
|
February 3, 2017 at 11:45 am
I have tried this both ways – with payment set in test mode/debug no (which doesn’t let me even get to a test payment option) and with a live (nontest mode) $1 ticket option I created, which gives me the error message. In both instances, I don’t get far enough into the process to enter any credit card data. The problem seems to occur after you enter all of the registrant information, and then make the payment option selection (pay online).
|
|
MIAQC
|
February 3, 2017 at 11:45 am
this is a pretty cumbersome process just to get me where I’ve already been. Isn’t there any way we could chat directly by phone?
|
|
Josh
|
February 3, 2017 at 11:51 am
I don’t have a solution for this that I can share over a telephone call. Here’s what I can do though. I can put in some of our own testing credentials for the Authnet SIM gateway, then run some tests. Then the results of the tests will point us where to go next to fix things.
Is it OK with you if I try the API testing credentials on your site?
|
|
MIAQC
|
February 3, 2017 at 11:54 am
As for invoicing, I have been playing with this a bit while waiting between replies. I think I have it figured out. I just tested it using my $1 ticket option, and see that my registration confirmation can also be my invoice simply by selecting that option. So – I think I am all set there. I just really need to get the payment portal function ASAP…
|
|
MIAQC
|
February 3, 2017 at 12:03 pm
Yes, please feel free to try the API testing credentials on our site.
|
|
MIAQC
|
February 3, 2017 at 12:17 pm
I see you are having better luck using your API credentials. Clearly I have something input incorrectly. Please do help me know what it is… 🙂
|
|
Josh
|
February 3, 2017 at 12:17 pm
The testing credentials worked right away.
The next step I can advise is to get new API credentials from Authorize.net.
You can get a new API Login ID and Transaction Key by following these steps:
Log into the Merchant Interface at https://account.authorize.net.
Click Account from the main toolbar.
Click Settings in the main left-side menu.
Click API Credentials & Keys.
Enter your Secret Answer.
Select New Transaction Key.
Then you replace the old transaction key and API login ID that are set in Event Espresso > Payment Methods > Authorize.net SIM
with the new keys.
|
|
MIAQC
|
February 3, 2017 at 12:19 pm
Thank you. Going now to try that. (although I’ve been here before too!)
|
|
MIAQC
|
February 3, 2017 at 12:26 pm
Question: I’ve created another new transaction key which I have input into Event Espresso. What is a Signature Key – is that a new API key? (because I haven’t created a new signature key, just a new transaction key.)
|
|
MIAQC
|
February 3, 2017 at 12:38 pm
Still getting error message: The following errors have occurred.
(14) The referrer, relay response or receipt link URL is invalid.
|
|
Josh
|
February 3, 2017 at 12:42 pm
The signature key is another type of key that Authorize.net offers, but the Event Espresso SIM integration does not use the signature key. The two items you need are:
API Login ID
Transaction Key
|
|
MIAQC
|
February 3, 2017 at 12:45 pm
I can easily change the Transaction key, which I did and retried the registration, which failed, as I’m still getting an error message. I cannot change the API login id, and per my live chat session with Auth.net apparently that is something that stays the same. What next?
|
|
Josh
|
February 3, 2017 at 1:03 pm
I can suggest re-sending the redeem a support token form and including the log in for the Auth net account. Then we can double check and make sure the credentials are correctly entered into the payment method settings page, and make sure all of the receipt and relay response URLs have been removed from the account.
|
|
MIAQC
|
February 3, 2017 at 1:15 pm
Will do. Thank you.
|
|
Josh
|
February 3, 2017 at 1:41 pm
OK thank you. I checked and there were 3 response URLs set in the Authnet account’s Response/Receipt URLs list If the URL provided does not match one of the values on this list, the transaction will be rejected. So that’s why Authnet was rejecting the transaction from EE. Now that those URLs have been removed from the list, the transactions won’t be rejected anymore.
|
|
MIAQC
|
February 3, 2017 at 1:46 pm
How odd – when I looked there was nothing listed. Perhaps it’s my browser? Thank you, though. I am glad to have the matter on the mend. I will try again now.
|
|
MIAQC
|
February 3, 2017 at 1:49 pm
Thank you – this worked beautifully. I appreciate your help.
|
|
Josh
|
February 3, 2017 at 2:08 pm
I think you may have been looking at the Receipt URL page in the Authnet account which doesn’t show a list, and Authnet also has a Response/Receipt URL page in the Settings area too, which shows the list.
|
