ulpher

Thank you @mrclayton

Hi @mrclayton,

Thanks for your reply.

I think it makes sense to show specific error messages like that, especially for the validation. As you said, the customer would at least know (or have a better idea) what needs to be amended. The error shown in this case was very generic: “The data passed to the 3D Secure provider was in an invalid format. Please check your entries for invalid values.”. If you can show the error text and explanation I believe the customer would easily be able to correct.

However, I think it is also wise for the website owner to know of such errors and their frequency through the logs. This would enable them to create a more user friendly website and avoid abandoned carts. As you know, an error like the one mentioned can easily be taken care of whilst the user is filling up the checkout form, making it more user friendly (which now, in this case, it was taken care of from my side).

Thank you for your help.

Best Regards

Hey Steve,

I’m referring to woo-payment-gateway, my mistake. Sorry to have wasted your time!

Regards

Hi @skyvergesteve

Thanks for your reply. I was aware of that config and the logs location, but unfortunately the error mentioned was not being logged. For the day that the error was known to be happening, there are only INFO logs like ‘INFO Processing payment for order ??’.

That error got triggered since ‘streetAddress’ had more than 50 characters. I believe this is a response to the 3DS ‘verifyCard’ method. I only found out the specifics after contacting Braintree support as the error displayed to the client was much more generic: “The data passed to the 3D Secure provider was in an invalid format. Please check your entries for invalid values”.

Plugin version I am running is 3.1.8. Maybe there were improvements since? But I didn’t see anything related in the release notes.

Thanks

same issue here as well

Thank you