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
Payee Needs to Be Different Than Person Paying | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Payee Needs to Be Different Than Person Paying

Payee Needs to Be Different Than Person Paying

Posted: March 16, 2013 at 2:26 pm

Viewing 2 reply threads


Michael Taylor

March 16, 2013 at 2:26 pm

We have parents registering/paying for the kids to attend athletic training sessions. We just launched and parents have noted that they are showing as the attendee and not their child whom they are registering. How do I have them register their child as the ATTENDEE but the parent is the one who completes the payment info?

Details for my set up:
http://peakcrosstraining.com/register/
WP 3.5.1
Event Espresso Version 3.1.30.7P
Active EE Plugins (Mailchimp, Members, Mult Event, Permissions, REcurring, Social Coupons, Social Media, Recurring)


Michael Taylor

March 17, 2013 at 7:17 am

I’m sorry – I meant the title to read ATTENDEE needs to be different than person paying.


Dean

  • Support Staff

March 18, 2013 at 3:42 am

Hello,

The Primary Attendee is always the purchaser. Of course, you could advise the clients to sign up with their childs name and pay with their details, it shouldnt matter from a payment perspective. I would also make sure there are additional required questions requesting the parents details.

Viewing 2 reply threads

The support post ‘Payee Needs to Be Different Than Person Paying’ 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.

Event Espresso - Staging Server