Best Payment Gateways for WooCommerce (2026): Fees, Features & Merchant Fit

StackScale independent buyer’s guide · Reviewed 20 October 2026 · U.S. reference pricing unless otherwise stated

The best payment gateway for WooCommerce is the one that supports your merchant country, payment methods and operating workflow at a sustainable total cost. A low advertised card rate is useful, but it is not enough: account ownership, subscription renewals, refunds, inventory synchronization and the ability to leave the provider may matter just as much.

Quick answer: which WooCommerce payment gateway should you shortlist?

WooPayments is a sensible starting point for a store that wants payments managed through WooCommerce. Stripe for WooCommerce is attractive when the business already has a standalone Stripe account or needs Stripe’s broader account and API workflow. PayPal Payments is often a complementary checkout option, not necessarily the replacement for your main card gateway. Square deserves a look when the same merchant sells online and in person. Authorize.net is primarily worth assessing if you need its gateway-and-merchant-account model, particularly if you already have processing arrangements.

These are recommendations by fit, not a claim that StackScale ran benchmark tests or measured conversion performance. We assessed published product documentation, fees, supported workflows and the questions a WooCommerce merchant must resolve before going live. All prices and availability should be confirmed against your own business location and contract.

Editorial and affiliate disclosure: StackScale researches software independently. Some links may earn us a commission at no additional cost to you; commercial relationships do not determine our comparisons. Official provider resources are linked throughout.

At a glance: five WooCommerce payment options

Gateway / integrationBest starting use caseAccount and administrationImportant limitation
WooPaymentsWooCommerce-first store seeking native payment managementPayment and reporting tasks in WooCommerce; WooPayments accountEligibility varies by country; not the same account model as regular Stripe
Stripe extensionExisting Stripe account, API or cross-channel requirementsStandalone Stripe account plus WooCommerce extensionConfiguration, extra products and region-dependent payment methods need validation
PayPal PaymentsOffer PayPal wallet, Venmo or eligible Pay Later choicesPayPal Business account connected to WooCommerceDifferent funding methods and products have different fees
SquareMerchant combining online checkout with physical POSSquare account plus configurable WooCommerce inventory/order syncSupported merchant countries and synchronization behavior are constrained
Authorize.netBusinesses seeking gateway-only or merchant-account choicesAuthorize.net gateway; separate merchant account on gateway-only planMonthly gateway fee, possible extension charges and processor fees

It is not always a winner-takes-all choice. A merchant might process its standard cards with WooPayments or Stripe and offer PayPal alongside. The correct comparison is the incremental value and costs of each method, not a false assumption that each integration must exclusively handle every checkout.

How we evaluated the gateways

Our shortlist starts with active WooCommerce integrations and published merchant documentation. We prioritized the practical questions a buyer can check: supported countries and currencies; core and alternative payment methods; headline pricing and hidden billing units; refunds and dispute workflows; recurring payments; dashboard reporting; saved payment method portability; compatibility with WooCommerce’s cart and checkout blocks; and what happens when the merchant wants to switch providers.

These five choices cover distinct common merchant situations rather than exhaust every provider in every country. Stores selling mainly in continental Europe should also investigate regionally strong options such as Mollie or relevant domestic payment methods. We have not ranked them here because localized contracts, settlement currencies and payment-method availability require a different market-specific analysis.

Before comparing fees: confirm your legal business country, expected settlement currency, average order value, and whether you sell subscriptions. A gateway’s acceptance of a customer card issued in another country is not the same as its willingness to onboard a merchant in your country.

WooPayments: best starting point for WooCommerce-centered operations

WooPayments is designed around the WooCommerce merchant dashboard. Merchants can see transactions, payouts, balance activity and fee reports without making an external payments dashboard their primary workflow. For a small team that handles fulfillment, refunds and finance from WordPress, reducing administrative context switching can be a practical advantage.

U.S. standard online card pricing is currently 2.9% + $0.30 per payment, with an additional 1.5% for international cards and 1% where currency conversion applies. WooCommerce publishes country-specific schedules, which can differ substantially from those U.S. numbers. It also lists a $15 U.S. dispute fee for cards. The standard online payment setup has no recurring WooPayments gateway subscription charge, but that does not imply that optional software, services or payment methods are free. See WooPayments’ official fee schedule.

Where WooPayments fits especially well is a merchant launching its first payment integration without complex pre-existing Stripe workflows. Its limits matter, too: accounts and payment credentials are not automatically portable to the standalone Stripe extension, despite the technology relationships between the products. International acceptance and payment method eligibility also depend on the merchant’s country.

