Title: Checkout problems
Last modified: October 25, 2025

---

# Checkout problems

 *  Resolved [Roberto Valente](https://wordpress.org/support/users/rvof/)
 * (@rvof)
 * [5 months, 2 weeks ago](https://wordpress.org/support/topic/checkout-problems-6/)
 * WordPress Version: 6.8.3
   Server Information: Microsoft-IISWooCommerce Version:
   10.2.2 Works fineWooCommerce Version: 10.3.3 Spinner doesn’t stop
 * I have two WordPress installations, both with the settings above.
   The only difference
   is in the WooCommerce version.At ingressoplus.com.br, it’s 10.3.3 (I’ve tested
   since 3.0).At ingressoplus.net.br, it’s 10.2.2.In WooCommerce versions 10.3.x,
   they all have the same problem.When I reach the checkout, the spinner doesn’t
   stop, and the element below remains visible, overlaying the payment options.Therefore,
   the checkout cannot be completed.I removed all caching, optimization, and debloat
   plugins, but the problem still persists.I would like help resolving this issue
   because I can’t update the site to new versions of WooCommerce.
 * Bellow you can check the both links and what happens
   [https://ingressoplus.net.br/Pagar/?id=1444488&cliid=11](https://ingressoplus.net.br/Pagar/?id=1444488&cliid=11)
   OK, version 10.2[https://ingressoplus.com.br/Pagar/?id=1444488&cliid=11](https://ingressoplus.com.br/Pagar/?id=1444488&cliid=11)
   spinner dont stop , version 10.3
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcheckout-problems-6%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Support [LovingBro (woo-hc)](https://wordpress.org/support/users/lovingbro/)
 * (@lovingbro)
 * [5 months, 2 weeks ago](https://wordpress.org/support/topic/checkout-problems-6/#post-18695301)
 * Hi Roberto,
 * I understand how frustrating it must be that your checkout stops working and 
   the spinner keeps running after updating to WooCommerce 10.3.x. I took a look
   at your checkout page using the browser’s inspection tools, and I found some 
   clear indicators of what’s causing this behavior.
 * In the **Network** tab, the request to update the order review ([https://ingressoplus.com.br/web/?wc-ajax=update_order_review](https://ingressoplus.com.br/web/?wc-ajax=update_order_review))
   is returning a **500 Internal Server Error**. This means that WooCommerce is 
   triggering a server-side error when it tries to refresh order details at checkout—
   which prevents the process from finishing and keeps the spinner active indefinitely.
 * From the **Console**, there’s also a JavaScript error:
 *     ```wp-block-code
       Uncaught TypeError: Cannot read properties of null (reading 'addEventListener')
       at pagamento/:896
       ```
   
 * This shows a script on your checkout page (pagamento.js) trying to attach an 
   event to an element that doesn’t exist anymore, which could be caused by changes
   in the checkout markup introduced in WooCommerce 10.3.x.
 * In addition, I noticed calls to external services like Mercado Pago being blocked(
   ERR_BLOCKED_BY_CLIENT) and requests to api.mercadolibre.com/tracks. These indicate
   a possible **JavaScript or API conflict** involving the Mercado Pago plugin.
 * To narrow down the cause, I suggest testing the following:
    1. **Temporarily disable Mercado Pago** in **WooCommerce → Settings → Payments**
       and reload the checkout page. This will confirm whether the issue is triggered
       by that gateway’s scripts.
    2. **Temporarily switch to the Storefront theme** and test again to rule out any
       theme-specific conflict.
    3. Check your **server’s PHP error logs** for the exact 500 error entry — it will
       show the specific file and line where the problem occurs.
    4. If the spinner stops after disabling Mercado Pago, the issue likely lies in 
       how its checkout integration handles AJAX responses in WooCommerce 10.3.x.
 * Once you gather the PHP error details or results from the plugin test, please
   share them here — I’ll be happy to help pinpoint the exact cause and suggest 
   the safest way to fix it so you can update WooCommerce confidently.
 * Let’s see how it goes!
 *  Thread Starter [Roberto Valente](https://wordpress.org/support/users/rvof/)
 * (@rvof)
 * [5 months, 2 weeks ago](https://wordpress.org/support/topic/checkout-problems-6/#post-18695679)
 * Many thanks. The problem was detected on pagbank plugin. Created a new topic 
   about this problem on plugin support.
 *  Plugin Support [LovingBro (woo-hc)](https://wordpress.org/support/users/lovingbro/)
 * (@lovingbro)
 * [5 months, 2 weeks ago](https://wordpress.org/support/topic/checkout-problems-6/#post-18695751)
 * Hi [@rvof](https://wordpress.org/support/users/rvof/),
 * Thank you for sharing your update and confirming that the issue was traced to
   the PagBank plugin. I appreciate you taking the time to follow up and let us 
   know.
 * I’ll go ahead and mark this thread as resolved, but please feel free to get back
   to us anytime if you need further help.
 * All the best with your site!

Viewing 3 replies - 1 through 3 (of 3 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcheckout-problems-6%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/woocommerce/assets/icon.svg?rev=3234504)
 * [WooCommerce](https://wordpress.org/plugins/woocommerce/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/woocommerce/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/woocommerce/)
 * [Active Topics](https://wordpress.org/support/plugin/woocommerce/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/woocommerce/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/woocommerce/reviews/)

 * 3 replies
 * 4 participants
 * Last reply from: [LovingBro (woo-hc)](https://wordpress.org/support/users/lovingbro/)
 * Last activity: [5 months, 2 weeks ago](https://wordpress.org/support/topic/checkout-problems-6/#post-18695751)
 * Status: resolved