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) 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:
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:
- 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.
- Temporarily switch to the Storefront theme and test again to rule out any theme-specific conflict.
- 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.
- 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!
Many thanks. The problem was detected on pagbank plugin. Created a new topic about this problem on plugin support.
Hi @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!
