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
Collected Attendee data not being sent to FirstData | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Collected Attendee data not being sent to FirstData

Collected Attendee data not being sent to FirstData

Posted: September 6, 2012 at 10:10 am

Viewing 1 reply thread


straycatco

September 6, 2012 at 10:10 am

We are collecting the name, address, etc when they register but that info is not being sent to Firstdata when they make a payment. Event Espresso records the payment as made but none of the collected data is transferred to Firstdata to reconcile the payment. Only the Transaction/Order number is recorded??


Sidney Harrell

  • Support Staff

    •

September 7, 2012 at 11:53 am

We’ve made the changes to the Firstdata Connect 2.0 gateway to send the attendee information to Firstdata. We’ll be running some tests on it over the weekend, and hopefully have it added to the next version.
Viewing 1 reply thread

The support post ‘Collected Attendee data not being sent to FirstData’ 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: resolved
Event Espresso - Staging Server