Read the dedicated WooPayments Pricing analysis for refunds, extra charges and detailed U.S. calculations. This guide addresses its place in the broader gateway selection decision.

Stripe for WooCommerce: flexible account and payment ecosystem

The official Stripe extension connects WooCommerce to a regular Stripe account. This matters to businesses that already use Stripe for another website, invoicing workflow, marketplace or custom application: the organization may want a single account administration and developer-access structure rather than a separate WooPayments account model.

Stripe’s published standard U.S. domestic card rate is also 2.9% + $0.30. The standard rate adds 1.5% for an international card and 1% if currency conversion is needed. Stripe offers many regional alternatives, but pricing, eligibility and plug-in support are not uniform across every method. Its own documentation describes cards, digital wallets, local methods and eligible pay-later choices. See Stripe’s U.S. pricing and the WooCommerce Stripe extension documentation.

The trade-off is operational ownership. Stripe offers powerful external dashboards and APIs, but teams need to understand which payment settings live in Stripe, which live in WooCommerce and how webhooks affect order states. A successful test payment does not prove the store can handle failed authorization, partial refunds, subscription renewals, or a delayed webhook correctly.

For the detailed account-model and subscription differences, see our WooPayments vs Stripe comparison. A merchant already using either gateway should not switch solely because a marketing page seems more integrated.

PayPal Payments: useful additional payment choice, with a separate fee model

PayPal should be assessed both as a merchant payment service and as a checkout preference. Some customers want to pay through a PayPal account instead of entering a card into an unfamiliar store. That can make the PayPal option commercially meaningful, but it does not prove it will increase conversion for your particular audience. Test actual checkout completion and fees before treating it as a guaranteed improvement.

The U.S. published standard domestic PayPal Checkout rate is 3.49% + $0.49 when receiving USD, while PayPal also advertises other card-processing arrangements such as PayPal Checkout card payments and Expanded Checkout at different rates. Its Pay Later pricing differs again. Do not charge all PayPal-related payments the same percentage in a budget model. Published merchant fees and the applicable product/contract are authoritative for a given transaction type. Consult PayPal’s U.S. merchant fee schedule and WooCommerce PayPal Payments documentation.

There are operating costs beyond percentages: PayPal-specific dispute handling, buyer claims, funding method availability and how refunds are initiated. Make sure the payments team knows whether an order is paid by PayPal or another provider; using two gateways complicates reconciliation if payout references, refund statuses or dispute notifications are not mapped to the correct processor.

Square: strongest shortlist candidate for a store with physical POS

Square becomes more attractive when an online WooCommerce shop is also connected to retail locations, events or pop-up sales. Its WooCommerce extension can operate as a payment gateway, an inventory synchronization tool, or both, with configuration determining which system is authoritative for catalog data. It also supports specific digital wallets and Square-related checkout options in eligible markets. See WooCommerce Square documentation.

Square’s U.S. rate card distinguishes transactions made through online payment APIs from other online products and from in-person card-present payments. Its published online API rate is 2.9% + $0.30; standard online payment pricing can show 3.3% + $0.30 depending on product and plan. Do not apply the generic online price to the WooCommerce integration without confirming which Square processing category your business will actually be billed under. See Square’s official pricing.

The principal risk is not simply processing fees. Product and inventory sync introduces directionality, update timing and conflict resolution. A retailer must define the source of truth for stock, price and order changes; audit what happens when a sale occurs in store while web inventory is nearly exhausted; and test cancellation and refund synchronization. The integration requires an eligible merchant country and technical requirements such as SSL and background processing.

Authorize.net: gateway-oriented choice for established processing arrangements

Authorize.net deserves evaluation when a merchant needs a payment gateway integrated with a merchant account or wants to preserve an established processor relationship. Its public U.S. pricing separates all-in-one, which combines gateway and processing, from gateway-only, which does not provide card-processing economics by itself.

Its advertised all-in-one plan currently lists $25 per month plus 2.9% + $0.30 per transaction, subject to eligibility. The gateway-only plan lists $25 per month plus $0.10 per transaction and a $0.10 daily batch fee; separate merchant-account processing charges still apply. It would be incorrect to treat the gateway-only $0.10 rate as the complete cost of accepting cards. See Authorize.net’s official pricing.

The available WooCommerce integration documents credit cards, eChecks, stored payment details through Customer Information Manager and WooCommerce Subscriptions compatibility, with account and extension requirements. There are multiple historical or related Authorize.net extensions, so merchants should check the specific plugin, its annual license cost, current WooCommerce compatibility and any needed CIM functionality. Review the gateway extension documentation.

WooCommerce payment gateway fees: U.S. reference prices

