Industry Payment Guides

Best Payment Gateway for WooCommerce: A Store Owner's Checklist

Find the best payment gateway for WooCommerce with this checklist: Checkout Blocks, HPOS, Subscriptions, plugin upkeep, pricing and saved-card portability.

Miniature shopping cart beside a laptop and colorful shopping bags

Photo: Pixabay

On this page 8 sections
  1. Hosted Redirect vs. On-Site Card Fields: What It Means for WooCommerce
  2. How to Vet a WooCommerce Payment Gateway Plugin: Updates, Reviews, and Support
  3. Compatibility With Checkout Blocks, HPOS, and WooCommerce Subscriptions
  4. Pricing Models: Flat-Rate Aggregators vs. a WooCommerce Merchant Account
  5. Card Data Portability: Can You Take Your Saved Cards With You?
  6. More WooCommerce Payment Options: Wallets, ACH, and BNPL Through One Plugin
  7. Questions to Ask When Choosing the Best Payment Gateway for WooCommerce
  8. Next Steps: How MannyPay Fits

Key takeaways

  • The plugin matters as much as the processor. Check Checkout Block, HPOS and WooCommerce Subscriptions compatibility before you compare brands.
  • Update history, "tested up to" versions and support responsiveness reveal more about a WooCommerce payment gateway plugin than star ratings do.
  • Ask in writing whether saved cards and subscription tokens can be exported if you leave. Your recurring revenue depends on the answer.
  • Flat-rate pricing is simple, and a dedicated WooCommerce merchant account can offer more control. Compare them using your own statements.

Most lists of the best payment gateway for WooCommerce rank processors by brand. That misses how payments actually work in a WooCommerce store. Your customers never interact with the processor directly. They interact with a WordPress plugin, and that plugin has to work with your theme, checkout layout, order storage, subscription renewals and caching setup. This checklist explains what to verify before you install one.

A strong processor paired with a weak plugin will still cost you sales. The factors below determine whether your payment setup holds up during a busy weekend or breaks after a routine update.

If you're still sorting out the basic pieces, start with our guide on how to set up e-commerce payment processing for your online store, then come back here.

Hosted Redirect vs. On-Site Card Fields: What It Means for WooCommerce

WooCommerce payment plugins generally collect card data in one of three ways.

ApproachWhat the customer seesTrade-offs
Hosted redirectLeaves your site to pay on the provider's page, then returnsSmallest security footprint for you. The extra step can feel jarring, and you have less control over the look.
Embedded hosted fields (iframes)Card fields appear on your checkout but are served by the providerFeels native and keeps card data off your server. Theme or script conflicts can break the fields.
Direct integrationYour site's checkout handles card entry more directlyMost control and the most security responsibility. Rarely the right fit for a small store.

The method you choose affects your PCI compliance workload. How card data reaches the processor determines which self-assessment questionnaire you complete and how much of your WordPress site falls in scope. Ask your provider which questionnaire applies to their plugin as you would configure it. Don't assume. If you also take orders over the phone, see our guide to entering phone-order card payments in WooCommerce admin.

Two WooCommerce-specific points:

  • Redirect flows depend on the return trip. If a customer closes the tab after paying but before landing back on your site, the order relies on a webhook to update. Make sure webhooks are configured and not blocked by a security plugin or firewall.
  • Embedded fields are sensitive to page optimization. Aggressive JavaScript minification, deferral or page caching on checkout pages can break iframe-based card fields. Exclude cart, checkout and account pages from caching.

How to Vet a WooCommerce Payment Gateway Plugin: Updates, Reviews, and Support

