|
FASeminars
|
August 20, 2019 at 11:42 am
Hello,
I have posted different tickets in the past asking questions to which some replies were insightful learning how EE works for payment part during registration.
We are currently using EE3. Understanding how the payment part works (registration comes first, then user can pay later), this causes challenges with how we need it to work since on point of registration form submission, we’re passing registrant data to a Marketing Automation system.
Problem is that on point of submission all registrations are deemed “not paid”. The data doesn’t pass at a later date updating payment part.
Is there a way currently to ensure payment is mandatory for event registration? We’ve evaluated this (our EE3 is heavily customized for client needs), and to try and customize logic to to pass ONLY after payment is completed is complex and we’re not sure best approach.
Does EE4 or future releases have payment as mandatory step (kind of like an eCommerce) so that registration only occurs if payment completion?
Thanks for any help that can be supplied to this thread.
Mike
|
|
Josh
|
August 20, 2019 at 12:29 pm
Hi Mike,
It sounds like what you need to do is hook in at the point of payment received, when passing registrant data to a Marketing Automation system. For example, the later hook point when the Payment Received email is triggered could be used.
In Event Espresso 3 there is:
action_hook_espresso_track_successful_sale
and
action_hook_espresso_email_after_payment
You could use either of the above.
Does EE4 or future releases have payment as mandatory step (kind of like an eCommerce) so that registration only occurs if payment completion?
It doesn’t, and no plans to change this. Event Espresso isn’t an eCommerce cart system, it’s an online registration platform. Some use cases require registration without payment so the current system allows for this.
|
