|
Angus Russell
|
September 6, 2015 at 1:36 am
Hi,
We were approached by a client who had made a double payment for an event using our 2CO gateway.
After some to & fro (English not his first language), I got the following explanation:
“I’m sure that that the ‘rejection’ came from the card processing side, since immediately after pressing ‘pay’ and seen the ‘rejection’ note on the screen one person called me to my mobile from the Bank from asking if I was doing a payment to xxxxxxx. I said YES and then he said ‘it’s all right, just a routine check from xxxxxxx Bank’.
Then I came back to the screen but nothing was changing and since I did not received the usual payment confirmation through SMS, I started the process again, believing that it really failed. ”
Our Event Espresso event data only records one entry for him with an incomplete payment record.
Following a previous issue, I followed Josh’s suggestion and made sure that the various EE pages were removed from the caching plugins lists.
I have also asked 2CO to look into this.
If you think there is anything that can be done from the EE end, happy to hear it!
Thanks
Angus
|
|
Josh
|
September 8, 2015 at 10:28 am
Hi Angus,
It sounds like the initial payment went through after the verification. Had they refreshed the page after the bank made the verification, it would have likely been marked as completed. Instead, it sounds like they hit the back button, and started the registration. We have a warning that pops up that says do not hit the back button. What happens is if they hit the back button while on the same session it will overwrite the prior registration.
You can even check the ID column and if there’s a gap between the one registration for them and any previous registrations, that’s one more clue that points to them re-registering on the same session.
|
