|
April 18, 2019 at 3:59 pm
Hi there,
Although users register onto events before payment, by default they do not apply to the event until payment is made.
Are you using a ‘default payment status’ of ‘Incomplete’?
You can find the default setting for all your events within in Event Espresso -> General Settings:
https://monosnap.com/file/YBLqIUG2mTyK43TGG0xfVcFcCCe2Hf
However, that can also be overridden per event within the settings:
https://monosnap.com/file/zJFHTYhmYcjI4MzNZa7f0yObWGMjvl
(‘No change’ will use the default value set in General Settings at the time of registration)
You mentioned in your other thread that you are handling emails outside of Event Espresso, so when are you sending the confirmation emails? After successful payment?
A major problem is the fact that Event Expresso allows users to “register” prior to payment thus resulting in registrants to events not paying on time or at all – or showing up at events with non-payment.
If a ticket has a price in Event Espresso, you’re given the option to pay for it.
If you don’t choose to pay for it and then show up at the event expecting to be given access, I’m not sure how EE handles the registrations changes that?
User don’t receive confirmation emails before payment (again this is by default) so if you’ve changed this they may. So if they show up to the event stating they have paid when they have not, EE not saving the registration isn’t going to change that, or am I misunderstanding the above?
I don’t see any settings to force payment at time of registering which is in theory far more logical approach versus a second step which almost feels optional or could be overlooked.
You can’t force payment, what’s to stop the user simply closing the browser?
Again, regardless of what EE does with the registration data, the registrations don’t apply to the event until payment is made, then emails are triggered etc etc. If you’ve changed this flow so they receive emails earlier than this, its that which is causing the confusion rather then EE saving a registration that doesn’t apply to the event.
If we don’t save the registration, you can’t send payment reminders, view if users are haivng issues registering onto your events etc.
Is there something that I am missing? Or is this a limitation of Event Expresso or the Paypal Standard payment approach?
Can you provide more details on the ‘limitation’ you are referring to? The fact that EE stores registration data early? That’s not a limitation, it’s a design choice for EE.
We want registrants to enter payment details prior to registering for an event.
Both EE3 and EE4 store the registrations early, but that doesn’t mean the registration apply to the events sold values.
I think there’s some confusion above and I’m not sure I follow exactly what the problem is, can you link me to an event I run a test registration on to view this so I can understand what is happening better?
|