Treat a WooCommerce credit card plugin like any other piece of critical infrastructure. Before installing, check its listing in the WordPress.org plugin directory or on the developer's site.

  • Last updated date. WooCommerce and WordPress release updates regularly. A payment plugin that hasn't been updated in a long time is a risk, even if it works today.
  • "Tested up to" version. Compare it against the WordPress and WooCommerce versions you run.
  • Who maintains it. A plugin built by the processor or gateway itself usually gets faster fixes when an API changes. Third-party plugins can be excellent, but confirm they're actively maintained.
  • Support forum behavior. Read recent threads. Look at whether issues get answered and resolved, not just whether complaints exist.
  • Changelog quality. A clear changelog that names fixes and compatibility updates signals a team that takes the plugin seriously.

Star ratings are a weak signal on their own. A plugin with modest ratings and a responsive support team is often a better bet than a highly rated plugin nobody has touched in a year.

Practical habit: Test payment plugin updates on a staging site first, and avoid updating payment plugins right before your busiest sales periods, such as the Black Friday and Cyber Monday stretch.

Compatibility With Checkout Blocks, HPOS, and WooCommerce Subscriptions

These three compatibility checks catch problems that brand rankings never mention.

Checkout Blocks

WooCommerce offers a block-based Cart and Checkout alongside the older shortcode-based checkout. Newer stores and themes increasingly use blocks. Some payment plugins support only the classic checkout. Others display in the block checkout but lose features such as saved cards or express wallet buttons.

Confirm the plugin supports the checkout type you use, with the features you need. If it doesn't, you may have to rebuild your checkout or drop a payment option.

HPOS (High-Performance Order Storage)

HPOS moves WooCommerce orders out of the general WordPress posts table and into dedicated order tables. Plugins that read or write order data the old way can fail or behave unpredictably with HPOS turned on.

WooCommerce flags incompatible plugins in its settings. Check that warning list after installing any payment plugin.

WooCommerce Subscriptions

For recurring revenue, the gateway has to do more than take a one-time payment. Confirm the plugin supports:

  1. Tokenization for automatic renewals. The card is stored as a token in the gateway's vault, and renewals charge it without customer action.
  2. Payment method changes. Customers can update an expiring card from their account page.
  3. Failed-payment retries. The plugin works with Subscriptions' retry logic rather than around it.
  4. Amount and date changes. It can handle upgrades, downgrades, proration and next-payment-date changes.
  5. Multiple subscriptions per customer. This is common for stores that sell more than one plan.

If a gateway lacks automatic renewal support, Subscriptions falls back to manual renewals. Customers have to come back and pay each cycle, which hurts retention. For the card-update side, see our guide to keeping subscribers billing when cards expire. If you bill on autopay, also review automatic renewal laws by state. That article is general information, so confirm requirements with a qualified professional.

Pricing Models: Flat-Rate Aggregators vs. a WooCommerce Merchant Account

Most WooCommerce payment options fall into one of two pricing structures.

Flat-rate aggregators charge one blended rate per transaction, usually plus a fixed per-transaction fee. Setup is fast, often with no separate underwriting up front, and you get a single rate to budget around.

The trade-off is that you share an account structure with many other merchants. That can mean more sensitivity to sudden volume changes, and the blended rate may not reflect your actual card mix.

Interchange-plus merchant accounts pass through the card networks' interchange and assessment costs, then add a disclosed processor markup. A dedicated WooCommerce merchant account involves underwriting at the start. In return, you get your own account and clearer visibility into what each transaction costs.

Illustrative example only: A store with mostly small debit-card orders and a store with large rewards-card orders could pay very differently under the same flat rate, because their underlying interchange costs differ.

The only reliable comparison uses your own numbers:

  1. Pull a few months of statements.
  2. Calculate your effective rate (total fees divided by total volume).
  3. Ask each provider to price the same volume and card mix.

Also check:

  • Monthly gateway fees and per-transaction gateway fees, which are sometimes separate from processing fees
  • Chargeback fees
  • Payout timing
  • Any reserve or rolling-hold terms

For more on deciding between the two models, read when your store should switch from flat-rate to interchange-plus.

