|
poptheagency
|
October 16, 2017 at 5:25 am
The customer originally tried to buy 4 tickets for an event for £240, but the card was declined – presumably because they didn’t have enough funds. This was on this date: 2017-10-08 3:17 pm.
The customer then went back to the event page and changed the order to 2 tickets for £120; the card was again declined, on this date: 2017-10-08 3:19 pm.
The customer tried again to buy 2 tickets. The payment was successful this time. This was on this date: 2017-10-08 3:21 pm.
In Event Espresso in the WordPress admin, the transaction had the three separate payments: two failed payments for £240 and £120; and one accepted payment for £120. The transaction Items show a ‘Transaction Total’ of £120 – this, we’re assuming, is the accepted payment.
However the Transaction Status was still ‘Incomplete’ and the ‘Attendees Registered in this Transaction’ section showed two pending and two failed attendees. We’re assuming that the session initially registered 4 tickets, of which 2 were successfully paid for. This seems like a bug in Event Espresso. Have you encountered this before?
The customer then received a confirmation email saying that the payment status is incomplete. However, we only want customers to notifications for ‘complete’ payments.
Do you know how we can prevent this issue in the future?
|
|
Josh
|
October 16, 2017 at 10:56 am
Hi there,
May I ask is this happening with the current version of Event Espresso 4 and which payment method was used for the transaction(s) in question?
|
|
poptheagency
|
October 17, 2017 at 3:22 am
Hi Josh. The version version of Event Espresso is 4.9.44.p. The payment method is ‘Stripe’.
Is this a known bug and can it be fixed by updating to the latest version of EE, 4.9.48.p?
Also, could you please point me to a page where I can read about the bug fixes in EE 4.9.48.p?
Thanks
|
|
Tony
|
October 17, 2017 at 8:30 am
Is this a known bug and can it be fixed by updating to the latest version of EE, 4.9.48.p?
It’s not a known issue and without the exact steps, we can’t say for sure if this will fix the above. I can’t reproduce the same issue when following the steps posted – http://take.ms/yGMbo
We’re assuming that the session initially registered 4 tickets, of which 2 were successfully paid for.
You shouldn’t be able to partially pay for registrations, each time you go back to the event page and select new tickets, a new session should be created (that’s why you see all my registrations are separated out in a group of 4, 2 and 1).
How did the user go back to the events page?
Did you have the multi event registration add-on enabled?
Are you running any caching plugins or does you host run server-side caching?
Also, could you please point me to a page where I can read about the bug fixes in EE 4.9.48.p?
You can find our change log here:
https://eventespresso.com/wiki/ee4-changelog/
|
