Many Console Errors and Payment Failure

  • Resolved Satinder Singh

    (@satindersingh)


    1 month, 2 weeks ago

    POST https://api.stripe.com/v1/consumers/sessions/lookup 404 (Not Found) – if user is already login then checkout page showing this error in browser console many times.

    Also i’m facing this sometimes – This object cannot be accessed right now because another API request or Stripe process is currently accessing it. If you see this error intermittently, retry the request. If you see this error frequently and are making multiple concurrent requests to a single object, make your requests serially or at a lower rate.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Satinder Singh

    (@satindersingh)

    I communicated with stripe support regarding this and they provided this response:

    I’ve thoroughly looked into the the PaymentIntent and it seems that during the creation, your application, WooCommerce Inc, explicitly passed card as the payment method to charge this transaction. On the other hand, during PaymentIntent confirmation, you passed this in your request: “key”: “pk_live_H86———–gXX”, “_stripe_version”: “2024-06-20”, “source”: “payatt_1Q7——wlVY” You passed a source: payatt_1Q7——wlVY

    In order to resolve this, you need to confirm the PaymentIntent without passing the source if possible.

    I also checked this in an instawp test site where strorefront theme along with just woocoomerce and stripe plugin is installed.

    Plugin Support Reynier C. (woo-hc)

    (@reynierc)

    hI @satindersingh ,

    Thank you for providing detailed information about the issues you’ve encountered with Stripe payments.

    From what you’ve provided, it looks like there’s a mismatch in how the payment method information is being passed to Stripe during the payment process. The error you’re encountering typically occurs when the payment method set during the creation of a PaymentIntent doesn’t match the method used for confirmation.

    To address this, please ensure that the payment method details are consistent throughout the payment process. You might want to check your store’s Stripe settings within WooCommerce to confirm that they’re configured properly and that no additional parameters are being passed during the confirmation that could conflict with the initial payment method specified.

    Since you’ve already set up a test environment, that’s a great starting point. Try running transactions there to see if you can replicate the issue. If the issue persists, please check the Stripe logs within the WooCommerce settings to provide more insight into what may be happening.

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