How to Restrict a WooCommerce Payment Method by Cart Total, Category, or Role (4 Plugins Compared)

If you need to restrict a WooCommerce payment method, say hiding Cash on Delivery unless the shipping method is local pickup, or turning off PayPal once a cart crosses a certain total, the fastest route isn’t custom code. It’s one of a handful of small, purpose-built plugins that hook into WooCommerce’s payment gateway filter and let you build the rule from a settings screen. This post compares four of them: what each one can actually condition on, what it costs once you outgrow the free tier, and where each one draws its wall between free and Pro.

The underlying mechanism is the same across all four. WooCommerce runs every available gateway through the woocommerce_available_payment_gateways filter before rendering the checkout page, and these plugins all hook into that filter to strip out gateways that don’t match your conditions. None of them touch WooCommerce core, so none of them are fragile in the way a custom functions.php snippet tends to be when WooCommerce ships a checkout update. The differences show up in which conditions each plugin exposes for free, how many rules you get before hitting a paywall, and whether the plugin was built to also handle extra fees and partial payments or just gateway visibility.

A few real scenarios this covers: offering Cash on Delivery only for local pickup orders, hiding PayPal on orders under a threshold where its percentage fee eats the margin, restricting a wire-transfer option to wholesale accounts by user role, or disabling a gateway entirely for one shipping country. None of this needs a PHP file. All four plugins below put it in a settings screen.

Conditional Payments for WooCommerce

Conditional Payments for WooCommerce, built by WP Trio, is the most straightforward of the four to set up. It works by letting you attach one or more conditions directly to an existing payment gateway: order subtotal, shipping method, billing address fields, or shipping address fields. The classic example from its own documentation is enabling Cash on Delivery only when the shipping method is local pickup, while leaving every other gateway untouched for every other order.

• Price: Free, Pro from $59/year (1-site license; $89 for 3 sites, $139 for 5)
• Requires: WordPress 4.5+, PHP 7.0+
• Last updated: August 6, 2026

Setup happens entirely inside WooCommerce’s own settings. After activation, go to WooCommerce > Settings > Payments > Conditions and add a ruleset there, picking the gateway it applies to and the conditions that have to be true for it to show or hide. The free version covers products in cart, order subtotal, shipping method, and billing or shipping address fields, which is enough for most of the scenarios above.

Where it draws the paywall: coupon-based conditions, currency, stock status, and shipping class all move to Pro, along with the ability to add payment method fees conditionally (not just hide or show a gateway, but surcharge it). If your rule only needs subtotal, shipping method, or address fields, the free version does the whole job.

Payment Methods by Product & Country for WooCommerce

Payment Methods by Product & Country for WooCommerce, from WPFactory, takes a narrower but deeper approach to one specific condition: what’s actually in the cart. Instead of a general rule builder, it works in two modes per gateway: show a gateway only when a chosen product category or tag is in the cart, or hide a gateway when a category or tag is present. WPFactory’s own example is a store selling an expensive product category that should only check out via wire transfer, while a separate cheap category stays open to every gateway.

• Price: Free, Pro from $59.99/year or $199 one-time for a lifetime license
• Requires: WordPress 4.4+ (minimum PHP version not listed by the developer)
• Last updated: June 29, 2026

After activation, the settings live at WooCommerce > Settings > Payment Gateways per Products, with separate tabs for category-based and tag-based rules. You pick a gateway, then move categories or tags into an “included” or “excluded” list for it. It’s worth reading the plugin’s own note carefully here: a category can only be set to “allow only” or “hide all except” for a given gateway, not both at once, so plan which direction you’re restricting in before you start adding rules.

The free version is genuinely usable on its own for category- or tag-based rules. Pro adds restriction at the individual product and variation level (not just category or tag), country-based restriction, and a fallback gateway setting for when a mixed cart triggers conflicting rules and would otherwise leave checkout with no available payment method at all. That fallback option is the one feature here worth paying for if your catalog mixes a lot of categories, since a cart with no valid gateway is a lost sale, not just an inconvenience.

PiWeb Disable Payment Method / Partial Payment for WooCommerce

PiWeb’s Disable Payment Method for WooCommerce is the broadest of the four on paper. Its free version alone lists conditions for product, category, shipping method, country, shipping zone, cart total, postcode, day of week, city, state, coupon code, shipping class, user role, and even days since the customer registered. It’s also the only one of the four that bundles a second, unrelated feature: conditional fees on a gateway (a flat or percentage surcharge for using COD, for instance) and partial payment, where a customer pays a small deposit upfront and the rest on delivery.

• Price: Free, Pro from ₹2,014/year for a 1-year license (roughly $24/year at current exchange rates)
• Requires: WordPress 4.0.1+ (minimum PHP version not listed by the developer)
• Last updated: October 20, 2026

Each restriction is built as a rule with two sections: Basic info (the gateway and, if relevant, the fee or partial-payment amount) and Conditions (what has to be true for the rule to fire). The plugin adds its own settings screen rather than a WooCommerce Settings tab, and you can give customers a plain-language reason when a gateway isn’t available instead of a generic checkout error.

