LovingBro (woo-hc)

Hi @tdw02d,

Thanks for sharing the screenshot, this helps clarify the issue. The “Bank” option you’re seeing is coming from Link by Stripe, which can enable bank account payments directly within the Stripe checkout experience, even when the standard WooCommerce bank transfer method is disabled.

At the moment, there is a known issue where disabling Link from WooCommerce → Settings → Payments → Stripe → Manage → Payment Methods does not always persist, and the setting may automatically re-enable itself after saving.

You can find more details here: GitHub issue #5468

In this case, the Link configuration may need to be disabled directly from the Stripe side by our development team.

Please contact us directly via: WooCommerce support contact form

While contacting us, include:

1. A link to this forum thread
2. The screenshot you shared
3. Confirmation that the Bank option is still appearing after disabling it in the Stripe settings

That will help the team disable the configuration lock for your account.

Hi @adammaly,

Thank you for sharing the detailed error log. I can see this started during the plugin update process, and the fatal error points to a missing file inside the Google for WooCommerce plugin package, specifically within the Google Ads PHP library files.

This can sometimes happen if the plugin update was interrupted or incomplete, leaving some vendor files missing after the update.

To help resolve this, could you please try the following:

1. Delete the current Google for WooCommerce plugin from Plugins > Installed Plugins, only the plugin, not WooCommerce itself.
2. Download and install a fresh copy of the latest version of the plugin from here:
   https://wordpress.org/plugins/google-listings-and-ads/
3. Clear any server, plugin, or CDN cache after reinstalling.
4. Then check if the fatal error still appears.

If the issue continues after a clean reinstall, please share your WooCommerce System Status Report using: WooCommerce > Status > Get system report > Copy for support. You can paste it using: https://pastebin.com or https://quickforget.com

That will help us check whether there may also be a server level or update related conflict involved.

Hi @ronbi13,

Thank you for sharing the details of what happened during the update. I can see why this would feel concerning, especially with the fatal error email appearing during the move from WooCommerce 10.7.0 to 10.8.0.

From what you shared, this looks like the update may not have completed cleanly at first, which can sometimes happen during plugin updates if files are temporarily missing or cached while the update process is running. Since your site is currently working, that is a good sign.

The database version showing as 10.8.0-2 is expected and is simply an internal database schema version used by WooCommerce. It does not always exactly match the plugin version number, so there is no issue there.

For the fatal error itself, the DefaultCustomerAddress class is part of WooCommerce 10.8.0, and the error suggests that during the update process, some files may not have been fully available at that moment.

To make sure everything is fully synced and complete, please try the following:

1. Go to Plugins → Installed Plugins and confirm WooCommerce is showing version 10.8.0.
2. Reinstall WooCommerce 10.8.0 manually over the existing installation. This will not affect your store data:
   https://woocommerce.com/document/how-to-update-woocommerce/
3. Clear all caches, including server cache, plugin cache, and CDN cache if applicable.
4. Go to WooCommerce → Status → Tools and run:
   • Clear template cache
   • Clear transients
   • Clear expired transients
5. Check if any additional fatal errors continue appearing after that.

If the issue returns after reinstalling, please share your System Status Report with us using: https://pastebin.com. You can get it from WooCommerce → Status → Get system report → Copy for support.

Please also let us know if the issue happened during an automatic update or a manual update.

Hi @hastibe,

From what we’ve been informed, this behavior came from a change on the Stripe platform side rather than from a WooCommerce plugin setting itself. Because of the configuration lock currently applied by Stripe, merchants who had previously disabled Link could still see it become active again.

At the moment, the main preventive measure is having the lock removed directly by our development team for affected accounts. Once removed, Link should remain disabled as expected.

As regards your question, by that time the underlying cause may already be fully resolved by Stripe, as this has been identified as a known issue and a bug report has already been filed with them.

We definitely appreciate you raising the impact this had on your store operations and customer experience, and I’ve shared that concern internally as feedback as well.

Hi @hastibe,

