WooCommerce Payment Gateway Plugins

These are WooCommerce payment gateway plugins for stores that already have a merchant account. Match your processor in the grid below, then read that product page for capture, refunds, hosted vs direct checkout, and any subscription notes—not a generic “best gateway” list.
If your processor is not listed, start with custom payment gateway integration or get a quote. Official Stripe or PayPal extensions are not in this catalog.

Showing 1–16 of 35 results

Choosing a gateway

Start with the processor you are already boarded on. PatSaTECH plugins connect WooCommerce to that account; they are not a way to apply for a merchant account.

Then confirm three facts on the product page—not from this grid:

  1. Checkout model — shopper stays on your checkout (direct / API / tokenized field) or leaves for a hosted page.
  2. Recurring — first charge vs renewal (tokens, retries, failed-payment emails).
  3. Store constraints — currency, country, and whether you use classic checkout, Blocks, or HPOS.

Catalog matches (live SKUs, not a ranking):

The grid also includes checkout utilities (for example shipping- or country-based method routing, and SecureRegister). Those are not payment processors.

Enable-in-admin walkthrough: How to use WooCommerce payment gateways.

Direct vs hosted checkout

Direct / on-site flows collect payment data on (or in a field on) your checkout and talk to the processor API. Hosted / redirect flows send the shopper to the processor page and rely on a return URL plus a server callback.

Neither model is “more PCI” by slogan. Hosted pages reduce how much card data your theme touches; they also add abandon-and-return cases and pending orders when the callback is late. Direct flows keep the shopper on-site and make refunds/voids in Woo admin more natural—if the plugin and your account support those operations.

This catalog has both shapes. Examples of named products (read each page; do not infer features): WorldPay XML Direct, Plug'n Pay Direct, Plug'n Pay Redirect, KOMOJU Hosted Page, NabTransact Direct, NabTransact Redirect.

If a redirect payment succeeds at the processor but Woo stays Pending, reconcile before retrying: WooCommerce payment timeout.

Subscriptions

A gateway that charges a one-time cart can still fail on renewal day. Recurring billing needs a triangle: WooCommerce Subscriptions (or your recurring engine), the gateway plugin’s subscription support, and the processor’s tokenization / recurring APIs.

Do not assume every SKU in this grid supports Subscriptions. Check that product page. The NMI product documents Subscriptions when your NMI package includes tokenization—sandbox-test renewals before go-live: Network Merchants Inc (Collect.js) for WooCommerce.

What to verify before launch: Subscriptions and recurring billing.

Tokenization

“Saved card” usually means the processor vaulted a token, not that WooCommerce stored a PAN. Tokens are what make one-click checkout and subscription renewals possible; they are also why cloning a site, switching accounts, or mixing sandbox and live keys breaks returning customers.

Read tokenization and saved payment methods. Confirm vaulting, card-update, and deletion behavior with the processor and on the product page—do not copy another gateway’s token story onto a different SKU.

WooCommerce Blocks checkout

Classic shortcode checkout and Blocks / block checkout register payment methods differently. A plugin can appear under WooCommerce → Settings → Payments and still be missing on the block checkout.

Test matrix and failure modes: WooCommerce Blocks checkout and payment gateways. If checkout shows no methods, use the decision tree (location, currency, Blocks, cache) in No payment methods available.

NMI’s product page documents Block checkout; treat other SKUs as unknown until that page or changelog says so.

HPOS

High-Performance Order Storage changes where WooCommerce keeps order data. Gateway plugins that still assume legacy wp_posts order storage can break admin capture/refund, webhooks, or subscription renewals after you flip HPOS on production.

There is no published PatSaTECH HPOS article as of this hub. Use the product changelog and requirements on each SKU. The NMI product page lists HPOS; do not extend that claim to the rest of the grid.

Testing before go-live

Use the processor’s sandbox or test credentials. Do not send invented card numbers to a live MID.

Minimum sandbox pass: authorize or sale, failed card, refund or void, and (if you sell subscriptions) one renewal.

Custom development

Buy a catalog plugin when your processor is listed and the product page covers your checkout model. Commission custom work when you need marketplace splits, headless storefronts, ISO-specific fields, or a processor we do not sell.

Need help installing a plugin you already purchased? Plugin installation support.

FAQ

Are these plugins compatible with WooCommerce Subscriptions?

Only if that product page (and your processor package) says so. Recurring billing also needs tokenization and a renewal test. See subscriptions and recurring billing.

Do you board merchant accounts or sell Stripe/PayPal?

No. This catalog is for stores that already have a processor. Official Stripe and PayPal WooCommerce extensions are not sold here.

Do you offer installation help?

Yes—plugin installation support. Product-specific credentials stay on that product’s docs or page.

Will this work with Blocks checkout or HPOS?

Check the individual product page and changelog. Category-level “all plugins support Blocks/HPOS” would be false. Blocks runbook: Blocks checkout and payment gateways.

My processor is not in the grid. What next?

Custom payment gateway integration or get a quote. Do not buy a different processor’s plugin and hope the API matches.

Also see the shop, Gravity Forms hub, Easy Digital Downloads hub, and custom integration.

Our Partners

fraudlabs
opayo
nochex
Razorpay
durango merchant services
2checkout is now verifone
authorizenet
gravity forms
whmcs