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
Time Period Error using FirstData Connect 2.0 Gateway | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Time Period Error using FirstData Connect 2.0 Gateway

Time Period Error using FirstData Connect 2.0 Gateway

Posted: September 16, 2012 at 1:11 am

Viewing 1 reply thread


Brian Sterr

September 16, 2012 at 1:11 am

I have EE set up with the firstdata gateway and I continually get the following error upon loading of the firstdata transaction page:

Your transaction did not complete successfully
The cause of this error could be one of the following:
The time period for this action has already elapsed.

Any idea why I would be getting this? I believe I have everything set up on EE, but is there some other setting I possibly missed?


Sidney Harrell

  • Support Staff

    •

September 16, 2012 at 11:07 pm

Hey Brian,
There may be a mismatch between the timezone setting you have set in the EE FirstData Connect 2.0 payment settings and the timezone where your server is physically located. For Connect 2.0 FirstData requires us to send both a timestamp from the server and a timezone. You should be able to see all the data being sent to FirstData if you inspect element on the FirstData logo on the payment page and look at the form submission hidden fields.
Viewing 1 reply thread

The support post ‘Time Period Error using FirstData Connect 2.0 Gateway’ 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 Sidney Harrell 12 years, 4 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server