All free tools Talk to a payments specialist

Free tools › Guides

Best Payment Gateway for WooCommerce: How to Choose the Right One for Your Store

The best payment gateway for WooCommerce has a well-maintained plugin, supports the payment methods your shoppers use (cards, Apple Pay, Google Pay, and ACH if you sell B2B), works with WooCommerce Subscriptions if you bill on a recurring schedule, and sits on a merchant account with transparent interchange-plus pricing and clear terms on holds and reserves. For most stores processing more than a few thousand dollars a month, the gateway's own fee matters far less than the merchant account behind it and whether your checkout offers what buyers expect.

Key takeaways

  • A gateway is the pipe between WooCommerce and your processor. Your cost and account stability come mostly from the merchant account, not the gateway.
  • Comparing gateways by posted fee alone is the most common mistake. Compare total effective rate, payout timing, and reserve terms.
  • In the example below, a $40,000-a-month store pays about $1,310 on an example flat rate versus about $960 on an example interchange-plus setup. Your numbers will differ.
  • Check plugin fundamentals: hosted payment fields for lighter PCI scope, wallet support, tokenization for subscriptions, authorize-and-capture, and refunds from the WooCommerce admin.
  • Ask for reserve and hold terms in writing before you sign, especially for subscriptions, preorders, or drop shipping.

What you are actually choosing: gateway, processor, and merchant account

Three separate pieces move money from a shopper's card to your bank account. The gateway is software that securely sends card details from your WooCommerce checkout to be authorized. The processor routes the transaction through the card networks to the cardholder's bank. The merchant account is the underwritten relationship that determines your pricing, payout schedule, and any holds or reserves.

Some providers bundle all three into a single sign-up with one flat rate. Others keep them separate: you get a merchant account from a processor and connect it to a standalone gateway such as Authorize.net or NMI, both of which offer WooCommerce plugins. Bundled setups are fast to start. With separate pieces, you get more control over pricing and underwriting, and you can change one piece without rebuilding your checkout.

When someone asks which gateway is best, they usually mean the whole stack. Evaluate the whole stack, because that is what determines your monthly bill and how reliably you get paid.

What most WooCommerce gateway comparisons get wrong

Most comparison articles rank gateways by headline fee, as if the gateway sets your rate. On a dedicated merchant account, the gateway usually charges a modest monthly fee and a few cents per transaction. Most of your cost comes from interchange, which is the fee the cardholder's bank sets based on card type and how the transaction was processed. Card brand assessments and your processor's markup come on top of interchange.

The second thing these articles skip is account stability. Two setups with similar rates can behave very differently when your sales spike, when you take preorders, or when a batch of refunds comes in. A provider that freezes payouts during your best month costs you more than a few basis points of fees. Ask how underwriting works up front, and whether the provider reviews your business model before approving you or after funds are already moving.

A better comparison has three parts: total effective rate (all fees divided by sales volume), payout and reserve terms, and plugin quality. The gateway's logo matters least of all.

Worked example: what a WooCommerce store might pay

This example uses made-up but realistic numbers. A WooCommerce store processes $40,000 a month across 500 orders, with an average order of $80. We compare an example flat rate of 2.9% plus $0.30 per transaction against an example interchange-plus setup. That setup assumes average interchange of 1.95% for eCommerce, a 0.20% markup, a $0.10 per-transaction processor fee, and a separate gateway costing $25 a month plus $0.05 per transaction. All of these figures are assumptions for illustration.

On the example flat rate: $40,000 x 2.9% = $1,160, plus 500 x $0.30 = $150, for a total of $1,310. That is an effective rate of about 3.28%. On the example interchange-plus setup: interchange of $780 + markup of $80 + per-transaction fees of $50 + gateway monthly fee of $25 + gateway per-transaction fees of $25 = $960. That is an effective rate of about 2.40%, or roughly $350 a month lower in this example.

Order size changes the picture. Per-transaction fees take a larger share of small orders. A $15 order pays $0.30 on the example flat rate, which is 2 percentage points in per-item fees alone. Rewards cards, corporate cards, and keyed-in transactions carry higher interchange, so your card mix moves the result as well. Plug in your own volume, order count, and the fees on your actual statement before drawing conclusions.

Estimates are based on published industry averages and are not a quote. Actual rates depend on card mix, ticket size, industry, and underwriting.

Run your own numbers

Check your online checkout against the payment methods and settings shoppers expect, and see what you're missing.

Open the free Checkout Payment Method Gap Analyzer Book a 15-minute call

Holds, reserves, and authorizations: the terms that affect cash flow

A reserve is money the processor holds back from your payouts to cover future refunds and chargebacks. Take a rolling reserve of 5% held for 180 days as a made-up example. On $40,000 a month, that withholds $2,000 each month, and the balance builds to about $12,000 before the first month's funds are released. That is real working capital. Stores selling subscriptions, preorders, or drop-shipped goods with long delivery windows are more likely to face reserves, because the processor carries the risk until the product arrives.

