Drop-in Payment UI blanks if form validation unsuccessful

  • alx359

    (@alx359)


    5 years, 4 months ago

    While placing an order during checkout, if form validation doesn’t pass, the BrainTree’s Drop-in Payment UI just defaults and wipes out all CC data. I understand of probably security concerns for this, but from an user perspective, it feels unfriendly, makes prone to customers making further mistakes, and in general, increases the risk of losing sales.

    Expected behavior: CC data to also persist after unsuccessful form validation.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor angelleyesupport

    (@angelleyesupport)

    5 years, 4 months ago

    Hi @alx359 , I’m so sorry for delay in getting back to you.

    Which validation you’re talking about? The woo form validation or the CC form validation? Because I was not able to reproduce any such issues. If you can record a video about how to reproduce the issue then we will be happy to look into that.

    Thanks!
    Oliver

    Thread Starter alx359

    (@alx359)

    5 years, 4 months ago

    Hi Oliver,

    This is a screenshot of my checkout page:
    http://gigahub.com/uploads/pp-bt-ui-issue.jpg

    I’ve marked the BrainTree’s Drop-in Payment UI in a red box on the right-down side.

    If the checkout form isn’t correctly fulfilled, when one hits the “Place Order” button, the form submits and then displays the found issue(s) on the top but still populated, as it should. The issue is, the Bt Drop-in UI isn’t following, as a form submit returns with blank Drop-in UI CC fields (i.e. the ‘Card’ option), and one has to enter all the CC details again. Can you reproduce that?

    Thanks!

    Plugin Contributor angelleyesupport

    (@angelleyesupport)

    5 years, 4 months ago

    @alx359 Ah, okay Now I understand. Let me guide you . Its not really a Braintree issue or our plugin issue. In general this is related to woocommerce. You know that the payment options depends on the billing / shipping address, right?
    So normally this is against the rule of thumb to first fill in the Credit Card info and then fill in the billing information. Because whenever you will change anything in those details, that payment methods section will reload again because the shipping price need should updated as well so the woo order object will also update too , which is why the Payment methods reload again.

    As of Braintree Bropin UI, the iFrame reloads again so that logical that any information filled in will be gone. And that’s how woo works. Hope that explains the concept.

    Let me know if you have any other questions or concerns.
    Thanks!

    Thread Starter alx359

    (@alx359)

    5 years, 4 months ago

    Hi Oliver, I understand. Unfortunately, that’s a rather typical gap between technical concerns and end-user/usability concerns, happening a lot in our trade (IT). To make customers re-enter their CC data because Woo can’t be bothered to persist user-exposed fields when needs to recreate the order object, is like that old adage of putting the horse in front of the carriage.

    Anyway, thanks for the explanation why it can’t be fixed.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Drop-in Payment UI blanks if form validation unsuccessful’ is closed to new replies.