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
USAePay error | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › USAePay error

USAePay error

Posted: July 8, 2013 at 11:55 pm

Viewing 5 reply threads


Anthony Huy

July 8, 2013 at 11:55 pm

Hi,

I have setup payments to use USAePay. I have an SSL certificate setup. I assume it detects it because the error message that the payment option on the dashboard disappeared once the SSL is setup. The site and page is not hosted on an https connect.

With all that, when I test the site and register and go to pay, I get this error:

Transaction authentication required.
There was no response from USAePay.

Any help in setting this up would be great.

Thanks
Tony


Josh

July 9, 2013 at 11:23 am

Hi there,

Is this the off-site version of USAepay or the on-site version? If it’s on-site, it might need to have the page set up to load as https, which can be done by following this guide:

http://staging.eventespresso.com/wiki/espresso-sslhttps/

Also, are there any error codes that display with the error message?


Anthony Huy

July 9, 2013 at 12:01 pm

Hi Josh,

This is an on-site version. It is now using HTTPS using the wordpress plugin you listed above. I still get the error. Here is a screen shot of the error I get:

https://docs.google.com/file/d/0B1FJwW33Chs9dDVub2gwMll5R2s/edit?usp=sharing

here is a screenshot of my settings

https://docs.google.com/a/forhisglorycc.org/file/d/0B1FJwW33Chs9VVFJVVBId2ZsWUk/edit

Is there a log somewhere for this plugin that would give further error codes?

Thanks,
Tony


Josh

July 9, 2013 at 2:25 pm

Here’s more details re: the Transaction authentication required error:

The merchant has set a pin for this transaction but the api did not receive a UMmd5hash. They need to either upgrade their software to send the hash or they need to remove the pin on the source.

source:

http://wiki.usaepay.com/reseller/console/resources

In the source keys settings documentation on page 56:

http://wiki.usaepay.com/_media/downloads/m_guide.pdf

it shows where the Pin can be entered in the Source Info editor. Can you check to see if the optional Pin field is empty?

As an aside, you might try unchecking the Force HTTPs on Return URL setting as it’s probably already HTTPS.


Anthony Huy

July 9, 2013 at 5:47 pm

Josh,

I actually have my pin number. But where can I put it. Hardcode it into the code?

Tony


Josh

July 9, 2013 at 6:14 pm

I don’t think so. Does it work if you remove the pin from the source field?
Viewing 5 reply threads

The support post ‘USAePay error’ 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 11 years, 6 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server