YITH Payment Method Restrictions makes payment options contextual: gateways show or hide based on cart contents, order amount, shipping destination, user role, or coupons – the rules reality demands. COD only for domestic orders; bank transfer hidden under $50; card processing required for subscription products; wholesale roles seeing invoice payment – every store with diverse payment methods eventually needs conditional availability, and WooCommerce’s default all-methods-always model breaks on the first edge case. Against the suite’s payment tools like YITH Dynamic Pricing per Payment Method (pricing methods) and the broader WooCommerce family, this plugin owns the availability logic – which methods appear when.
The 1.5x line maintains steady cadence. For stores with mixed payment rails or regional constraints, it’s checkout correctness in plugin form.
Competitive Features
- Cart-based rules – products/categories gate methods
- Amount thresholds – order value gates options
- Geographic rules – country-limited availability
- Role-based methods – wholesale sees invoice, retail sees cards
- Coupon interactions – methods gated by discounts
- Multiple rule combination – conditions stack
- Clear messaging – hidden methods explained optionally
Key Features
- Include/exclude product lists – precise catalog scoping
- Shipping-class rules – bulky goods restrict carriers of methods
- Time-based rules – methods on schedules
- Fee awareness – restricted methods’ costs considered
- Default selection logic – sensible method pre-choice
- Translation ready – multilingual compatible
Comparison with Competitors
YITH Payment Method Restrictions vs gateway settings
| Aspect | Conditional restrictions | Gateway-level settings |
|---|---|---|
| Granularity | Cart/product/role/location | Global enable only |
| COD limits | Per country, per amount | All or nothing |
| Subscription rules | Method-gated by product | Impossible |
| Fit | Real-world constraints | Toy-model stores |
Bottom line: Gateway settings toggle methods globally; real commerce needs conditionality – COD domestically only, bank transfer above thresholds, invoice for wholesale. The plugin provides the rule layer WooCommerce core lacks.
YITH Payment Method Restrictions vs conditional fee plugins
| Aspect | YITH Restrictions | YITH Payment Pricing |
|---|---|---|
| Question answered | “Which methods show?” | “What do methods cost?” |
| Model | Availability logic | Fee logic |
| Together? | Yes | Yes |
Bottom line: YITH Payment Method Pricing prices methods; this plugin gates their availability – different questions, complementary plugins for stores steering payment behavior both ways.
Recommended Stack – method rules pair with quantity constraints: combine with WooCommerce Subscriptions so subscription products gate to the card-processing methods their recurring billing requires.
Official Changelog
Version 1.58.0
Release Date: August 24, 2026
- Feature release: rule-combination and messaging refinements.
Version 1.57.0
Release Date: July 12, 2026
- Maintenance release: WooCommerce compatibility updates.
Version 1.56.0
Release Date: May 15, 2026
- Maintenance release: stability and rule-evaluation fixes.
Frequently Asked Questions
When would a store restrict payment methods?
Real-world constraints everywhere: COD only where couriers collect; bank transfer for large B2B orders; card-only for subscriptions; invoice payment for wholesale roles; methods hidden on discounted orders where margins thin.
Can rules combine?
Yes – method available only when “cart contains product X AND destination is US AND order exceeds $100” – the stacked conditions real policies need.
Do hidden methods explain themselves?
Optionally – a message explains why COD is unavailable (region restrictions), converting confusion into understanding at checkout.
Can I gate methods by user role?
Yes – wholesale roles see invoice and bank transfer; retail sees cards and wallets – the B2B/B2C split that payment policy usually requires.
Does it work with all gateways?
Yes – restrictions apply at the standard WooCommerce payment-gateway level, so any registered gateway (core or third-party) can be conditionally available.
Leave a Reply