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
Incomplete/pending payments, PSIGate | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Incomplete/pending payments, PSIGate

Incomplete/pending payments, PSIGate

Posted: August 27, 2013 at 1:01 pm

Viewing 1 reply thread


Michel Neray

August 27, 2013 at 1:01 pm

We are having random registrations showing as incomplete or pending in EE, even though the registrant has indeed paid. Their transactions show up in PSIGate, but the information isn’t coming back to EE. We can update it manually, but obviously we’d like to figure out what’s causing this and fix it.

It happened most recently for this event: http://momondays.com/event-registration/?ee=81

INFO: WP and EE are both at the latest version. PSIGate was integrated custom for us to include both US and CAD stores/currencies.


Josh

August 27, 2013 at 7:22 pm

Hi Michel,

Is this a case where the ones that do not get completed have the tax added?
Viewing 1 reply thread

The support post ‘Incomplete/pending payments, PSIGate’ 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, 4 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server