• Resolved wmacmill

    (@wmacmill)


    Running into issues with the ACH integration returning an error when attempting to chekout “Error processing payment. Reason: public_token must be a non-empty string” once they’re logged in and go back through the checkout a second time everything works. Any ideas?

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

    (@mrclayton)

    Hi @wmacmill

    That sounds like you have an issue with the ajax request fetching the ACH token when the user is not logged in.

    I’d take a look at what plugins you have installed that might be rejecting ajax requests for non-logged in users.

    You can use your network tab in the chrome dev tools to observe that ajax request for a guest user and see what the response is. It will probably be a 403 http response code.

    Thanks,

    Thread Starter wmacmill

    (@wmacmill)

    So no issue with the response – everything coming back 200 for ?wc-ajax=wc_stripe_frontend_request&elementor_page_id=3989&path=/wc-stripe/v1/plaid/link-token

    Plugin Author Payment Plugins

    (@mrclayton)

    @wmacmill Can you please share your website url?

    The fact that this just started happening is a strong indication something on your site changed since we haven’t released a new update in 4 weeks. Our most recent update was released after your request and we didn’t change anything related to ACH.

    Thread Starter wmacmill

    (@wmacmill)

    Found the conflicting plugin https://www.ads-software.com/plugins/woocommerce-product-price-based-on-countries/ but what’s weird is they haven’t had an update in over 2 months so trying to narrow down what it could be.

    Plugin Author Payment Plugins

    (@mrclayton)

    @wmacmill were you able to narrow down what was causing that error?

    Thread Starter wmacmill

    (@wmacmill)

    I was not able to – updates along the way seem to have resolved whatever the underlying issue was and we seem to be no longer experiencing it.

    Thread Starter wmacmill

    (@wmacmill)

    Also thanks for following up on it.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Error processing payment. Reason: public_token must be a non-empty string’ is closed to new replies.