Provider and payment scenarioPublic reference rateCost that can be missed
WooPayments, U.S. domestic online card2.9% + $0.30International card, FX, dispute, different payment-method fees
Stripe, U.S. domestic online card2.9% + $0.30International card, FX, optional paid Stripe products
PayPal, U.S. domestic PayPal Checkout (USD)3.49% + $0.49Cards through other PayPal offerings use different published schedules
Square, U.S. online API payment2.9% + $0.30Other online products/plans can have different rates; POS not equivalent
Authorize.net, U.S. all-in-one$25/month + 2.9% + $0.30Possible WooCommerce extension/license costs and contract eligibility
Authorize.net, gateway only$25/month + $0.10/payment + $0.10 daily batchPlus separate merchant-account processing fees

Reference date: 20 October 2026. These rates describe named U.S. products, not every method or contract a merchant might use. Sources: official WooPayments, Stripe, PayPal, Square and Authorize.net pricing pages in the references below. Confirm your account’s applicable rates before making a decision.

Worked cost example: why order mix changes the result

Suppose a U.S. WooCommerce merchant records 200 successful domestic payments in a month, with an average paid order value of $45. The month’s card volume is 200 × $45 = $9,000. For comparability, initially assume every payment is a normal domestic online card using the stated standard flat rate, and ignore international fees, chargebacks, refunds, premium methods and fixed software subscriptions.

ScenarioIllustrative calculationTotal costShare of $9,000 volume
WooPayments domestic cards$9,000 × 2.9% + 200 × $0.30$321.003.57%
Stripe domestic cards$9,000 × 2.9% + 200 × $0.30$321.003.57%
PayPal Checkout wallet transactions$9,000 × 3.49% + 200 × $0.49$412.104.58%
Square online API, if applicable$9,000 × 2.9% + 200 × $0.30$321.003.57%
Authorize.net all-in-one$9,000 × 2.9% + 200 × $0.30 + $25$346.003.84%

Illustrative arithmetic only; no merchant sales data or measured performance. PayPal wallet payments are not the same payment type as card payments, so that row is an example of the cost of one additional buyer option—not a controlled like-for-like ranking. Square assumes the API rate is contractually applicable. Authorize.net excludes extension and other fees.

The example demonstrates two truths. First, transaction mix matters: a merchant receiving 20% of its sales through PayPal does not pay the PayPal rate on its other 80%. Second, a cost gap is not automatically a profit gap. A different checkout option may retain otherwise lost purchases or may bring additional support and reconciliation overhead. The article cannot claim either outcome without the merchant’s own tests.

At a lower average order value, fixed transaction fees make up a larger percentage of revenue. At a higher order value, percentage fees dominate. Use your median and average paid order values, not just the cart price shown on product pages, because shipping, taxes, refunds and multiple payment captures may affect the billed payment amount.

How to compare Authorize.net gateway-only correctly

If the same 200 transactions generate one settled batch per day for 30 days, Authorize.net’s published gateway-only charge would be $25 + (200 × $0.10) + (30 × $0.10) = $48 before the separate merchant processor’s charges and any extension licensing. A hypothetical merchant processor priced at 2.5% + $0.10 per payment would add $225 + $20 = $245, producing an illustrative $293 combined. That merchant-processor rate is an assumption, not an Authorize.net offer and not an estimate of what an applicant will be approved for.

For a real comparison, request both the merchant-processing statement and the gateway statement, then include chargebacks, statement charges, PCI program fees, minimums, batch expenses and contract terms. Without those inputs, a superficially cheap gateway-only quote is incomplete.

Subscriptions: the payment token and renewal path matter

A recurring-revenue store must distinguish a payment gateway’s ability to take an initial payment from its ability to charge a saved method months later. WooCommerce Subscriptions coordinates subscription scheduling and renewal orders; the gateway integration must provide the required saved-method support for the particular renewal workflow.

Ask the merchant’s developer or provider to verify the gateway’s current support for automatic renewals, subscription payment-method updates, authorization rules, failed-payment retries, off-session requirements, customer authentication and webhook events. PayPal and card methods can behave differently, even inside the same extension. A plugin marked ‘Subscriptions compatible’ is not proof every payment method inside that plugin supports every recurring scenario.

If switching providers, determine whether existing card tokens can move and whether the original processor’s agreement permits migration. Token portability is not a simple database export; sensitive credentials and processor vaults impose restrictions. Do not cancel the old gateway before confirming what will charge the next renewal. Our subscription payment-migration guide covers the broader principle of continuity, although Shopify mechanisms differ from WooCommerce.

Refunds, disputes and payout reconciliation

