Payment nonce is missing |

Hi @justinrogers,

Thanks for bringing this up. I can see how concerning it is when payments suddenly stop processing, especially when everything had been working previously. From what you described, it does look isolated to the Square gateway since Stripe is still able to process payments successfully.

The Payment nonce is missing or related Square.js errors usually point to an issue occurring during the tokenization step between the checkout page and Square’s API. This can sometimes happen due to a conflict on the checkout page, cached or outdated scripts, or a recent update affecting the Square integration.

To help narrow this down, please try the following checks:

1. Clear any site cache and CDN cache if one is in use, then test checkout again.
2. Temporarily deactivate all plugins except WooCommerce and WooCommerce Square, then switch to a default theme like Storefront or Twenty Twenty-Four, and test the checkout to see if the issue persists.
3. Make sure both WooCommerce and WooCommerce Square are fully updated to their latest versions.

If the issue still occurs after that, could you please share your System Status Report so we can take a closer look at the environment? You can get it from WooCommerce → Status → Get system report, then copy the report and share it using one of the following services: https://pastebin.com, https://quickforget.com or https://gist.github.com.

Also, if possible, please share a screenshot of the error or the browser console output using https://snipboard.io. Once we have that information, we will be able to investigate further and help pinpoint what might be causing the Square payment failure.

Hi @justinrogers,

Thank you for taking the time to run those tests and for sharing the System Status Report. It is helpful to see that you already tested with only WooCommerce, WooCommerce Square, and a default theme, which confirms this is likely not caused by a plugin or theme conflict on the checkout page.

The “Payment nonce is missing” message typically appears when the Square payment token is not generated correctly before WooCommerce attempts to process the payment. Since the console request to Square is returning a 400 Bad Request, it may indicate an issue with the Square connection or the tokenization step between the checkout form and Square’s API.

At this point, could you please try the following checks:

1. Go to WooCommerce → Settings → Payments → Square and disconnect the Square account, then reconnect it again to refresh the API authorization.
2. After reconnecting, navigate to WooCommerce → Status → Logs and enable Square logging if it is not already enabled. Then attempt another checkout and check if any Square related errors are recorded in the logs.
3. Confirm that the site URL in WordPress matches the domain configured in your Square application settings, as mismatches can sometimes prevent the nonce from being generated correctly.
4. Clear any server cache or CDN cache if one is in use, then reload the checkout page and test again.

The connection guide here can also help verify that everything is configured correctly: https://woocommerce.com/document/woocommerce-square/

If the issue still persists after reconnecting Square, please share the latest WooCommerce Square log from WooCommerce → Status → Logs using https://pastebin.com so we can take a closer look at what is happening during the request.

Also, if possible, please share a screenshot of the browser console errors using https://snipboard.io so we can review the exact response from Square during checkout.

Once we have that information, we can investigate further and help narrow down what might be preventing the payment nonce from being generated.

Hi @justinrogers,

Thanks for sharing the logs and the console screenshot.

Looking at the logs, woocommerce_square_gift_card_payment_token-is-missing-from-session suggests that attempting checkout may have had a Square Gift Card applied, and the gift card payment token wasn’t persisting correctly in the WooCommerce session. When that fails upstream, it can break the entire Square.js tokenization flow, which would explain why the nonce generation is failing and why Square’s verifications endpoint is returning a 404.

A couple of follow-up questions to help confirm this:

1. Was a Square Gift Card being applied at checkout? Is the gift card field visible/active on the checkout page by default? I did test this on my side and it works well.
2. Is Square Gift Cards enabled in WooCommerce → Settings → Payments → Square? If so, could you try temporarily disabling it and testing checkout with a regular credit card to see if the nonce error goes away?

Also, one thing caught our eye in the console screenshot, there’s a warning: State dropdown not found with ID: input_1_7_4. That input ID pattern is typically associated with Gravity Forms. Could you confirm whether Gravity Forms (or any add-on for it) was fully deactivated during your testing? Even a mu-plugin or helper that loads form assets could cause interference.

Finally, we noticed your active Square location is configured as type "MOBILE" in Square’s dashboard. While this shouldn’t block credit card processing outright, it can occasionally cause unexpected behavior with web-based gift card flows. It may be worth checking in your Square Dashboard whether the location is set up appropriately for online/eCommerce use.

As a quick test in the meantime: disable the Square Gift Card option (if enabled), clear all caches, and try a fresh credit card checkout, then let us know if that gets through cleanly. That’ll help us confirm whether the gift card session issue is the root cause here.

Looking forward to your response!