Payment plugins are not a category where we would choose the product with the longest feature list.
The gateway sits directly in the path between a customer deciding to buy and the store receiving money.
That makes reliability, payment-method coverage, recurring-payment support, refunds, saved payment methods, checkout compatibility, and operational clarity more important than a long list of secondary features.
It also means there is no universal "best payment plugin" for every WooCommerce store.
A European store that needs iDEAL and Bancontact has a different requirement from a US retailer already using Square at physical locations. A subscription business has different priorities from a store that only takes one-off payments. An established business with an Authorize.Net merchant account may have little reason to rebuild its payment stack around something newer.
For a typical new WooCommerce implementation, Stripe is my first choice, with PayPal second when customers specifically want it. This is a preference shaped by running real stores, not a claim that every business needs both gateways.
That recommendation is based on hands-on WooCommerce work, not only product-page research. We have used Stripe for normal card payments, Apple Pay, Google Pay, Link, saved payment methods, refunds from WooCommerce, subscription renewals, failed renewals, payment-method changes, and the webhook/error handling that comes with running recurring-payment stores.
But Stripe is not automatically the right answer for every merchant.
Last researched: 2 October 2026.
A note on our experience: Stripe and PayPal are gateways we have worked with repeatedly. We have also used Mollie and Klarna on individual stores. Our Authorize.Net experience is older, so we treat its current 2026 implementation primarily as a research-based recommendation. WooPayments and Square are included from current documentation, compatibility, maintenance, and product-scope research rather than fresh hands-on testing.
The Short Version
| Plugin | Best for | Subscriptions | Blocks / HPOS | Plugin cost |
|---|---|---|---|---|
| Stripe for WooCommerce | Best starting point for most stores | Yes | Yes / Yes | Free |
| WooPayments | Best for payments managed closely inside WooCommerce | Yes | Yes / Yes | Free; transaction fees |
| PayPal Payments | Best when customers expect PayPal | Yes | Yes, with some block feature differences / Yes | Free |
| Mollie Payments | Best for European and local payment methods | Yes, for supported methods | Check current implementation for your required flow | Free |
| Square for WooCommerce | Best for stores selling online and in person | Yes | Yes / Yes | Free |
| Authorize.Net | Best for established Authorize.Net merchants | Yes | Yes / Yes | $79/year for the established SkyVerge extension |
This is not a strict ranking of all six gateways. My practical preference for most online stores is Stripe first, PayPal second. The remaining options solve different business needs.
The more useful question is:
Which payment stack covers the ways your customers need to pay, with the fewest moving parts?
For many stores, that may be Stripe alone. I have also seen merchants choose not to add PayPal because Stripe already covers their card and wallet checkout needs.
For others, Stripe plus PayPal makes sense. A European merchant may find Mollie covers the local methods it actually needs. A retailer already operating Square POS has a strong reason to evaluate Square before introducing a separate online payment stack.
What We Look for in a WooCommerce Payment Plugin
A payment gateway needs to do more than successfully process a test order.
For a production WooCommerce store, we care about:
- merchant availability — can the business actually open an account in its country?
- customer payment methods — cards, wallets, bank methods, BNPL, and relevant local options,
- Checkout Blocks support — including the specific payment flows the store intends to use,
- HPOS compatibility — now part of the normal modern WooCommerce baseline,
- WooCommerce Subscriptions support — when automatic recurring billing matters,
- saved payment methods and tokenization,
- Apple Pay and Google Pay where appropriate,
- refunds and captures from WooCommerce,
- webhook and error visibility,
- maintenance and current WooCommerce compatibility,
- documentation and support,
- fees in the merchant's actual country and currency.
That last point is important.
Payment pricing is highly regional. International cards, currency conversion, disputes, local payment methods, BNPL, and merchant location can all change the real cost.
We would not choose a gateway from a generic "2.9% vs 2.7%" comparison without calculating the store's actual payment mix.
1. Stripe for WooCommerce — Best Starting Point for Most Stores
Stripe for WooCommerce is the payment integration we would evaluate first for most new WooCommerce stores where Stripe is available.
The official Marketplace extension currently reports 700,000+ active installs, supports Cart and Checkout Blocks, HPOS, and WooCommerce Subscriptions, and offers Link, Apple Pay, and Google Pay alongside cards and a growing set of alternative payment methods.
That feature list is useful.
Our reason for putting Stripe first is more practical.
Our experience with Stripe in WooCommerce
Stripe is the gateway we encounter most often in current WooCommerce work.
We have used it for:
- standard card payments,
- Apple Pay,
- Google Pay,
- Link,
- saved cards and payment tokens,
- WooCommerce Subscriptions,
- automatic renewal payments,
- failed renewal handling,
- customers changing payment methods,
- refunds initiated from WooCommerce,
- webhook-driven payment events,
- troubleshooting payment errors.
In our experience, this is a mature WooCommerce payment stack.
When something goes wrong, the combination of WooCommerce order notes/logging and Stripe-side payment information usually gives you something concrete to investigate rather than leaving the order in an unexplained state.
We have also worked on stores that offer PayPal for one-off purchases but intentionally keep subscription payments on Stripe. Keeping the recurring-payment path narrow can make subscription operations easier to reason about.
That is an operational preference, not a rule every store needs to follow.
More than card processing
The current Stripe extension includes wallet and alternative-payment support that can reduce the need to install a separate plugin for every payment brand.
Its Marketplace listing currently highlights:
- Link,
- Apple Pay,
- Google Pay,
- Klarna,
- Afterpay/Clearpay,
- Affirm,
- Bancontact,
- Alipay,
- WeChat Pay.
Availability depends on merchant country, customer location, currency, account eligibility, and the payment method itself.
So "Stripe supports Klarna" does not mean every Stripe merchant can simply switch it on for every order.
Subscriptions are a major strength
For subscription stores, gateway compatibility matters well beyond the first checkout.
You need to think about:
- automatic renewals,
- saved payment methods,
- failed payments,
- customer payment-method changes,
- Strong Customer Authentication where applicable,
- renewal retries,
- webhook delivery.
Stripe's WooCommerce Subscriptions support is one of the main reasons we are comfortable using it as the payment foundation for recurring stores.
Where Stripe makes the most sense
We would start here when:
- Stripe supports the merchant's country,
- cards are the primary payment method,
- Apple Pay / Google Pay / Link are useful,
- subscriptions are important,
- the merchant wants a direct Stripe relationship,
- the store may need additional Stripe-supported payment methods later.
Where it may not be the best fit
Stripe is less compelling when the merchant's business is already deeply built around another processor.
A physical retailer running Square, for example, may value unified inventory and POS operations more than switching online payments to Stripe.
A European store whose customers strongly prefer a collection of country-specific payment methods may find Mollie's positioning more natural.
Best for: most new WooCommerce stores that want a mature general-purpose payment stack, especially when subscriptions and digital wallets matter.
Our current default: Stripe is the first gateway we would evaluate.
2. WooPayments — Best for Managing Payments Inside WooCommerce
WooPayments takes a different approach.
Instead of treating the payment processor as a mostly separate system connected to WooCommerce, WooPayments puts payment operations directly into the WooCommerce admin experience.
It is built by Woo and uses payment infrastructure provided through Stripe, but it should not be treated as simply another name for the normal Stripe plugin.
The operational model is different.
Why merchants choose WooPayments
WooPayments can handle:
- card payments,
- saved cards,
- Apple Pay,
- Google Pay,
- Link by Stripe,
- WooPay,
- Amazon Pay,
- eligible BNPL methods including Klarna, Affirm, and Afterpay/Clearpay,
- regional payment methods including iDEAL/Wero, Bancontact, EPS, Multibanco, and others.
Not every method is available in every country.
WooPayments itself is also restricted to supported merchant countries, although the list is now broad and includes the United States, United Kingdom, Australia, Canada, Romania, and many EU markets.
The integrated admin experience is the real selling point
The main reason to choose WooPayments over the direct Stripe extension is not that one can process a Visa card and the other cannot.
It is the workflow.
Payments, deposits, disputes, transaction details, and related payment administration are designed to live closely inside WooCommerce.
For a merchant who wants to operate the store primarily from WordPress rather than moving between WooCommerce and a separate processor dashboard, that can be attractive.
Subscriptions support
WooPayments supports WooCommerce Subscriptions.
Current documentation notes that cards and supported express-checkout methods can be used for automatic subscription renewals, while not every alternative payment method that works for a one-off order can be used for recurring billing.
That distinction matters.
A gateway saying "supports subscriptions" does not mean every payment method exposed by that gateway can automatically renew a subscription.
WooPayments vs Stripe
This is one of the more useful comparisons in the payment category.
Choose WooPayments when the WooCommerce-native management experience is the priority.
Choose the direct Stripe for WooCommerce integration when you specifically want the direct Stripe relationship and Stripe-centric operational workflow.
We have substantially more hands-on experience with the latter, so we would not pretend these two options have been equally tested by us.
Best for: merchants who want a payment system tightly integrated into WooCommerce administration and whose country and payment requirements are supported.
3. PayPal Payments — Best When Your Customers Expect PayPal
PayPal Payments for WooCommerce is the current official PayPal integration for WooCommerce.
It reports 800,000+ active installs and supports WooCommerce Subscriptions, HPOS, and the modern block checkout architecture, although the current Blocks documentation still lists differences between supported payment flows.
Depending on merchant and customer eligibility, the extension can expose:
- PayPal,
- cards,
- Pay Later,
- Venmo in the US,
- Apple Pay,
- Google Pay,
- other regional payment options.
PayPal is no longer automatically mandatory
There was a period when adding PayPal to an ecommerce store felt almost automatic.
Our recent WooCommerce work is different.
We still encounter and use PayPal, but Stripe has increasingly become the default payment foundation in the stores we work on. Some merchants are now comfortable launching with Stripe and wallets without adding PayPal at all.
That is our client experience, not a claim that PayPal demand has disappeared globally.
The reason to add PayPal should be straightforward:
your customers want to pay with PayPal.
If they do, the PayPal button can be valuable even when Stripe already handles cards.
It can complement Stripe rather than replace it
We do not think every payment decision needs to be framed as Stripe versus PayPal.
A common stack can simply be:
- Stripe for cards, wallets, and recurring billing,
- PayPal for customers who specifically prefer their PayPal account.
That keeps the roles clear.
On subscription stores we manage, we prefer allowing automatic recurring payments through Stripe even when PayPal is available elsewhere in the store. Again, that is an operational choice rather than a requirement of WooCommerce.
Check the exact Blocks flow you need
PayPal's current documentation supports Block Cart and Block Express Checkout functionality, Advanced Card Processing, Pay Later messaging, and several other block-based flows.
It also documents some differences and unsupported combinations.
That is a good example of why we do not stop at a "Cart & Checkout Blocks compatible" badge when reviewing payment gateways.
Test the exact flow your store uses.
Best for: stores where PayPal itself is an important customer payment preference, often alongside a primary card processor.
4. Mollie Payments — Best for European and Local Payment Methods
Mollie Payments for WooCommerce is the option in this list we would look at especially closely for European stores.
The current Marketplace listing reports 100,000+ active installs.
Mollie's strength is the breadth of regional payment methods it can bring into one integration.
Current options include methods such as:
- iDEAL,
- Bancontact,
- Cartes Bancaires,
- EPS,
- Przelewy24,
- cards,
- Apple Pay,
- PayPal,
- Klarna.
The exact methods available depend on country, account, and transaction context.
Why local payment methods matter
Payment preferences are regional.
A checkout built around what is common in the United States can be a poor fit for customers in the Netherlands, Belgium, Poland, or other European markets.
That is where Mollie's positioning becomes more interesting than simply comparing card-processing rates.
Instead of installing a collection of unrelated integrations, a merchant can manage several relevant European payment methods through one payment provider.
Our experience
We have used Mollie on one WooCommerce store.
That is enough for us to classify it as hands-on experience, but not enough to pretend we have the same operational depth with Mollie that we have with Stripe.
Our recommendation here therefore combines that limited real-world exposure with current product research.
Subscriptions require method-level checking
Mollie supports WooCommerce Subscriptions for supported recurring methods.
Its current Marketplace information specifically references recurring support involving cards, iDEAL, and SEPA Direct Debit, but recurring-payment behavior can depend on the initial payment method and mandate setup.
If subscriptions are central to the business, verify the exact customer payment method you intend to offer — not merely whether the plugin appears on a WooCommerce Subscriptions compatibility list.
Refunds and payment management
Mollie supports full and partial refunds and provides its own dashboard for payment management and reporting.
For merchants already using Mollie elsewhere, keeping WooCommerce inside that same payment operation can be a stronger reason to choose it than any generic feature comparison.
Best for: European WooCommerce stores that need a strong mix of cards, wallets, and country-specific payment methods.
5. Square for WooCommerce — Best for Online + In-Person Retail
Square for WooCommerce earns a place in this roundup for a reason that goes beyond online card processing.
It connects WooCommerce to the Square ecosystem used by physical retailers.
The extension currently reports 80,000+ active installs and supports Cart and Checkout Blocks, HPOS, and WooCommerce Subscriptions.
Square currently lists merchant availability in the United States, Canada, Australia, Japan, United Kingdom, France, Spain, and Ireland.
The real advantage is omnichannel operations
Square can act as a WooCommerce payment gateway, but the more interesting capability is synchronization between online and physical selling.
Current WooCommerce documentation covers synchronization of:
- products,
- inventory,
- orders,
- customer information.
The payment integration can also support cards and digital-wallet options including Apple Pay and Google Pay.
If a merchant already takes payments through Square POS, this changes the gateway decision.
The question is no longer:
"Is Square a better online card processor than Stripe?"
It becomes:
"Can Square reduce the operational gap between our physical shop and WooCommerce?"
That is a much stronger use case.
Why we would not choose it for everyone
We have not used the current Square integration hands-on, so this recommendation is based on current WooCommerce documentation and product scope.
For a pure online store with no Square ecosystem, we would normally start our evaluation with Stripe or WooPayments instead.
Square becomes compelling when the merchant already uses — or intends to use — Square for in-person commerce.
Best for: retailers that want WooCommerce and physical Square operations to work as one connected commerce setup.
6. Authorize.Net — Best for Established Authorize.Net Merchants
Authorize.Net for WooCommerce represents a different part of the payment market.
It is not the gateway we encounter most often on new WooCommerce builds today.
But that does not make it irrelevant.
There are established businesses with existing Authorize.Net merchant setups, processing relationships, customer profiles, and operational processes. For those stores, "move to Stripe because it is newer" is not automatically useful advice.
The established SkyVerge WooCommerce extension currently costs $79/year, reports 30,000+ active installs, and supports WooCommerce Subscriptions, Cart and Checkout Blocks, and HPOS.
It includes capabilities such as:
- credit-card processing,
- eChecks,
- saved payment methods,
- tokenization,
- refunds and voids from WooCommerce,
- capturing previously authorized transactions,
- subscription payments.
Our experience here is historical
We used Authorize.Net much more frequently roughly a decade ago.
At that time it was a common part of the ecommerce payment landscape we worked with.
We do not encounter it nearly as often in new builds now.
For that reason, we are not presenting our old experience as proof of how the current extension behaves in production in 2026. The current recommendation is based primarily on the present WooCommerce integration and documentation.
A specific Blocks caveat
The current Authorize.Net documentation says the gateway supports Cart and Checkout Blocks.
However, it also notes that Apple Pay is not currently compatible with the Cart and Checkout Blocks implementation, even though Apple Pay can be used with the shortcode checkout.
This is exactly the kind of detail worth checking before changing a live checkout architecture.
"Blocks compatible" can describe the gateway overall while a particular payment feature still has a limitation.
When Authorize.Net makes sense
We would consider it when:
- the merchant already has an Authorize.Net account,
- existing business processes depend on it,
- saved customer payment profiles matter,
- eCheck support is useful,
- WooCommerce Subscriptions is required,
- migrating processors would create more work or risk than value.
For a brand-new small WooCommerce store with no existing processor relationship, it would not be our first gateway to investigate.
Best for: established merchants already invested in Authorize.Net and its merchant-account ecosystem.
What About Klarna, Braintree, and Other Gateways?
Six products cannot represent the entire payment market.
We have used Klarna on a WooCommerce store, but we did not give a dedicated Klarna plugin one of the six places because Klarna can now be reached through broader payment stacks.
Stripe supports Klarna for eligible transactions. WooPayments offers Klarna in supported markets. Mollie can also expose Klarna.
If Klarna is strategically important to your business, compare those routes with the dedicated Klarna integration and check the exact merchant country, currency, product, subscription, and checkout requirements.
The same principle applies to other gateways.
Braintree, Adyen, regional bank integrations, and country-specific processors can be the right answer when the business requirement points there.
This roundup is not an argument that every WooCommerce store should consolidate onto these six providers.
Payment Plugins and WooCommerce Subscriptions
Subscriptions deserve their own payment-gateway checklist.
A gateway working for a normal WooCommerce order does not automatically mean it supports every recurring operation you need.
Before launching subscriptions, verify:
- Can the gateway perform automatic renewal payments?
- Can customers save/tokenize the required payment method?
- Can a customer change the payment method attached to a subscription?
- What happens after a failed renewal?
- Does the gateway support the store's retry workflow?
- How are Strong Customer Authentication requirements handled?
- Do refunds work from WooCommerce?
- Are webhook failures visible and recoverable?
- Does the specific wallet or local payment method support recurring charges?
We have seen this distinction matter in real subscription operations.
For stores where recurring billing is business-critical, I prefer Stripe for subscriptions even when PayPal is enabled for ordinary purchases. A predictable renewal and troubleshooting workflow is more valuable to me than offering every available gateway for recurring payments.
Checkout Blocks and HPOS: Check Features, Not Just Badges
Modern WooCommerce compatibility now has two obvious checks:
- HPOS
- Cart and Checkout Blocks
But they are not identical compatibility problems.
HPOS concerns how order data is stored and accessed.
Checkout Blocks change the checkout architecture and the way extensions integrate with the front end.
A gateway can declare Blocks compatibility while still documenting limitations for a particular express wallet, tokenization path, or subscription flow.
Before changing a live store to Checkout Blocks, test:
- normal card checkout,
- guest checkout,
- logged-in checkout,
- saved payment methods,
- Apple Pay,
- Google Pay,
- PayPal/express buttons,
- subscription signup,
- renewal behavior,
- failed payments,
- coupons,
- refunds,
- any custom checkout fields.
Payment is not the place to assume that a compatibility badge means every edge case has been covered.
How We Would Choose a Payment Stack in 2026
For a typical new WooCommerce store, we would start with Stripe and add another gateway only when there is a clear customer or operational reason.
For a merchant that wants payment administration centered inside WooCommerce, WooPayments deserves a direct comparison with Stripe.
If customers actively use PayPal, add PayPal Payments rather than forcing those customers through cards.
For a European business with important local payment methods, evaluate Mollie early rather than designing the checkout around US-centric assumptions.
For a retailer already selling through Square in physical locations, Square for WooCommerce may solve an operational problem that a standalone online gateway does not.
And if an established business already has an Authorize.Net setup that works, Authorize.Net remains a legitimate WooCommerce option. There is no prize for migrating a stable payment operation merely because another processor is more fashionable.
The goal is not to install the most gateways.
It is to build the smallest reliable payment stack that covers how your customers actually pay.
Final Take
If I were launching a normal WooCommerce store today, Stripe would be my first choice and PayPal my second, when there is real customer demand for PayPal. For subscriptions, I would stick with Stripe.
That conclusion comes from both the current integration and our experience running Stripe through the less glamorous parts of ecommerce: saved payment methods, subscription renewals, failed payments, refunds, webhooks, and troubleshooting.
But payment gateways are unusually dependent on context.
WooPayments offers a more WooCommerce-centered operational experience.
PayPal still matters when customers specifically want PayPal.
Mollie is particularly interesting for European and local payment methods.
Square makes the strongest case when online and physical retail need to meet.
Authorize.Net remains relevant for established merchants already built around it.
Choose based on the merchant's country, customers, recurring-payment needs, existing processor relationships, and exact checkout architecture.
Then test the payment flows on staging before changing a live checkout.
Because with payment plugins, "compatible" is the starting point.
A successful real order — and a clean refund, renewal, failure, and recovery path — is what actually matters.
Pricing, availability, payment methods, transaction fees, and compatibility can change by country and over time. Verify the current provider and WooCommerce documentation for your merchant account before making a payment-platform decision.
