Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

WooCommerce Payment Settings Not Displaying: A Simple Guide

WooCommerce Payment Settings Not Displaying: A Simple Guide

Short answer

WooCommerce payment settings usually stop displaying because of a JavaScript error, a plugin or theme conflict, an outdated WooCommerce or gateway plugin, or missing permissions. Hard refresh first, try a private window, then check the browser console and test for conflicts on a staging copy before updating plugins.

Key takeaways

  • Browser extensions and ad blockers can break the Payments settings page.
  • The browser console often names the plugin causing a blank screen.
  • Use troubleshooting mode to test conflicts without affecting customers.
  • Gateways may hide if the store country or currency is unsupported.
  • Update WooCommerce and gateway plugins together after a backup.

Why are WooCommerce payment settings not displaying?

WooCommerce payment settings usually fail to display because of a JavaScript error, a plugin or theme conflict, an outdated WooCommerce or gateway plugin, or missing user permissions.

The symptom varies. Sometimes WooCommerce > Settings > Payments loads as a blank white area. Sometimes the list of gateways appears but a specific gateway's settings will not open. In other cases a gateway you installed simply is not listed.

Most of the time nothing is broken in your store data. Something is stopping the settings screen from loading properly, and you can find it with a few checks.

This guide works through the causes from quickest to most involved. If your issue is that payment options are missing on the checkout page rather than in the admin, see WooCommerce checkout not working instead.

What should you check first?

Reload the page with a hard refresh, try another browser or a private window, and confirm you are logged in as an Administrator or Shop Manager.

Quick first checks:

  1. Hard refresh the settings page to load fresh scripts.
  2. Open a private window to rule out browser extensions such as ad blockers.
  3. Check your role. Only users with the right capabilities can manage WooCommerce settings.
  4. Clear caches, including any cache plugin or server cache that might affect the admin.
  5. Look for admin notices at the top of the screen, such as a pending database update.

Ad blockers and privacy extensions are a surprisingly common cause. They can block scripts with names like payment or stripe, leaving the page half-loaded.

Is the new Payments settings page causing the issue?

Recent WooCommerce versions have been rebuilding the Payments settings screen, so the layout may look different and some gateways now open from new locations.

WooCommerce's developer team described the change in a post on modernizing the WooCommerce payments experience. The newer screen is built with React, which means it depends on JavaScript loading cleanly.

What this means for you:

  • Offline methods such as bank transfer, cheque and cash on delivery may be grouped in their own section rather than listed with other gateways.
  • Some gateways open their own settings screen when you click Manage or similar.
  • Older gateway plugins that have not been updated for the new screen may not appear correctly.

If you recently updated WooCommerce and the payments screen changed, look around the new layout before assuming settings are missing. Our WooCommerce payment settings explainer covers where each option lives.

How do you check for JavaScript errors?

Open your browser's developer tools on the Payments settings page and look at the Console tab for red error messages naming a plugin or script.

Steps:

  1. Open the Payments settings page.
  2. Press F12, or right-click and choose Inspect.
  3. Click the Console tab.
  4. Reload the page and note any red errors.

Errors often include a file path that names the plugin causing the problem, such as a folder inside wp-content/plugins. Google's guide to the Chrome DevTools Console explains how to read these messages.

If you see errors, note the plugin name. That is your strongest lead for the next step.

How do you find a plugin or theme conflict?

Test on a staging copy by switching to a default theme and deactivating all plugins except WooCommerce, then reactivate them one by one until the settings break again.

Conflicts are the most common cause of a blank or broken settings page. Admin tweak plugins, script optimizers and old gateway add-ons are frequent culprits.

The safe way to test is with the Health Check & Troubleshooting plugin. Its troubleshooting mode disables plugins and switches the theme only for your logged-in session, so customers are not affected.

Possible causeTypical signFix
Ad blocker or browser extensionWorks in private windowDisable or allowlist your admin
Optimization pluginMinified scripts in admin failExclude admin pages from optimization
Outdated gateway pluginOne gateway missing or blankUpdate or replace the gateway
Theme conflictFixed with a default themeUpdate theme or contact its developer
Pending database updateNotice at top of adminRun the WooCommerce database update
PHP errorBlank page, errors in logCheck debug log and PHP version

When you find the plugin that breaks the page, update it, check its support forum, or replace it.

Could an outdated plugin or WooCommerce version be the problem?

