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 PayPal Checkout Issues: A Simple Guide

WooCommerce PayPal Checkout Issues: A Simple Guide

Short answer

WooCommerce PayPal checkout issues usually come from a broken account connection, an unsupported currency, a script conflict or caching on the checkout page, or webhooks that never reach your site. Reconnect PayPal, test with other plugins off, exclude checkout from optimization and check the logs.

Key takeaways

  • Reconnecting the PayPal account fixes many failed payments.
  • Only run one PayPal gateway plugin at a time.
  • JavaScript delay and minify settings often break the PayPal button.
  • Orders stuck on pending usually mean the webhook was blocked.
  • WooCommerce logs show the real reason behind generic errors.

Why does PayPal checkout fail in WooCommerce?

PayPal checkout in WooCommerce usually fails because of a broken API connection, a mismatched currency or country, a script conflict on the checkout page, or a webhook that never reaches your site.

The tricky part is that the symptom often looks the same. The PayPal button vanishes, spins forever, or the customer pays and the order stays stuck on Pending payment.

This guide walks through each cause in order, from the quickest checks to the deeper ones. Most stores fix the problem in the first three sections.

Before you start, take a full backup and, if you can, copy the site to a staging site. Testing payment changes on a live store can confuse real customers.

SymptomLikely causeFirst check
PayPal button missingGateway disabled, currency not supported, script blockedPayment settings and browser console
Button spins or popup closesJavaScript conflict or cachingDisable optimization plugins
Something went wrong errorAPI credentials or merchant account issueReconnect the PayPal account
Paid but order is pendingWebhook not deliveredWebhook status in plugin settings
Card fields not showingAdvanced card processing not approvedPayPal account eligibility
Works in sandbox, not liveLive credentials missingConnection mode

Which PayPal plugin are you using?

Most stores today use the official WooCommerce PayPal Payments plugin, so start by confirming that is the one active on your site.

Older stores sometimes still run PayPal Standard or a legacy PayPal Checkout extension. These older gateways behave differently and are no longer the recommended route.

Go to WooCommerce > Settings > Payments and look at the list. If you see two PayPal gateways turned on, disable one. Two PayPal plugins loading their own scripts on the same checkout page is a common cause of broken buttons.

The official plugin is listed on WordPress.org, where you can check the latest version and the support forum for known issues.

If you have not set up the plugin properly yet, follow our guide on setting up PayPal in WooCommerce first, then come back here.

Is the PayPal account connected correctly?

A broken or expired connection between WooCommerce and PayPal is the most common reason payments fail, and reconnecting the account fixes it in many cases.

Open the PayPal Payments settings and look at the connection area. It should show that your account is connected in live mode, not sandbox mode.

If the store was set up by a developer, it may still be pointing to a sandbox (test) account. Sandbox buttons look normal, but real customers cannot complete a payment through them.

Try these steps in order:

  1. Note your current settings, such as button placement and payment methods.
  2. Disconnect the PayPal account inside the plugin settings.
  3. Reconnect using the onboarding button and sign in to your live PayPal business account.
  4. Place a small test order with a real card or PayPal account, then refund it.

Also log in to PayPal directly. If PayPal has limited your account, asked for verification, or not confirmed your email, payments can fail no matter what you do in WordPress.

Does PayPal support your store currency and country?

PayPal only shows its buttons when it supports the store currency and the buyer's country, so a currency mismatch can make the button disappear without any error.

Check WooCommerce > Settings > General and confirm the currency. If you use a multi-currency plugin, test checkout in each currency you offer.

Some payment methods inside PayPal, such as Pay Later or local methods, only appear in certain countries. A customer abroad may see fewer options than you do.

WooCommerce's own payment error troubleshooting page is a good reference for general gateway checks like this.

Is a plugin or theme conflict breaking the button?

When the PayPal button spins, flickers or opens a popup that closes at once, a JavaScript conflict from another plugin or the theme is the usual cause.

Open the checkout page, right-click, choose Inspect, and look at the Console tab, as described in the Chrome DevTools console docs. Red errors that mention PayPal, jQuery or a specific plugin file point straight to the problem.

To confirm a conflict, follow a standard plugin conflict test:

  1. Switch to a default theme such as Twenty Twenty-Five on staging.
  2. Deactivate every plugin except WooCommerce and PayPal Payments.
  3. Test checkout. If it works, reactivate plugins one by one until it breaks again.

Checkout field editors, one-page checkout plugins, custom checkout templates and popup plugins are frequent offenders. So are older themes that override WooCommerce templates.

If you recently switched between the checkout block and the classic shortcode, read our comparison of checkout blocks vs the shortcode. Some extensions only support one of them.

Are caching or optimization settings blocking PayPal scripts?

Speed plugins that delay, combine or defer JavaScript often break PayPal, because the PayPal SDK must load in a specific order on the cart and checkout pages.

Cart, checkout and account pages should never be cached as static pages. Most caching plugins exclude them by default, but custom rules and server caches sometimes do not.

Check these settings in your speed plugin:

  • Delay JavaScript execution: exclude PayPal scripts or turn it off on checkout.
  • Combine or minify JavaScript: exclude the PayPal SDK and plugin files.
  • Lazy load iframes: PayPal popups and card fields use iframes.
  • CDN or Cloudflare rules that cache HTML on checkout pages.

After any change, clear your cache at every level, including the plugin, the server and the CDN. Then test in a private browser window.

