Enabling Google/Apple Pay adds duplicate items to cart on variable products

Hello 4tcmedia,

Thank you for contacting WooCommerce support.

I understand you’re seeing double quantities added to the cart for variable products when using Apple/Google Pay on single product pages in a multisite setup. You’ve already identified the tokenized-express-checkout.js script as the trigger.

You did a great job narrowing that down. To troubleshoot this further, I’d like to reproduce the issue on my test site. Please share your site’s System Status Report by pasting it at https://pastebin.com and posting the link here, so I can match your settings.

Also, please enable the “Log error messages” option under WooCommerce > Settings > Payments > WooPayments. Any related logs will appear under WooCommerce > System Status > Logs. If you spot any relevant entries, share them via Pastebin as well.

Looking forward to your response. 🙂

Hello 4tcmedia,

Thank you for your reply.

I’ve reviewed the report, and everything looks fine here.

I see you’ve reactivated the plugins and are no longer using a default theme. To investigate further, please deactivate the plugins and switch to a default theme. If this isn’t possible on your live site, consider using a staging site instead.

I tried to reproduce the issue on my test site but couldn’t, which suggests the problem may be specific to your setup. Having a staging site will allow me to troubleshoot this issue more effectively.

Looking forward to your response. 🙂

Hi @4tcmedia,

Thanks again for the detailed information and for sharing the screen recording; it’s incredibly helpful. I also tried to test your store directly, but it looks like a valid postcode is required to access the products, so I wasn’t able to replicate the cart behavior myself.

From your video, it’s clear that enabling Apple/Google Pay leads to variable products being added to the cart with a quantity of 2, even when only one is selected. Disabling Apple/Google Pay or blocking the tokenized-express-checkout.js script stops this from happening, so it’s likely the issue stems from how that script interacts with your product page’s add-to-cart logic.

The tokenized-express-checkout.js script is part of the WooPayments integration that enables Apple and Google Pay functionality. It attaches event listeners to the page to handle express checkout actions, but in some cases, especially on product pages with variations, it might inadvertently duplicate click or form submission events. This could explain why clicking “Add to Cart” triggers the action twice, especially on a multisite sub-site, which may be rendering or initializing scripts slightly differently due to pathing or context.

To help narrow this down further, could you let me know:

• When exactly did this issue start happening? Was it after a recent update to the WooPayments plugin, WooCommerce, or WordPress?
• Is this a newly created multisite setup, or has it been running without this issue until recently?
• Do you have any custom JavaScript or child theme modifications that might interact with variation selection or add-to-cart actions?

While I wasn’t able to reproduce this issue on a standard WooCommerce site, your findings suggest that the bug may only manifest in multisite environments where the tokenized-express-checkout.js script might be triggering duplicate form submissions.

Let me know the answers to the questions above, and we can go from there.

Hi @4tcmedia ,

Thanks so much for reaching out—and I really appreciate you taking the time to dig into this.

I was able to reproduce the issue on your site, and I noticed that you’re using a theme called Adelaide Child. It doesn’t appear to be the default Twenty Twenty-Five theme, so it’s likely a custom or third-party theme.

Just to double-check—have you already tested the site with all plugins disabled except for WooPayment, as we suggested earlier? That step can help rule out any conflicts. If you’ve done that and the issue still shows up, especially after spotting the tokenized-express-checkout.js script causing errors, it’s worth checking whether a recent update triggered this.

You might want to try rolling back both WooCommerce and the Stripe Payment plugin to an earlier version to see if the problem goes away. A quick way to do that is by using the WP Rollback plugin, which lets you safely switch plugin versions right from your dashboard.

Let us know how that goes, and we’ll keep working through it with you!

Hello 4tcmedia,

Thank you for your reply.

You did a great job finding this trigger. To troubleshoot further, I recommend creating a clone of the site within the same Multisite setup, then deactivating all other plugins (except WooCommerce and WooPayments) and switching to a default theme. This will help us test the issue more effectively from our end.

Please share the URL when the clone site is ready.

Best regards.

• This reply was modified 1 year, 2 months ago by Zee. Reason: Rewrite

Hi @4tcmedia,

Thank you for the update and for clarifying your position. I completely understand your concern and your decision to focus on your business. That said, I’d like to clarify that we follow certain protocols when troubleshooting issues like this, one of which involves first isolating the issue within the merchant’s environment before attempting to replicate it on our end.

To ensure you get the support you need, a more effective approach—rather than stepping away—would be to submit the issue directly on GitHub: WooCommerce Payments GitHub Issues.
This allows the development team to take a closer look, and opens the door for other contributors to help replicate the issue or offer insights, which can also benefit others facing similar problems.

Thank you again for your time and effort so far. In the meantime, if you could spare a few moments to leave an honest review for the plugin, we’d really appreciate it—your feedback plays a key role in helping us improve: Leave a Review.