Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Authorize.net relay reponse not working for some browser | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Authorize.net relay reponse not working for some browser

Authorize.net relay reponse not working for some browser

Posted: August 16, 2012 at 12:02 pm

Viewing 1 reply thread


vchatham

August 16, 2012 at 12:02 pm

Hi,
We have an event setup for members only and must be logged in. We are using the Authorize.net SIM payment gateway. I’ve tried contacting Authorize.net but they just direct me to their Developer documentation which is not very helpful.
We are have gotten registrations from about 10 users since an email blast yesterday. Most of these people seem to be in IE 7. It seems the confirmation page of the event doesn’t refresh to the Auhorize.net page: “https://secure.authorize.net/gateway/transact.dll”

The page that has Event registration code and short code is “http://www.naiopsfba.org/?page_id=83” and in our Authorize.net account I am using http://www.naiopsfba.org/?page_id=83 under the “Default Relay Response URL” Is this correct? Should it be a different confirmation page or a page with https://?

Below is our Confirmation page:
“REGISTER

Virginia Test,

Your registration is not complete until payment is received.

Amount due: $60.00

Your Registration ID: 502d333c502d62.24280603

Please choose a payment option:

Off-site Payments
Please wait, your order is being processed and you will be redirected to the payment website.

If you are not automatically redirected to the payment website within 5 seconds…”


Josh

August 16, 2012 at 1:02 pm

Looks like you have the registration page set as the response URL. It should be set as directed in the Auth.net payment settings (it’s highlighted in yellow). Since you’ve sent log in creds and purchased a support token I can take a look and make sure the payment/response page is set up correctly. Stand by while I get that URL, you will need to log into authorize.net and change the response URL once I verify what it should be.

In looking over the priority support ticket, it looks like you’re also having an issue with the confirmation page not loading the CSS. This can be resolved by installing an SSL certificate for your domain and once installed, enabling the “Force HTTPS on Return URL” option in Event Espresso>Payment Settings>Authorize.net SIM Settings.
Viewing 1 reply thread

The support post ‘Authorize.net relay reponse not working for some browser’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

The original Forum description...

Status: closed

Updated by Josh 12 years, 5 months ago ago

Topic Tags

Tagged: , , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server