Payout holds are different. They are temporary freezes, often triggered by a sudden volume jump, an unusually large order, or a rise in disputes. You can reduce surprises by telling your provider about planned promotions and seasonal peaks in advance. Ask for their volume-review triggers in writing.

Authorizations also matter in WooCommerce. If you ship later, a gateway that supports authorize-now, capture-later lets you charge when you fulfill. Authorizations expire after a window that varies by card brand and transaction type. Backordered items may need a fresh authorization rather than a late capture, so confirm the plugin handles this cleanly.

Checkout features that change conversion and fraud exposure

Once costs are reasonable, the gateway's job is to avoid losing sales and to block bad ones. Apple Pay and Google Pay matter most for mobile shoppers. They skip typed card entry and can reduce checkout friction. If you sell to businesses, ACH or eCheck at checkout can lower costs on large orders. For subscriptions, you need tokenization that works with WooCommerce Subscriptions so renewals charge a stored token. Ideally you also want an account updater so expired cards are refreshed automatically.

How the card form is built affects your PCI scope. Hosted fields or iframes keep card data off your server and generally qualify for a lighter self-assessment. Direct-post setups, where your own page controls the form, generally increase scope. Confirm the exact requirement with your processor.

Fraud tools should be adjustable, not just on or off. Look for AVS and CVV rules you can tune, velocity limits that stop card-testing bursts, and 3-D Secure, which can shift liability for certain fraud chargebacks to the card issuer. Set these too strictly and you decline good customers. Set them too loosely and you invite disputes.

It is hard to judge your own checkout objectively, so use a structured comparison. The free [Checkout Payment Method Gap Analyzer](https://touchsuite.com/tools/checkout-payment-method-gap-analyzer) compares your online checkout against the payment methods and settings shoppers expect and shows what you are missing. Run it before you switch gateways, so you know which features the new setup has to cover.

How to decide and test before you commit

Start with requirements, not brands. List the payment methods you need, whether you bill on a recurring schedule, whether you authorize and capture later, your monthly volume and average order size, and any business-model details an underwriter will ask about, such as preorders or long fulfillment times. Then ask each provider for a written pricing breakdown on your actual volume, plus their reserve, payout, and early termination terms.

Check the plugin itself. Look at when it was last updated, whether it supports current WooCommerce versions and block-based checkout, and whether refunds issued in WooCommerce sync to the gateway automatically. Run test transactions in sandbox mode, covering a successful charge, a decline, a partial refund, and a subscription renewal, before going live.

If you would like a second opinion on your setup or a pricing breakdown based on your volume, [talk to a payments specialist](https://touchsuite.com/contact).

Frequently asked questions

Is the WooCommerce payment gateway the same as a merchant account?

No. The gateway is software that sends card data from your checkout to be authorized. The merchant account is the underwritten relationship that sets your pricing, payouts, and reserves. Some providers bundle both, and others let you pair a merchant account with a separate gateway.

Should a small WooCommerce store use flat-rate or interchange-plus pricing?

At very low volume, a flat rate's simplicity can be worth the extra cost. As volume grows, interchange-plus often costs less because you pay the actual interchange plus a fixed markup. Calculate your effective rate on real numbers to see where you stand.

Which gateway features matter for WooCommerce Subscriptions?

You need tokenization that WooCommerce Subscriptions can use for automatic renewals. Ideally you also want an account updater for expired or reissued cards and retry logic for soft declines. Confirm the plugin explicitly supports Subscriptions, including payment method changes by the customer.

Can I switch WooCommerce gateways without losing my saved customer cards?

Sometimes. Stored card tokens belong to the gateway or processor that created them, so moving them requires a secure token migration between providers. Ask both providers whether they support it before you switch, or subscription customers may need to re-enter their cards.

How we put this together

The cost example uses illustrative assumptions, not quotes. These include an example flat rate of 2.9% plus $0.30, an assumed average eCommerce interchange of 1.95% drawn from published industry ranges, an assumed 0.20% markup and $0.10 per-transaction fee, and an assumed gateway fee of $25 a month plus $0.05 per transaction. Actual interchange is set by the card brands in their published interchange tables. It varies by card type, transaction method, and merchant category, and card brands typically revise their schedules periodically. The reserve example (5% held for 180 days) is hypothetical. Real reserve terms are set during underwriting. To check these figures against your own business, divide total fees by total sales on a recent merchant statement to get your effective rate, then compare your per-transaction fees, gateway fees, monthly fees, and any reserve or hold language in your agreement. Figures and practices reflect general industry conditions at the time of writing and should be rechecked against current card brand tables and your own contract. Estimates are based on published industry averages and are not a quote. Actual rates depend on card mix, ticket size, industry, and underwriting.

Estimates are based on published industry averages and are not a quote. Actual rates depend on card mix, ticket size, industry, and underwriting.