Thanks for bringing this to our attention. I can see how unexpected it would be to have orders showing as paid “via Link” after you had already disabled it in Stripe.

This is currently related to a known issue with the Stripe platform configuration. At the moment, there is a configuration lock on the Stripe side that prevents Link from being fully disabled through the WooCommerce Stripe settings, which is why the option may keep re-enabling itself after saving changes.

Our development team can remove this lock and disable Link directly for your account. To proceed with that, please contact us directly using the guidance shared in this GitHub comment: https://github.com/woocommerce/woocommerce-gateway-stripe/issues/5468#issuecomment-4533653879

Once the lock is removed, Link should no longer appear as an available payment method for your customers.

Hi @tdw02d,

Thanks for reaching out about this. If the bank payment method is still showing at checkout after disabling it, this is usually related to a cache issue or another plugin/theme overriding the available payment methods.

Please try the following:

1. Go to WooCommerce > Settings > Payments and confirm the bank payment method is disabled there.
2. Clear all caches on the site, including any caching plugin, server cache, and browser cache.
3. Temporarily deactivate all plugins except WooCommerce and the Stripe plugin, then switch to a default theme like Twenty Twenty Four and check if the payment method still appears.
4. If you are using Checkout block or any custom checkout plugin, test with the default WooCommerce checkout page as well.

If the issue continues after the above, please share:
– A screenshot of the payment settings page and checkout page using https://snipboard.io
– Your System Status Report via WooCommerce > Status > Get system report > Copy for support, then paste it to https://pastebin.com or https://quickforget.com and share the link here

That will help us take a closer look.

Hi @dazsmodels,

Thank you for the update and for testing that further. Since reinstalling Google for WooCommerce resolved the earlier issue, this new fatal error after updating to WooCommerce 10.8 appears to point to an incomplete or corrupted WooCommerce update, as the DefaultCustomerAddress class is part of WooCommerce core files.

Please try the following steps:

1. Reinstall WooCommerce 10.8 manually using a fresh copy from WordPress.org:
   https://wordpress.org/plugins/woocommerce/

You can do this by:
• Deactivating and deleting WooCommerce, while keeping the database and data intact
• Uploading and installing a fresh copy of WooCommerce 10.8

2. Clear all caching layers after reinstalling:
   • Plugin cache
   • Server cache
   • CDN cache
   • Browser cache
3. Go to WooCommerce → Status → Tools and run:
   • Clear template cache
   • Clear expired transients
4. After that, test again and let us know if the error still appears.

If the issue continues, please share your updated WooCommerce System Status Report via: https://pastebin.com or https://quickforget.com

You can find it under WooCommerce → Status → Get system report → Copy for support.

Hi @vasilisweb,

Thanks for reaching out with these thoughtful questions around HPOS. It’s great that you’re checking before making the switch, as that’s definitely the best approach.

Yes, when compatibility mode is enabled, WooCommerce keeps orders synced between the new HPOS tables and the legacy post tables. This helps older plugins continue working while you transition.

Before disabling compatibility mode, the main thing to check is whether all plugins that interact with orders are HPOS compatible. If a plugin still relies on the legacy order storage and is not HPOS compatible, it could stop working correctly once compatibility mode is disabled.

You can check this under WooCommerce > Settings > Advanced > Features, where WooCommerce usually shows plugin compatibility notices.

A few recommendations before switching fully to HPOS:
– Make sure WooCommerce, your theme, and all plugins are fully updated
– Test the change on a staging site first if possible
– Confirm that payment, shipping, invoicing, ERP, fulfillment, and reporting plugins support HPOS
– Keep compatibility mode enabled for a while if you are unsure about some plugins

In many cases, modern plugins already support HPOS, so merchants can switch without issues. But if an older plugin is not compatible, you may need to update it, contact the plugin author, or eventually replace/customize it.

You can also review the official HPOS documentation here:
https://woocommerce.com/document/high-performance-order-storage/

I hope this helps clarify things a bit.