When comparing gateways, most merchants start with percentages and stop there. Finance teams must also reconcile the money that actually reached the bank. Refunds can reverse gross sales without reversing original processing fees; dispute charges and reserve policies can change balances; and settlement timing can create differences between the WooCommerce order date and the bank deposit date.

Before going live, process a controlled refund in the supported test environment, confirm the WooCommerce order state and provider-side transaction state, and ensure the accountant can trace one order to a payout and fee entry. Check whether refunds can be initiated from WooCommerce or require a provider dashboard, whether partial refunds are available and how customer emails are triggered. These details are often operationally more significant than nominal card-rate equality.

Also decide which system is the accounting source of truth. A WooCommerce order report records sales; it does not necessarily represent net cash after processing fees, disputes, FX conversions or timing differences. Export payout details and reconcile transaction IDs to orders. Our existing WooCommerce cost breakdown covers the broader platform budget.

International sales and local payment methods

A store shipping globally may not need a globally located payment provider, but it must be supported in its merchant country. Review onboarding eligibility, payout destinations, supported settlement currencies and the buyer methods actually available in each country. The ability to display prices in euros does not necessarily mean the merchant receives euros without conversion charges.

WooPayments and Stripe publish international-card and foreign-exchange additions on their U.S. pricing schedules; PayPal has distinct international commercial transaction charges; Square’s merchant acceptance is limited to specified countries. Local methods such as bank debits or market-specific wallets may have separate commercial conditions, return rights and settlement timelines. Use a region-by-region decision table rather than pretending an American card price represents worldwide economics.

For stores selling into the European Economic Area, also test strong-customer-authentication flows and relevant payment compliance. Supporting 3D Secure at the provider level is not the same as a configured WooCommerce checkout that reliably handles every authentication return, decline or delayed confirmation.

Implementation checklist: test before enabling live checkout

A sound evaluation includes a staging environment that resembles the real store. Use supported provider sandboxes or test modes, but understand that a sandbox does not automatically simulate every live settlement, dispute or wallet scenario. Record test results and identify who signs off.

  1. Verify eligibility: legal entity, owner identity, payout account, business category, expected currencies and prohibited/restricted-product rules.
  2. Map the current checkout: blocks or shortcode, theme compatibility, tax and shipping plugins, express wallet buttons and any caching exclusions.
  3. Test ordinary orders: successful payment, rejected card, customer return to checkout, duplicate click and manual order capture if relevant.
  4. Test money movement: full and partial refunds, canceled authorizations, disputes, payout exports and finance reconciliation.
  5. Test asynchronous events: delayed webhooks, duplicate notifications, timeouts and fulfillment actions that must not happen twice.
  6. Test recurring billing: renewal eligibility, saved cards, failed payments and customer payment-method updates when subscriptions are sold.
  7. Test on phones: card fields, wallet availability, focus order, error visibility, contrast and the end-to-end order confirmation.
  8. Plan rollback: preserve the previous configuration and know when, how and by whom the new gateway could be disabled safely.

Do not run two card processors simultaneously without knowing which one controls checkout buttons and saved tokens. Duplicate gateways can create confusing payment labels or duplicate captures if poorly configured. Begin with a narrow rollout and use transaction logs to investigate failures, without exposing customer payment data or keys.

Decision matrix: which gateway for which merchant?

Merchant situationStart by evaluatingReason to choose differently
First WooCommerce store, standard domestic productsWooPayments, StripeExisting provider contracts or local methods could change the result
Business already using Stripe beyond WooCommerceStripe extensionNative WooCommerce financial administration may be more important
Customers specifically request PayPal walletsAdd PayPal PaymentsReconciliation burden or actual demand may not justify the option
Shop plus physical retail using Square POSSquareInventory sync or supported-country limitations may prevent fit
Merchant with a negotiated processor agreementAuthorize.net gateway-only, plus existing processorCombined processing + gateway + software cost may be higher
Subscription business with active membersCurrent gateway first, then verified migration optionsRenewal token continuity may outweigh new-transaction pricing
International merchant with regional payment habitsEligible local gateways and Stripe/WooPayments alternativesU.S. price tables are not applicable to every country

What a convincing provider quote should include

Ask every shortlisted provider or payment integrator for a written response about: exact merchant entity and payout country; fees by transaction type; FX and international-card increments; gateway or connector subscription charges; refund and dispute fees; payout schedule and reserves; token storage; available exports; supported mobile wallets; recurring-payment eligibility; and who handles technical support when WooCommerce and the processor disagree.

