|
echobrin
|
June 6, 2023 at 9:59 am
We switched from PayPal Express to PayPal Commerce and it seems to be working fine for most people but some are getting this error: Invalid order ID provided. Someone said the error pops up before going to PayPal or asking for credit card info. The logs show this error for several other people who were eventually able to complete their payment, but the person who brought this to my attention has tried three times with the same result.
|
|
Tony
|
June 6, 2023 at 1:17 pm
Hi there,
I could ask a bunch of question on this, but it would be quicker if I can take a quick look over the payment logs if that’s ok?
If so you can send temp login details using this form:
https://eventespresso.com/send-login-details/
If not I can work through the logs with you but will need screenshots of each one as I’m looking for anything that may stand out rather than something specific.
|
|
Tony
|
June 6, 2023 at 1:56 pm
Thank you for the login.
So there isn’t an Order ID on those requests, they are empty.
The value for the Order ID is set once the PayPal modal opens, so, I’m wondering how these users are submitting the form. It looks like they are somehow managing to submit the form before opening the modal which is why no ID.
Can you ask the above users for the steps they are taking on the payment options step?
|
|
echobrin
|
June 6, 2023 at 4:44 pm
I did some more testing and I think I’m onto something… I had the PayPal Commerce button selected by default in the settings since it’s the only payment method we use. I noticed that if you click that button again (even though it’s already selected) it stays blue but the big PayPal/Pay Later/Debit or Credit Card buttons under the billing info form disappear. The “Proceed to Finalize Registration” button then appears and if you click that, you get the invalid order ID error message.
For now I have turned off the option to have the PayPal Commerce payment method selected by default. Hopefully this will lead to fewer errors but there is still a change of someone accidentally clicking on that button more than once and causing the error.
|
|
Tony
|
June 7, 2023 at 6:31 am
Nice sleuthing and nice find!
I can confirm this and have created a ticket for our developers to investigate/fix.
|
