|
subkom
|
November 19, 2014 at 5:22 am
Hi,
after registering for an event, the customer gets to the payment overview site where he can choose PayPal or manual bank transfer. At this moment, he also gets an email with purchase details and his registration id (which he must use within the bank transfer so we can relate the payment).
However, every now and then we receive payments from customer with a good looking registration-id but which is not known by EE. It doesn’t show up in the attendee list nor in the database table. It seems that the registration process has not been completed.
– How is this possible?
– Maybe registration-id is being generated and sent via mail but not inserted into attendee table?
This is leading to massive confusion. Worst, when someone orders ticket, he thinks everything is fine, but when the registration is not recognized, the event could be sold out in the meantime which is really frustrating.
We are using EE3. Thanks for your help.
Best regards
Stephan
|
|
Tony
|
November 19, 2014 at 7:19 am
Hi Stephan,
Can you tell if any of the missing attendees have also booked other events/tickets after the missing purchase?
Let me explain what I think may be happening.
When a users clicks to register onto an event, they start a ‘session’ which has a session_id.
They enter the registration details and confirm (at this point the attendee is added to the database, using the session_id)
Now the user is shown the payment options…. at this point they still have an ‘open’ session.
So the user selects Electronic Funds Transfer and finds the bank details… however at the bottom of the EFT Payment is a link to finalise the registration – http://take.ms/AA19U
This link closes the session and basically gives you a new session_id. This is important because during the registrations the session_id is used to keep track of the attendee and used to push the information to the database. So if they don’t click this link, then register another attendee, they basically overwrite the original details with these new details.
Which version of EE3 are you currently using? We have added pop-ups to the thank you page warning users of doing this.
|
|
subkom
|
November 19, 2014 at 7:36 am
Hi Tony,
thank you for your reply. Your help is much appreciated. Currently we are using 3.1.36.5.P
The mentioned popups might prevent the user from leaving the page without clicking the finalize-link, so this is something we really would see on our page.
Is there a chance to finalize the registration when selecting the electronic funds transfer button? Or already finalize it when entering the “payment options” page? maybe you could provide us with some lines of code?
Thanks again!
|
|
Lorenzo Orlando Caum
|
November 19, 2014 at 10:52 am
Hi,
The notices/warnings that are already in Event Espresso 3 and should appear.
Are you not seeing these?
—
Lorenzo
|
|
subkom
|
November 20, 2014 at 4:47 am
Hi,
the warning message box is already shown, sorry i missed that before.
However, a perfect solution for us would be, if the registration is saved in the database when entering the payment site and the mail confirmation was already sent. Is there a way to achieve this by editing the source code?
|
|
Dean
|
November 20, 2014 at 6:14 am
Potentially, but you would be modifying the plugins core structure so any updates would need to be modified as well which will make maintenance a nightmare.
If you wish to look into it further we have a list of recommended developers here: https://eventespresso.com/developers/event-espresso-pros/
|
|
subkom
|
November 20, 2014 at 6:26 am
Since Ticketing is on the horizon for EE4, we are thinking about upgrading next year.
Will EE4 react similar in this situation?
|
|
Dean
|
November 20, 2014 at 7:06 am
There are some changes coming to the Single Page Check Out (SPCO) system, and it is possible that attendees will be entered into the database much earlier.
Currently they are only entered when finalizing the registration, but (unless things change) they will probably be entered after their details have been captured.
However I am hopeful that this issue will not be applicable to EE4 due to the different way the code handles the registrations and the fact that the finalize option is more noticeable.
|
