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 Ticket Price for Extra Attendee, Reg. Deposit, Campaign Monitor, Gateway | Event Espresso - Staging Server
When registering extra attendees, is it possible to assign a ticket price option to each attendee. Currently all attendees use the selected ticket price. I see its possible if the Add-to-cart method is used.
Registration Deposit
Is it possible to pay 10% of the total amount to confirm registration? Which is then deducted from the total amount owing.
Right, with the Multiple Event Registration addon you can do that with the cart function. This function will also be standard in 3.2, which we’ve released an alpha version for user testing.
I would give attendees a deposit and full-price option. The full-price option is obviously the full amount, but if an attendee chooses the deposit function then after they register and pay the deposit, you’ll have to go into their payment record and set the amount due to be the balance. They will then be sent an invoice to finish their payment. Does that make sense?
You can build your own gateway, or you can hire us to do the same. I would recommend the latter because the gateway process in constantly changing and we’ve made significant improvements in 3.2. We don’t have full-documentation on writing your own gateway yet because we’ve been busy building 3.2.
The support post ‘Ticket Price for Extra Attendee, Reg. Deposit, Campaign Monitor, 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.