• Resolved ulpher

    (@ulpher)


    I had a client which was getting the below 422 error, since the streetAddress was more than 50 characters. I believe this was a response to the verifyCard 3DS Method.

    {“error”:{“message”:”Billing line1 format is invalid.\nShipping line1 format is invalid.”},”threeDSecureInfo”:{“liabilityShifted”:false,”liabilityShiftPossible”:false}}

    Is there a way to get access to these kind of error logs from the server, so that I would know if anything similar happens?
    I have the plugin’s debug enabled, but for the day this was happening, there is only info logs such as “INFO Processing payment for order..”. No error logs.

    After contacting Braintree, they said that these errors are immediately available at my site.

    Thank you

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Payment Plugins

    (@mrclayton)

    Hi @ulpher,

    Thank you for contacting us. That is an error message that is returned from a client side call from the Braintree JS SDK to the Braintree API when 3D secure is being used. Because it’s a client (browser) to Braintree server call, that response isn’t included in the plugin debug log.

    To include those in the Braintree debug log, I would need to add an ajax call from the checkout page that records that log entry.

    I am wondering if a better option is to show that error message to the customer so they will have more context as to why the payment failed.

    Any feedback you have regarding that is welcome.

    Kind Regards,

    Thread Starter ulpher

    (@ulpher)

    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

    Plugin Author Payment Plugins

    (@mrclayton)

    @ulpher I have made a note to try and include the validation specific error message for 3DS in the next release.

    Kind Regards,

    Thread Starter ulpher

    (@ulpher)

    Thank you @mrclayton

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘gateway error logs’ is closed to new replies.