That single detail is why most search results for how to add PayPal to WooCommerce will waste your afternoon. The setup takes about fifteen minutes when you follow the current path, which uses a login-based connection rather than copied keys. This guide covers that path, what the sunset means if your store has run the same gateway since 2019, what each PayPal button actually costs you per sale, and the four errors that account for most failed setups.
To add PayPal to WooCommerce, install the official PayPal Payments plugin, go to WooCommerce > Settings > Payments > PayPal, and click Activate PayPal Payments. Log into your PayPal Business account in the popup. The plugin creates API credentials and registers webhooks automatically. No manual key entry is needed.
Table of Contents
The 2026 Change That Breaks Most Older Guides
PayPal Standard, the redirect gateway bundled with WooCommerce core for over a decade, is being retired. The bundled gateway stopped loading by default for new stores in WooCommerce 5.5, and the opt-in filter plus the gateway itself were removed entirely in WooCommerce 8.9 in May 2024. Only legacy configurations and workaround plugins have kept it alive since.
WooCommerce made the direction official in its PayPal Standard sunset advisory on June 24, 2026. The practical mechanism sits inside PayPal Payments 4.1.0, and it is worth understanding before you touch anything.
What version 4.1.0 actually does
Three behaviors, and they matter in this order:
- Updating the plugin alone changes nothing. If PayPal Standard runs alongside PayPal Payments today, the update leaves it exactly as it is.
- Connecting a PayPal account is the trigger. The moment a merchant account connects successfully, PayPal Standard is disabled and hidden from checkout. Customers see only the modern integration.
- Active subscriptions are protected. If your store has active or pending-cancel subscriptions still billing through PayPal Standard, the plugin detects them and leaves the old gateway in place. You get a notice saying how many are affected and where to find them.
There is no announced date after which PayPal Standard stops taking payments. WooCommerce has been explicit that an abrupt shutdown would break live stores. What stops is development: no new features, no enhancements, and no long-term support, on connection technology being phased out.
If your store still runs PayPal Standard
Run the Upgrade Readiness Tool before anything else. It sits in your WordPress admin, it is read-only, and it changes nothing. It reports which PayPal integration you are on, whether versions are current, known conflicts, and whether subscriptions need special handling. The WooCommerce documentation for the tool covers what each result means.
One caution from the field: sites running both gateways at once have produced checkout freezes and “unknown error while connecting to PayPal” failures, caused by conflicting API calls between the old and new integrations. If your checkout is misbehaving and you can see PayPal Standard in your payments list, that overlap is the first thing to check.
What You Need Before You Start
You need four things: WooCommerce on a current version, a PayPal Business account in a supported country, the official PayPal Payments plugin, and an SSL certificate on your checkout. You do not need API keys, a merchant ID, or a signature. The connection process generates all of that for you.
| Requirement | Why it matters | Common failure |
|---|---|---|
| PayPal Business account | Personal accounts are limited or unsupported for store checkout in most regions | Store owner connects a personal account, then finds card features unavailable |
| Current WooCommerce version | The plugin syncs with both WooCommerce and PayPal API releases | Old WooCommerce blocks plugin activation |
| SSL on checkout | PayPal will not process card fields over an insecure connection | Mixed content warnings kill the card form |
| Store currency PayPal supports | Currency mismatch fails at authorization, not at setup | Setup looks fine, live payments decline |
| Reference transactions enabled | Required for subscriptions and automated billing | Subscription renewals silently fail weeks later |
Reference transactions deserve attention because the problem surfaces late. Enabling them is a PayPal-side request that can take a day or two depending on account type and region. If you sell subscriptions, start that request before you build the checkout, not after. Our guide to PayPal recurring payment settings and fees covers how the billing side works once it is on.
If your PayPal Business account is new or unverified, sort that out first too. An unverified account can accept payments and then hold the funds, which is a bad surprise on your first live sale. Both confirming your identity on PayPal and knowing how to get PayPal money off hold are worth reading before launch rather than during a panic.
How to Add PayPal to WooCommerce: The Current Steps
The whole process runs through one plugin and one login popup. Install PayPal Payments, open the payments settings, click Activate PayPal Payments, and sign into PayPal in the window that opens. The plugin then creates a REST application in your PayPal developer account, retrieves credentials, and registers webhooks without you copying anything.
Step 1: Install the official plugin
In WordPress, go to Plugins, then Add New, and search for PayPal Payments. Install the one published by WooCommerce, not a third-party plugin with a similar name. Several exist and they are not interchangeable. Activate it.
Step 2: Open the PayPal setup
Go to WooCommerce, then Settings, then the Payments tab. PayPal appears in the gateway list. Click Set Up, or Manage if the extension is already active. Make sure you are opening PayPal, not PayPal Standard if a legacy entry is still visible.
Step 3: Connect your account
Click Activate PayPal Payments. A PayPal-hosted window opens. Sign in with your PayPal Business credentials, choose Business as the account type, and approve the permissions. If you want card payments without requiring a PayPal account, check the option to accept major credit and debit cards during this flow. That checkbox starts the eligibility review for Advanced Card Processing, and it can be changed later.
When the window closes, the connection is done. The plugin has created the REST application, stored the client ID and secret, and registered webhooks. This is the step every outdated guide replaces with copying an API signature.
Step 4: Configure what appears at checkout
The settings screen splits into tabs. The choices that change revenue are in the button and funding sections:
- Button placement. Enable PayPal buttons on product pages and the cart, not only at checkout. Express buttons earlier in the flow reduce steps.
- Funding sources. Turn off any funding source you do not want visible. Pay Later is the expensive one, covered in the fee section below.
- Intent. Capture takes the money immediately. Authorize holds it for later capture, which suits made-to-order or pre-order stores.
- Advanced Card Processing. If approved, enable it to replace the generic card button with dedicated card fields on your own checkout page.
Step 5: Test before you trust it
Enable sandbox mode in the plugin’s connection settings and create sandbox buyer and seller accounts in the PayPal Developer dashboard. Run a full purchase as a buyer, then check three things: the WooCommerce order status updated, the payment shows in the sandbox seller account, and the order confirmation email sent.
Then switch to live and run one real low-value purchase with your own card. Sandbox does not catch account-level problems like currency mismatch, unverified status, or a missing reference-transaction permission. A single $1 live test does.
What Each PayPal Button Actually Costs You
PayPal does not have one rate. It has a different rate for each way a customer can pay, and the spread between the cheapest and most expensive option on the same $60 order is more than three percentage points. Most store owners never look at this, then wonder why their effective processing cost runs above 4%.
| Payment method | US rate (2026) | Fee on a $60 order | Effective rate |
|---|---|---|---|
| Pay by Bank (ACH) | 1%, capped at $10 | $0.60 | 1.00% |
| Advanced Card Processing | 2.89% + $0.29 | $2.02 | 3.37% |
| Standard card via PayPal Checkout | 2.99% + $0.49 | $2.28 | 3.81% |
| PayPal wallet and Venmo | 3.49% + $0.49 | $2.58 | 4.31% |
| Pay Later | 4.99% + $0.49 | $3.48 | 5.81% |
US domestic rates compiled from PayPal’s published merchant fee schedule and cross-referenced against multiple 2026 rate trackers, checked August 2026. International commercial transactions add roughly 1.50 percentage points before any currency conversion spread. Confirm your own rate in your PayPal dashboard, since negotiated and volume rates exist.
Two things in that table surprise people.
The PayPal wallet costs more than a card. A customer clicking the yellow PayPal button costs you 3.49% + $0.49. The same customer typing a card number costs 2.99% + $0.49. You are paying half a percentage point extra for the convenience button, on every wallet sale.
The fixed fee dominates small baskets. That $0.49 is a small line on a $200 order and a brutal one on a $20 order, where it alone is 2.45% before the percentage rate applies. Stores with low average order values pay a much higher effective rate than the headline number suggests. If your basket sizes are small, this is the single biggest argument for looking at alternatives, which is the ground covered in our breakdown of how Stripe and PayPal fees compare.
The Advanced Card Processing break-even
Advanced Card Processing requires a PayPal review and approval, so store owners routinely skip it. Here is what skipping it costs. Against the standard card rate, Advanced saves 0.10% of the order plus $0.20 per card transaction.
| Average order value | Saving per card order | 100 card orders monthly | 400 card orders monthly |
|---|---|---|---|
| $25 | $0.23 | $23 | $92 |
| $50 | $0.25 | $25 | $100 |
| $100 | $0.30 | $30 | $120 |
| $250 | $0.45 | $45 | $180 |
Calculated from the published rate difference between Advanced Card Processing at 2.89% + $0.29 and standard card acceptance at 2.99% + $0.49, applied to card transactions only. Wallet payments are unaffected.
The pattern is clear once it is on a page. The saving is driven almost entirely by the fixed fee, not the percentage, which means transaction count matters far more than order value. A store doing 400 small card orders saves more than a store doing 100 large ones. If you process over roughly 100 card transactions a month, the approval paperwork pays for itself in the first month and every month after.
Pay Later is the other lever worth a decision rather than a default. At 4.99% + $0.49 it is the most expensive line on the page, and it is enabled by default. It earns its cost on high-consideration purchases where it lifts conversion, and it quietly destroys margin on low-priced repeat items. Our overview of PayPal Buy Now Pay Later explains what customers see on their side. If the maths does not work for your catalog, switch it off in the funding sources settings.
For the wider set of levers on what PayPal takes, see how to avoid PayPal fees when receiving money.
Four Errors That Cause Most Failed Setups
Setup failures cluster around four causes: leftover legacy gateways, credential confusion, currency and country mismatches, and webhook problems. Almost none are plugin bugs. Working through these in order resolves the large majority of “PayPal is not working on WooCommerce” cases.
1. Two PayPal gateways running at once. The classic symptom is a checkout that freezes after submission, or an unknown connection error. If PayPal Standard is still listed under Payments alongside PayPal Payments, the two integrations can issue conflicting API calls. Connecting your account through PayPal Payments 4.1.0 disables the legacy gateway automatically, which is the cleanest fix.
2. Manually entered credentials from the wrong era. If you followed an old guide and pasted an API Username, Password, and Signature, the connection will not behave. Those belong to the retired NVP and SOAP integrations. The current plugin uses a Client ID and Secret Key, and even those are only entered manually in rare cases. Disconnect and re-run the standard connection flow instead.
3. Currency or country mismatch. Your WooCommerce store currency must be one PayPal supports for your account’s country. This passes setup silently and fails at authorization, so it presents as random declines rather than a configuration error. Check store currency against your PayPal account country before assuming the plugin is broken.
4. Webhooks not registering. Order statuses that never update past Pending usually mean PayPal cannot reach your site. Staging environments behind HTTP authentication, aggressive security plugins, and firewall rules blocking PayPal’s IP ranges all cause this. Enable the plugin’s debug log, place a test order, and read what actually arrives.
If troubleshooting turns into a rebuild, our eCommerce launch security checklist covers the checkout-adjacent items worth verifying at the same time.
Should PayPal Be Your Only Gateway?
For most WooCommerce stores, no. PayPal earns its place as a trusted, familiar option that removes friction for buyers who dislike typing card numbers into unfamiliar sites. It is a weaker choice as the sole processor, because its wallet rate is above market and the $0.49 fixed fee punishes small baskets.
The common setup that works: PayPal Payments handles the wallet, Venmo, and Pay Later, while a second gateway handles direct card payments at a lower blended cost. You capture the trust benefit without routing every card sale through the more expensive path.
Three cases where PayPal alone is defensible. Very low transaction volume, where a second gateway’s setup effort outweighs the savings. High average order values, where the fixed fee is negligible. And stores whose audience skews heavily toward PayPal-first buyers, where checkout familiarity is worth more than the rate difference.
Three cases where it is not. Low average order values under about $30, where the fixed fee dominates. Heavy international sales, where the surcharge plus conversion spread compounds. And subscription businesses, where the reference-transaction dependency adds a failure mode you do not need. Choosing across the wider set of options is covered in how to choose payment methods for your store.
Frequently Asked Questions
How do I add PayPal to WooCommerce?
Install the official PayPal Payments plugin from the WordPress repository. Go to WooCommerce, then Settings, then Payments, and click Set Up next to PayPal. Click Activate PayPal Payments and sign into your PayPal Business account in the popup. The plugin creates credentials and registers webhooks automatically.
Do I still need PayPal API keys for WooCommerce?
No. The connection flow creates the REST application and retrieves the Client ID and Secret Key for you. Manual entry exists as a fallback, but the API Username, Password, and Signature that older guides describe belong to retired integrations and should not be used for a new setup.
Is PayPal Standard being removed from WooCommerce?
It is being retired. The bundled gateway was removed from WooCommerce core in version 8.9 in May 2024. As of PayPal Payments 4.1.0, connecting a merchant account disables and hides PayPal Standard automatically. No shutdown date has been announced, but the integration receives no new features or long-term support.
What happens to my subscriptions if I upgrade?
PayPal Payments 4.1.0 detects active and pending-cancel subscriptions still running on PayPal Standard and leaves the old gateway in place rather than disabling it. Existing subscribers keep getting billed. The plugin shows a notice with how many subscriptions are affected and where to find them.
How much does PayPal charge WooCommerce stores?
US domestic rates in 2026: PayPal wallet and Venmo at 3.49% + $0.49, standard card at 2.99% + $0.49, Advanced Card Processing at 2.89% + $0.29, and Pay Later at 4.99% + $0.49. International commercial transactions add roughly 1.50 percentage points before currency conversion.
Do I need a PayPal Business account?
Yes, for practical purposes. PayPal supports personal seller accounts in some regions, but a Business account is required for advanced card processing, invoicing, and most store features. Connecting a personal account is a common reason card options never appear in the settings.
Why is PayPal not showing at my WooCommerce checkout?
Check four things in order: the gateway is enabled in settings, your store currency is supported for your PayPal account country, no legacy PayPal Standard gateway is conflicting, and the connection status shows as connected. Caching plugins can also serve a stale checkout page after you enable it.
Can customers pay by card without a PayPal account?
Yes. Standard card acceptance shows a card button that opens a PayPal-hosted form. Advanced Card Processing, which requires PayPal approval, replaces that with card fields directly on your checkout page, so the customer never leaves your site. Advanced also carries the lower rate.
How do I test PayPal on WooCommerce safely?
Enable sandbox mode in the plugin and create sandbox buyer and seller accounts in the PayPal Developer dashboard. Run a full purchase and verify the order status, the sandbox seller balance, and the confirmation email. Then run one small live transaction, since sandbox does not catch account-level problems.
Why do my WooCommerce orders stay on Pending after PayPal payment?
This is almost always a webhook problem. PayPal cannot reach your site to confirm the payment, so the order never advances. Common causes are staging sites behind HTTP authentication, security plugins blocking the callback, and firewall rules. Enable the plugin’s debug log and place a test order to see what arrives.
Getting the Setup Right the First Time
The fifteen-minute version of this job only exists if you start from the current path. Follow a 2019 guide and you will spend an hour hunting for an API signature screen that PayPal has moved on from, then another hour wondering why the connection behaves oddly with two gateways fighting each other.
So the checklist is short. Use the official plugin. Connect by logging in, not by pasting keys. Run the readiness tool first if your store predates 2021. Test in sandbox, then test once for real. And before you launch, spend ten minutes on the fee table deciding which buttons deserve a place at your checkout, because that decision runs on every order from then on.
The setup is the easy half. The part worth revisiting each quarter is which payment methods you leave switched on, since PayPal enables the expensive ones by default and never asks again. When did you last check what your own checkout is costing you per sale?