Yes, mismatched versions are a common cause, so update WooCommerce, your payment gateway plugins and your theme, after taking a backup.

Payment gateways rely on WooCommerce's internal APIs. When WooCommerce changes the settings screen, gateway plugins need updates to match. If one side is old, settings may vanish.

Check Dashboard > Updates and update in this order: back up, update WooCommerce, update gateways, then update the theme. Our guide on updating WooCommerce safely covers the process.

If WooCommerce shows a database update notice, run it. Until it finishes, some screens may not behave correctly. See WooCommerce database update required if it gets stuck.

Why is a specific gateway missing from the list?

A gateway may be missing because its plugin is inactive, it does not support your store's country or currency, or it needs to be set up through its own onboarding screen first.

Check these points:

  • Plugin active? Go to Plugins and confirm the gateway plugin is activated.
  • Country and currency. Some gateways only appear when your store address and currency are supported.
  • Onboarding required. Gateways such as WooPayments or Stripe may ask you to connect an account before showing full settings.
  • Separate menu. Some gateways place settings under their own menu item rather than in the Payments list.

Your store country and currency are set under WooCommerce > Settings > General.

For setup steps for popular gateways, see setting up Stripe in WooCommerce. PayPal users can follow our guide on setting up PayPal instead.

How do you check for server or PHP errors?

Turn on WordPress debug logging, reload the payments page and read the debug log, plus WooCommerce's own logs, for fatal errors or warnings.

On a staging site, add debug settings to wp-config.php so errors are written to a log file rather than shown to visitors. The WordPress guide to debugging in WordPress explains WP_DEBUG and WP_DEBUG_LOG.

Also check:

  • WooCommerce > Status > Logs for fatal error logs.
  • WooCommerce > Status for PHP version, memory limit and outdated template warnings. Our guide to the WooCommerce status report explains each section.
  • Your host's PHP error log.

A low PHP memory limit or an old PHP version can cause admin screens to fail. Your host can raise the limit or switch PHP versions.

What if payment settings save but do not stick?

If your changes disappear after saving, the cause is usually object caching, a security firewall blocking the save request, or a database permission issue.

Try these steps:

  1. Flush your object cache, such as Redis, from your cache plugin or host panel.
  2. Check whether a security plugin or web application firewall is blocking admin requests.
  3. Save again and watch the browser's Network tab for failed requests.
  4. Ask your host to check database errors if nothing else works.

Firewalls sometimes flag API keys or long secret values in form fields as suspicious. Temporarily allowlisting your IP for admin requests can confirm this.

When should you contact support?

Contact WooCommerce or your gateway's support when the settings still fail on a clean staging site with only WooCommerce and the gateway active.

Before you reach out, gather:

  • Your WooCommerce system status report
  • Console errors from the browser
  • Any fatal error logs
  • The steps that reproduce the problem

WooCommerce's support documentation explains how to collect this information. With these details, support can usually find the cause much faster.

Once your settings display again, place a test order to make sure payments work end to end before you leave it.

Frequently asked questions

Why is my WooCommerce Payments tab blank?

A blank Payments tab usually means a script failed to load. Common causes are browser extensions, optimization plugins minifying admin scripts, outdated gateway plugins or a theme conflict. Check the browser console and test in troubleshooting mode.

Where did bank transfer and cash on delivery go?

In newer WooCommerce versions, offline payment methods such as bank transfer, cheque and cash on delivery may appear in their own section of the Payments settings rather than in the main list of gateways.

Why can't a Shop Manager see payment settings?

Access depends on user capabilities. A custom role, a role editor plugin or a membership plugin may have removed the permission to manage WooCommerce settings. Check the role with an Administrator account.

Can a caching plugin hide WooCommerce settings?

Yes, if it caches or minifies admin pages. Most cache plugins skip the admin by default, but script optimization or a misconfigured object cache can interfere. Exclude admin pages and flush the cache.

Will deactivating plugins to test conflicts affect my live store?

Deactivating plugins on a live store can affect customers. Use a staging copy or the Health Check troubleshooting mode, which disables plugins only for your own logged-in session.

Sources

  1. Modernizing the WooCommerce payments experience: Technical changes ahead WooCommerce Developer Blog
  2. Health Check & Troubleshooting WordPress.org Plugins
  3. Debugging in WordPress WordPress Developer Resources
  4. Console overview Chrome for Developers
  5. WooCommerce Self-Service Guide WooCommerce

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.