Some merchants also offset card costs through programs such as surcharging where state law and card network rules permit. Online surcharging has disclosure and checkout-display requirements, so confirm current rules before turning it on. For a side-by-side look at two common options, see our breakdown of WooPayments vs. Stripe fees, payouts and features.

Card Data Portability: Can You Take Your Saved Cards With You?

This is the question most store owners ask too late.

When a customer saves a card or starts a subscription, the card number lives in your payment provider's vault. WooCommerce stores only a token that references it. If you switch providers, those tokens stop working with the new gateway. Unless the card data itself can be migrated, every subscriber and saved-card customer has to re-enter their details. Some won't. If you take deposits and charge balances to saved cards, see our guide to setting up WooCommerce deposits and partial payments.

Card data migration between providers happens through a secure, PCI-compliant transfer, not a CSV you download yourself. Policies vary. Some providers support outbound exports on request, some attach conditions and some don't offer it at all.

Before you commit, ask:

  • Do you support exporting stored card data to another PCI-compliant provider if I leave?
  • Is there a fee, a minimum notice period or a typical timeline?
  • Do you accept inbound migrations from my current provider?
  • After migration, who remaps the new tokens to existing WooCommerce Subscriptions records, and is there a supported tool or process for it?

Get the answers in writing. For a store with meaningful recurring revenue, portability can matter more than a small difference in rates.

More WooCommerce Payment Options: Wallets, ACH, and BNPL Through One Plugin

Every extra payment plugin is another thing to update, test and troubleshoot. Where possible, choose a plugin that covers the methods your customers actually use.

  • Digital wallets. Apple Pay and Google Pay can shorten checkout on mobile, where typing card numbers is a common drop-off point. Apple Pay requires domain verification on your site. Confirm the plugin handles it, and that express buttons work on product and cart pages if you want them there.
  • ACH and bank payments. These are useful for higher-ticket or B2B orders. Settlement is slower than with cards, and returned payments work differently from chargebacks, so your fulfillment hold rules may need adjusting.
  • Buy now, pay later. BNPL providers approve merchants separately and set their own product restrictions and fees. Check whether the plugin supports BNPL in the block checkout and on subscription products, which many BNPL offerings exclude.

Also look at fraud tools. Support for 3-D Secure authentication, address and CVV checks, and configurable fraud rules can help. Overly strict settings create their own problems, as our article on why good customers' cards get declined at checkout explains.

Questions to Ask When Choosing the Best Payment Gateway for WooCommerce

Run through this list with any provider you're considering:

  1. Which checkout types does your plugin support: block, classic or both? Does feature support differ between them?
  2. Is the plugin declared compatible with HPOS?
  3. Does it support WooCommerce Subscriptions automatic renewals, payment method changes and retries?
  4. Who maintains the plugin, and how quickly are compatibility fixes released after WooCommerce updates?
  5. Which PCI self-assessment questionnaire applies to my setup with your plugin?
  6. Can stored cards and subscription tokens be exported if I leave? Can you import mine now?
  7. Which wallets, ACH and BNPL options work through this single plugin?
  8. What are all the fees, including processing, gateway, monthly and chargeback fees? What are the payout timing and reserve terms?
  9. Is there a sandbox or test mode I can use on a staging site?
  10. Who do I call when checkout breaks on a Saturday?

Next Steps: How MannyPay Fits

MannyPay is a U.S. merchant services provider offering merchant accounts and online payment processing for e-commerce businesses. MannyPay supports WooCommerce integration, along with gateways including Authorize.net and NMI.

To see what fits your volume and checkout, request a free quote and include your current statements so the comparison is based on your numbers rather than a generic rate sheet. A MannyPay specialist will respond within one business day. Bring the questions above, including how subscriptions and stored cards would be handled, and get the answers in writing.

About the author

MannyPay Editorial Team

Beyond the Swipe's editorial desk researches the publication's guides and news and cites its sources in every article. Articles reviewed by a named MannyPay editor carry that editor's byline.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading