Support

October 24, 2022 at 9:18 am

Hi there,

The ‘Registration could not be completed’ error is a catch-all error for when EE does not have a ‘proper’ error to display from the request, meaning it either had a response it didn’t understand/wasn’t expecting or nothing at all.

If there is an error being thrown for the above, that would usually be saved in the server’s error logs so if you check those around the time of one of these registrations, can you see any errors from Event Espresso?

Also, if you open up the EE Transaction for one of these users, can you see anything in the ‘Gateway Response’ field?

Finally, as you’ve mentioned Stripe and it’s happening to ‘some’ of your users, I’m wondering if you’re using the old Stripe checkout integration which doesn’t support 3DS. This would mean any users getting a 3DS check on payment would fail.

Go to Event Espresso -> Payment methods -> Stripe.

Find ‘Integration Type*’

Is it listed as ‘Stripe Checkout (legacy) or ‘Stripe Elements’?

October 24, 2022 at 2:14 pm

Yeah, so it does sound likely that those failed transactions required 3D Secure verification and Stripe Checkout doesn’t support it.

I obviously can’t say for sure, but the numbers match in that they give a rough estimate of 30% of transactions for 3DS.

If you continue to run into this issue please do let me know and we can troubleshoot further.