Support » Plugin: WooCommerce Stripe Payment Gateway » My clients can’t wright there credit card information

  • Resolved Coraline Ribière

    (@coralinerib)


    Hello,

    Today I tried to take on order on my website with my administrator account to test the new icons added by Stripe (as suggested by a banner on my admin account) and realized that it was impossible to wright credit card information on the Stripe boxes.

    The boxes height looked smaller than usually and it was impossible to click inside and add credit card information.
    I tried to order as a client too, and the problem was the same.

    Could you help me fix it please.
    Thank you

    Coraline

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author royho

    (@royho)

    Hello,

    That is because you have JS errors on your site. Possible coming from your theme or a plugin. Try switching to a default theme and turn all plugins off except WooCommerce and Stripe.

    Hi,

    Thank you for answer. I finally find what plugin was blocking stripe (by the way, this blocking only appears on safari). That’s Autoptimize which is blocking stripe.

    I will contact them to fix it.

    randommess

    (@randommess)

    Hi, @royho
    This exact thing is happening for me too, again, and just with the latest plugin update. Does this really show just us an admin 2019 preview or is this live and I need to worry about having a tiny unusable cc field breaking my Stripe checkout again if I use the latest update? I rolled mine back to 4.1.10 so everything works. Let me know if you need me to switch it back to the latest update to troubleshoot. BTW I had JS errors, too, one of the two was an error 500, but both were only present when 4.1.11 was activated :<

    Optimizing Matters

    (@optimizingmatters)

    in Autoptimize unticking the option “also aggregate cart/ checkout” should fix this 🙂

    Plugin Support woosteve

    (@woosteve)

    Automattic Happiness Engineer

    It seems that the original thread was resolved with conflict testing and a helpful suggestion from Optimizing Matters.

    The new question by @randommess seems to also be a conflict, which can be identified by temporarily disabling all other plugins and activating a default WordPress theme.

    I’ll resolve this thread, but if the above does not help you determine the cause of the error, please feel free to open a new thread.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.