• matlitel

    (@matlitel)


    Hi,

    I’m getting reports from some customers that they are unable to pay during checkout saying when they click the button nothing happens. We have had more issues than we are comfortable with customers having problems during checkout.

    There are no obvious errors in the server logs but looking at the console in checkout i see this error.

    Refused to apply inline style because it violates the following Content Security Policy directive: “style-src ‘self'”. Either the ‘unsafe-inline’ keyword, a hash (‘sha256-1bd1ss83rhoRESXnUSD+xUzVPZzKrKQPYKkWOj5TJIc=’), or a nonce (‘nonce-…’) is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the ‘unsafe-hashes’ keyword is present.

    Not sure if that is of any use but any tips on diagnosing?

    thanks

    MAt

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

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

    (@mrclayton)

    Hi @matlitel

    I reviewed your site and don’t see any Javascript errors being triggered by 3rd party plugins. The Stripe plugin correctly submitted the payment method to Stripe for verification when the place order button was clicked.

    There are no obvious errors in the server logs but looking at the console in checkout i see this error.

    That error isn’t related to your payments functionality and wouldn’t cause any issues.

    What you’re describing is more than likely not a Stripe plugin issue. It sounds like you might have some functionality that’s listening for the click event on the place order button and it’s calling e.preventDefault() which prevents the checkout form from submitting, which is how WooCommerce processes the order via the checkout page.

    Is there a corresponding order within WooCommerce for one of these affected customers? If not, then that means the click event is most likely being intercepted. If there is an order, that means the issue could be happening after the checkout form is submitted.

    I looked at the Stripe logs and there aren’t any failures there that would indicate it’s a result of a failed Stripe API request.

    Kind Regards

    Thread Starter matlitel

    (@matlitel)

    Thanks for taking the time to look.

    Mat

    Plugin Author Payment Plugins

    (@mrclayton)

    Hi @matlitel

    Any instances of that issue being reported still? Or were you able to track down the source of the problem?

    Kind Regards

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Some customers unable to pay’ is closed to new replies.