For a larger store, also request an effective-rate report by payment method and order size. A blended ‘average fee’ may hide expensive methods or treat gateway invoices as separate operating expenses. Your comparison should allow a finance manager to reperform every number using the same transaction sample.

Common mistakes to avoid

  • Comparing different payment products as if they are identical: a PayPal wallet rate, a standard card rate and a gateway-only transaction fee cover different functions.
  • Ignoring monthly and extension fees: WooCommerce gateway plug-ins and premium capabilities may incur separate license costs.
  • Assuming every wallet works everywhere: Apple Pay, Google Pay, PayPal, Venmo and local payment methods depend on browser, region, account and plugin configuration.
  • Switching during a subscription billing cycle without a token plan: even small routing mistakes can interrupt renewals.
  • Judging POS integration solely by payment fees: inventory synchronization, source-of-truth rules and return handling also cost staff time.
  • Believing a successful sandbox charge proves readiness: test failed payments, asynchronous updates and accounting workflows.

Frequently asked questions

Is WooPayments cheaper than Stripe for WooCommerce?

For the standard U.S. domestic online card scenario, both currently publish 2.9% + $0.30. That equality does not establish equal total costs for every merchant: product additions, other payment types, foreign card charges, refunds and merchant-specific arrangements can change the result. Choose on operational fit and your real transaction mix, then check the current schedules.

Can I offer PayPal alongside WooPayments or Stripe?

Many WooCommerce stores configure a separate PayPal option beside their main card checkout. The choice should be deliberate: each provider may have its own transaction fees, payouts, refunds and dispute workflow. Test that the right order is sent to the right provider and only one payment is captured.

Is Square the best choice for a WooCommerce store with a physical shop?

Square merits a strong evaluation when you already use Square POS and want WooCommerce integration, but it is not automatically the best choice. Test item synchronization, order imports, gift cards and return workflows, and confirm that the WooCommerce merchant and selected features are supported in your country.

Does Authorize.net’s 10-cent gateway fee replace card processing fees?

No. The gateway-only plan sits on top of a separate merchant-processing relationship and has a monthly charge and batch-related fee. The all-in-one plan is a different price structure. Compare the final statement-level cost, including WooCommerce integration fees.

Do all payment gateways support WooCommerce Subscriptions?

No blanket claim is safe. Compatibility depends on the exact gateway extension, its version, payment method, saved-payment details and recurring-charge mechanism. Verify the official compatibility guidance and test future renewal scenarios before onboarding subscribers or migrating them.

Final verdict

For most new WooCommerce stores, begin with WooPayments and the official Stripe extension as the core card-processing shortlist. They can share a headline U.S. card rate, but their account and administration models differ. Add PayPal Payments when it meets a genuine buyer need. Give Square special consideration for integrated in-person retail, and evaluate Authorize.net when merchant-account structure or negotiated processing makes its additional gateway layer worthwhile.

The strongest decision is the one a merchant can explain with documented fees, a verified checkout test, a workable accounting process and a safe migration plan—not the provider that wins an unqualified ‘best’ label. Evaluate the full checkout experience before routing revenue to a new processor.

Building or improving a WooCommerce store?

Compare WooCommerce’s official extension and payment options, and check your exact eligibility before signing up. Explore WooCommerce tools and extensions (affiliate link). For broader platform cost context, see StackScale’s Shopify vs WooCommerce comparison.

Methodology, official sources and additional reading

This guide was prepared from publicly available provider pricing and primary extension documentation, reviewed 20 October 2026. It does not present merchant transaction logs, hands-on benchmark tests or undisclosed commercial relationships as independent testing. Posted rates can change; financial examples are illustrative. Editorial judgments reflect feature and operational suitability for defined merchant scenarios, not measured checkout conversion.

  1. WooCommerce — WooPayments fees: country-specific card, international, FX and dispute prices.
  2. WooCommerce — WooPayments documentation: accounts, payments, reporting and eligibility.
  3. Stripe — U.S. payments pricing: cards, international fees, conversion and additional products.
  4. WooCommerce — Stripe extension documentation: supported payment methods and administration.
  5. PayPal — U.S. merchant fees: product-specific commercial transaction fees.
  6. WooCommerce — PayPal Payments documentation: integration and configuration.
  7. Square — official payment processing fees: online, API and in-person distinctions.
  8. WooCommerce — Square integration: payment settings, POS and synchronization.
  9. Authorize.net — official pricing: all-in-one and gateway-only plans.
  10. WooCommerce — Authorize.net extension: requirements, saved payment details and subscriptions.

Related StackScale guides: WooPayments Pricing · WooPayments vs Stripe · WooCommerce Cost Breakdown · Shopify Payments Fees.

Similar Posts