Posted: December 5, 2023 at 1:22 pm
|
Hi, As I wrote five year ago we are using only offline payments and to prevent overselling we would need to count registrationg with Pending payment status as Sold. We need to keep the registered space for a few days before registrants pay. We cannot use the ‘Default Registration Status’ setting to ‘Approved’ as: Is there any update in this matter in EE? |
|
|
Hello again, I’m afraid the programmatic situation is still the same. Conflating the Payment Pending and Approved statuses is not something we plan to change nor officially support. Doing so would likely cause a cascade of unintended consequences and require additional alterations. Event Espresso is designed primarily for online payments because online payments help secure ticket sales and registrations nearly instantly. The complications you are facing are due to the delay in receiving payments when accepting offline payments. The Status Pending Payment is intended define who has officially paid or not. The easies way to account for the delay in time for accepting offline payments is to tightly manage the number of tickets available to account for or anticipate how many attendees will (or still need to) actually send in payment. As you get closer to your event dates or have more people send in payment you can adjust the available tickets. You are welcome to hire a developer to make these changes for you personally, but that would likely mean you would not be able to get support from our team nor use any new versions of Event Espresso in the future. I would strongly suggest considering a way to accept instant payments online. |
|
I wish I knew that before we havily invested in EE. 🙁
That is a lot of administration. We acquire EE to lower the administration./
That is what we do. However updates make our life more difficult and the whole EE funcionality is a bit crippled.
Well, wire transfers are more common in Europe. |
|
|
Manual payments require a lot of administration, more manual work, more errors, etc. Accept instant payments and a lot of the administration and trouble inherently goes away because of the delays to wire transfers. The Pending Payment in Event Espresso is correct, you are still awaiting payment. You can choose to manually change the registration status of a new registration to Approved, while not also applying a payment and changing the transaction status, because within Event Espresso you will see that a payment has not been recorded and you will know who has paid or not. That system already exists. |
|
I would love to switch to instant payments. Believe me I wish that. Unfortunatelly we cannot.
Well, what if there is one last spot available, but three people pay via bank transfer at the same/similar time? One will get the spot (and EE will be in correct state), but two other would overpaid. Lots of administration with refund, angry unsuccesful registrants who thought they got the spot and paid immediately…
Yes, but only in more complicated (filtered) view. Most importantly it would not be visible in mobile app. |
|
EE has a reservation system within it so that when you start a registration, the ticket is placed in ‘reserve’ for the duration of your session (which by default is 1 hour) so with that and a Default Registration Status (DRS for short) setting of Approved that situation is avoided. Users can’t start a registration at the same time, user 1 will start the registration, be placed in reserved and then approved. By NOT using a DRS of Approved you are creating the situation you are referring to. Then by trying to switch out the Pending Payment status to also be included in the values it changes how the core functionality EE works and has a waterfall effect throughout the plugin.
May I ask why its more complicated? The TXN status for each registration is easily visible at a glance. Is it because you can’t also filer by TXN Status? Becuase if so I have a snippet for that here: https://gist.github.com/Pebblo/22995de5472c46a361ecc206bc8e9f9b You can add that to a custom functions plugin and we have some documentation on creating one here: https://eventespresso.com/wiki/create-site-specific-plugin-wordpress-site/
This part, I agree with… mostly. The app doesn’t do a good job of highlighting Approved registrations with incomplete transactions, because they are approved they scan and check in as any regular ticket would. They already apply to the sold values so it’s assumed they are attending and the admin will/has already handled payment. It is possible to check for these, you would need to scan the tickets in lookup mode: https://monosnap.com/file/u5hyjULwdgCCbS9MfS5TMfaEAOkUfx Then hit the details button on the top right, which takes you here: https://monosnap.com/file/PnsBgBmAXVPA2rEqVc9YAY2gcthzMe That $20.00 / $0.00 is I’m not saying that’s ideal by any means, but it is possible to do with the app as is. — However…. you do have another option for this which involves slightly more admin work but IMO is still a better option than trying to include Pending Payment registrations in the sold values. You already know you can filter Approved registrations and now have a snippet that can filter approved registrations with Incomplete transactions, I’m assuming your ticket sales end before the event, correct? If so, right before you are due to start scanning tickets, filter all of those Approved registrations with Incomplete transactions and change their status to Pending Payment (be sure NOT to notify the registrations when you do this). Now when they scan their tickets the app will show they are pending payment and I assume they will be asked to pay somewhere at the event… at which point you can force the app to check them in (the app will NOT change their status back to approved). There is a caveat when doing this, you will need to make sure your event is closed off from registrations before switching them (set ‘Display ticket selector’ to no, I’d also advise setting the ticket sale end date/time to be something BEFORE the event starts). If you don’t do the above the event will show as tickets being available right before the event starts (because the registration have switched from Approved and no longer apply to the sold values). Also, you won’t be able to identify which registrations were once Approved and have now been changed to Pending Payment so if you have other registrations sitting at Pending Payment you wont know the difference between those (but that’s a similar situation to what you would be in with your solution anyway), use a CSV report before doing the switch above for that. The above involves a little more admin work to ‘fix’ the registrations but is much less work than trying to alter the Pending Payment status to act like it’s Approved. |
|
|
Hi Tony and Garth,
It is extra admin work. Registrations are opened till last moment, there is no one sitting behind the computer to check the transactions at the time of the event. We are already using the suggested snippet.
In the amount of people coming, clicking there and back in the app is extra time that we don’t have. However following point is the most important. One hour in reserve is not long enough.
I understand, EE does not have this function. |
|
I still don’t follow here, how is this more complicated than adding pending payment registrations to the sold values?
I’m not saying check the transactions, I’m suggesting you take a couple of minutes before the event opens to switch the ‘Approved/Incomplete’ (Reg Status/TXN Status) registration to be pending. Again it’s a much simpler approach than what you are trying to do above.
Yes, as mentioned, it’s not an ideal solution but switching the registrations before the event works around that.
I’ll need more details on this, 1 hour isn’t enough reservation time on the ticket? How so? What do you consider enough in that situation?
It does, when you use a DRS of Approved. |
|
The support post ‘Counting Pending payment registrations with offline payment as sold’ 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.
