When clicking Place order produces no spinner, message or network request, the failure is usually in the browser before WooCommerce receives checkout data. Common causes include an invisible overlay, a disabled button, failed field validation, a JavaScript exception or custom code that prevents the submit event.
The visual symptom is similar in every case, but the evidence is different. Check what the click actually triggers before changing server or gateway settings.
Define what “nothing” means
Test once in a private window and note whether the button changes appearance, the page scrolls to a field, the browser console records an error or the Network panel sends a checkout request.
Also check recent WooCommerce orders and the gateway dashboard. A customer may describe “nothing” when the page failed after payment processing. Protect against duplicate charges before asking them to retry.
Check whether the button can receive the click
Inspect the button in developer tools. It should be visible, enabled and inside the checkout form. Use the element picker to see whether a cookie banner, loading mask, chat widget or transparent layout element sits above it.
/* Diagnostic only: do not leave this in production */
.suspected-overlay {
outline: 3px solid red;
pointer-events: none;
}Apply diagnostic CSS only in your own browser or staging. Permanently disabling pointer events can make consent or accessibility controls unusable.
Read the first browser error
Open Console, reload checkout and click once. Start with the first error generated after the page loaded. Later errors may be consequences.
Typical sources include checkout field plugins, theme scripts, address autocomplete, consent management and compressed JavaScript assembled by an optimisation plugin. A message naming jQuery, an undefined object or a blocked script gives a better lead than deactivating every extension.
Confirm whether Content Security Policy or a browser extension blocked a required file. Repeat in a clean browser profile before changing the store.
Inspect validation and required fields
WooCommerce may refuse submission because a required field is invalid, while CSS hides the error or scroll position. Inspect fields with aria-invalid="true" and error containers near the top of checkout.
Custom fields need a unique name, a valid value and matching server-side validation. Test addresses, phone formats and postcode rules appropriate to the selected country. Do not remove validation globally just to make one test pass.
Confirm the submit event and request
In Network, filter for checkout and click Place order. No request means the failure remains in layout, JavaScript or client validation. A request that returns an error belongs to a different path: inspect its status and response rather than the button.
If custom JavaScript handles the event, look for code that calls preventDefault() without later resuming checkout. Check conditional branches for payment methods or terms acceptance.
Isolate the responsible integration safely
Reproduce the store in staging with the same theme, checkout type and relevant data. Disable script combination first if generated bundles obscure the source. Then test one suspected extension or theme override at a time.
Changing to a default theme can prove the theme layer is involved, but it is not automatically the final repair. Identify the override or script conflict so the live design can remain intact.
Repair without weakening checkout
Correct the conflicting selector, event handler, overlay stacking, invalid field markup or script loading order. Restore any required consent, fraud or payment control after testing. Avoid snippets that force-enable the button continuously; they bypass symptoms and can permit incomplete orders.
Clear only the relevant asset cache and confirm the new file reaches an anonymous visitor.
Verify customer paths after the fix
Test guest and account checkout, each active payment method, mobile tapping, keyboard activation, terms acceptance and validation errors. A valid order should be created once, stock should change once and the gateway should show one matching transaction.
For recurring care, monitor front-end JavaScript errors and run a scheduled low-value checkout test after theme, WooCommerce, payment or optimisation updates. That catches a dead button before customers become the monitoring system.