Two honest limitations. First, the developer’s own changelog shows the free version has historically capped the number of active rules, with Pro removing that cap, so a store that needs more than a handful of conditional rules at once will hit the ceiling. Second, and more important if you’ve already moved to the new checkout: the plugin’s FAQ states plainly that partial payment does not support the WooCommerce checkout block, and requires the classic shortcode checkout ([woocommerce_checkout]) instead. If you’re on block-based checkout and specifically need the partial-payment feature, this isn’t the plugin for that part, even though its gateway-hiding rules themselves aren’t called out with the same restriction.

Conditional Payment Methods for WooCommerce

Conditional Payment Methods for WooCommerce, built by theDotStore, sits closest to WP Trio’s plugin in what it does: hide or show a gateway based on conditions, with unlimited rules even on the free version. Its particular strength is billing and shipping address fields specifically, down to first name, last name, and full address, not just country or state, which makes it a fit for B2B-style rules like restricting a net-terms payment option to a specific known billing company name.

• Price: Free, Pro from $119/year (Personal plan, 1 site; $299/year for 5 sites)
• Requires: WordPress 5.0+, PHP 5.6+
• Last updated: September 29, 2026

Setup also lives under WooCommerce > Settings > Payments, in a Conditions section the plugin adds. theDotStore’s own getting-started guide walks through a rule like disabling PayPal for orders above a set amount as the worked example, built from a condition category it calls product-specific rules, with billing and shipping fields as a separate condition category alongside it.

The honest caveat here is thinner install numbers than the other three (1,000 active installs against 4,000 to 10,000 for the rest), and it’s the only one of the four with a hard PHP floor (5.6) stated on its listing, worth a quick check if you’re still on an older hosting stack. Where it earns a look anyway is the address-field granularity: if your actual rule is “hide this gateway unless the billing company field matches a known wholesale account,” this is the plugin built for that case specifically, not a side effect of a broader rule engine.

How to pick

1. If your rule is simple (subtotal, shipping method, or address fields) and you want the least setup, start with Conditional Payments for WooCommerce (WP Trio). Its free tier covers most single-condition rules outright.
2. If the rule is really about product category or tag, and your catalog already separates expensive and cheap products cleanly, Payment Methods by Product & Country for WooCommerce is more direct than bolting a category check onto a general rule engine.
3. If you also need a surcharge on a gateway or a partial-payment deposit option for COD, and you’re on classic checkout rather than the checkout block, PiWeb’s plugin covers both in one install instead of running two plugins.
4. If the actual condition is a specific billing or shipping field value, not just country or state, Conditional Payment Methods for WooCommerce (theDotStore) is built around that case specifically.
5. If you’re running the WooCommerce checkout block and need more than gateway hiding, confirm block compatibility with the vendor before buying a Pro license. Only PiWeb’s documentation explicitly flags a block limitation (on its partial-payment feature); the others don’t document it either way, which is worth a direct support question before you pay.

FAQ

Do any of these plugins require editing theme or functions.php code?
No. All four add their own settings screen or a tab under WooCommerce’s existing Payments settings, and the rules are built through that interface.

Will restricting a payment method break WooCommerce Subscriptions or recurring orders?
None of the four plugins mention explicit WooCommerce Subscriptions compatibility on their listings. If you sell subscriptions, test a rule against a subscription product in a staging environment before relying on it, since a gateway hidden for the wrong condition on a recurring order can block renewal payments silently.

Can I use more than one of these plugins at the same time?
Technically yes, since they all hook into the same WooCommerce filter independently, but it gets hard to reason about which rule won when two plugins both have an opinion about the same gateway. Pick one plugin that covers your actual conditions rather than stacking two.

What happens to a customer if a rule leaves no payment method available at all?
By default, WooCommerce just shows a message that no payment methods are available, which looks broken to a shopper. PiWeb’s plugin lets you customize that message, and WPFactory’s Pro tier adds a fallback gateway specifically to prevent this state. Build and test your rules with an eye on this edge case, especially if you’re combining category and country restrictions that could overlap.

Do these plugins affect page speed?
Minimally. The filter they hook into only runs on the cart and checkout pages, not sitewide, so there’s no meaningful front-end performance cost from any of the four.

None of the four plugins above are built by ConicPlex, and nothing in our own plugin lineup covers conditional payment-gateway logic, so there’s no honest reason to work one in here. If your rule is more complex than any of these four can express, say a rule that spans cart contents, a loyalty tier, and a shipping zone all at once, that’s usually a sign it’s worth a custom plugin instead of stacking workarounds. Our WooCommerce development team builds that kind of checkout logic directly against the same gateway filter these plugins use, without the extra settings screens.

For related checkout customization, see our posts on adding an extra fee for Cash on Delivery or card payments, hiding a WooCommerce shipping method by product category, and adding an EU VAT number field to WooCommerce checkout. If you sell across multiple regions, our ecommerce industry page covers more of what we build for stores at that stage.

Sources

• Conditional Payments for WooCommerce (WordPress.org)
• Conditional Payments for WooCommerce Pro pricing (WP Trio)
• Payment Methods by Product & Country for WooCommerce (WordPress.org)
• Payment Methods by Product & Country for WooCommerce Pro pricing (WPFactory)
• PiWeb Disable Payment Method / Partial Payment for WooCommerce (WordPress.org)
• PiWeb Disable Payment Method Pro pricing
• Conditional Payment Methods for WooCommerce (WordPress.org)
• Conditional Payment Methods for WooCommerce Pro pricing (theDotStore)
• Getting Started with Conditional Payments for WooCommerce (theDotStore docs)