If you use WP Rocket, our guide to delay JavaScript exclusions explains how exclusions work.

Why is the order stuck on pending after the customer pays?

When a customer pays but the order stays on Pending payment, WooCommerce usually never received PayPal's confirmation, which is sent through a webhook.

A webhook is a message PayPal sends to your site to say the payment is complete. If your site blocks it, WooCommerce does not know the money arrived.

Common reasons the webhook fails:

  • A security plugin or firewall blocking requests from PayPal.
  • The site URL changed after the plugin was connected, for example after moving from HTTP to HTTPS.
  • A maintenance mode or password protection on the site.
  • Server errors that return a 500 response to PayPal.

The PayPal Payments plugin includes webhook status tools in its settings. The official PayPal Payments troubleshooting guide explains how to check and resubscribe webhooks.

Our separate guide on orders stuck on pending payment covers the WooCommerce side in more depth, including cron and Action Scheduler issues.

What do PayPal error messages mean?

Most PayPal checkout errors are generic on the front end, so the real detail is in the WooCommerce logs rather than in the message the customer sees.

Turn on logging in the PayPal Payments settings, then go to WooCommerce > Status > Logs. Pick the PayPal log file for the date of the failed order.

Error you might seeWhat it usually means
Something went wrong. Please try againGeneric API failure; check logs for the real reason
Instrument declinedThe buyer's card or funding source was refused
Payer action requiredThe buyer needs to complete an extra step, such as 3D Secure
Invalid currency or unsupportedStore currency or country not allowed for that method
Duplicate invoice IDThe order number was already sent to PayPal before

Duplicate invoice errors often appear when two stores share one PayPal account. Setting a unique invoice prefix in the plugin settings usually solves this.

For API level error codes, PayPal's developer Orders API troubleshooting reference lists what each code means.

Could the server or SSL be the problem?

Yes, an outdated PHP version, a broken SSL certificate or a server that cannot make outgoing HTTPS requests will stop PayPal from talking to your store.

Go to Tools > Site Health and look for critical issues. Our Site Health guide explains how to read the report.

Pay attention to these items:

  • The REST API encountered an error: PayPal Payments relies on the REST API.
  • Could not reach WordPress.org or other loopback failures: often a server firewall.
  • An old PHP version that the plugin no longer supports.
  • Mixed content warnings, where checkout loads some files over HTTP.

If Site Health shows REST API errors, fix those first. Our guide on the REST API error in Site Health walks through it.

You can also turn on WordPress debug mode on staging and reproduce the failed checkout. PHP errors during the payment request will then appear in the debug log.

How do you test PayPal checkout safely?

The safest way to test is in PayPal sandbox mode on a staging copy, then one small live order on the real store that you refund afterwards.

PayPal's sandbox lets you create fake buyer and seller accounts. Connect the plugin in sandbox mode on staging and run through every payment option you offer.

Test these cases:

  1. A logged-out guest buying one product.
  2. A logged-in customer with a saved address.
  3. A coupon or free shipping order.
  4. A subscription or pre-order, if you sell those.
  5. Mobile checkout on a real phone.

Then switch back to live mode on production. Our guide on testing WooCommerce payments has a fuller checklist.

When should you contact PayPal or WooCommerce support?

Contact support when your logs show account-level errors, your PayPal account is limited, or the problem continues with only WooCommerce and PayPal Payments active on a default theme.

WooCommerce support helps with the plugin itself. PayPal support handles account limits, verification, eligibility for card processing and disputes.

Before you contact either team, gather:

  • Your WooCommerce, PayPal Payments, WordPress and PHP versions.
  • The exact error message and the time it happened.
  • The relevant log entries with any personal data removed.
  • The System Status report from WooCommerce > Status.

This information usually cuts days off a support ticket.

While you wait, you can offer a second payment method so sales continue. Our guide on adding payment methods in WooCommerce shows the options.

Frequently asked questions

Why is the PayPal button not showing on my WooCommerce checkout?

The button is usually hidden because the gateway is disabled, the store currency is not supported, or a script is blocked by an optimization plugin or conflict. Check the payment settings, confirm the currency, and look at the browser console for JavaScript errors on the checkout page.

Why does my order stay on pending payment after PayPal payment?

WooCommerce did not receive PayPal's confirmation webhook. A firewall, security plugin, maintenance mode or changed site URL can block it. Check the webhook status in the PayPal Payments settings and resubscribe if needed, then confirm your site is reachable over HTTPS.

Can I use two PayPal plugins in WooCommerce?

It is best not to. Two PayPal gateways often load competing scripts on checkout, which breaks the buttons or creates duplicate payment options. Pick the official PayPal Payments plugin and deactivate older PayPal Standard or legacy checkout extensions.

How do I see the real PayPal error in WooCommerce?

Turn on logging in the PayPal Payments settings, reproduce the problem, then open WooCommerce, Status, Logs and choose the PayPal log for that date. The log shows the API response, which is far more specific than the message customers see.

Does caching break PayPal checkout?

It can. Caching the cart or checkout page, or delaying and combining JavaScript, can stop the PayPal SDK from loading correctly. Exclude checkout pages and PayPal scripts from optimization, clear every cache layer and test again in a private window.

Sources

  1. WooCommerce PayPal Payments troubleshooting WooCommerce
  2. WooCommerce PayPal Payments plugin WordPress.org
  3. Troubleshoot payment errors WooCommerce
  4. Orders API troubleshooting PayPal Developer

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.