什么是 Payment Method Restrictions & Rules for Magento 2？
Show or hide Magento 2 payment methods using flexible rules based on cart total, country, customer group, product, category, zip code, shipping method or schedule. Custom-built, installed and supported by ECOSIRE. Built to order by ECOSIRE for Magento 2 / Adobe Commerce (build-to-order) — indicative price from $149.00 USD; request a quote for a scoped proposal.
产品详细信息以英文显示。翻译即将推出。
示意预览Show or hide Magento 2 payment methods using flexible rules based on cart total,
country, customer group, product, category, zip code, shipping method or schedule. Custom-built, installed and supported by ECOSIRE.
核心功能
Restrict payment methods by billing or shipping country and region
Postcode / zip pattern rules (ranges, wildcards, exact match)
Customer-group rules (e.g. hide COD for wholesale, allow PO for B2B)
Cart subtotal / grand total thresholds with min and max per method
Product- and category-in-cart conditions (block methods for restricted SKUs)
Shipping-method conditions (e.g. only prepaid for express shipping)
Schedule-based availability with active date/time windows
AND/OR condition groups with rule priority ordering
Per-store-view and per-website scope using Magento config scopes
Works across web checkout, REST carts API, and GraphQL availablePaymentMethods
Filters core and gateway methods (PayPal, Braintree, Stripe, Adyen, Authorize.Net)
Dedicated admin grid with enable/disable toggle and ACL-protected access
按需定制，全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Magento 2 上构建、配置并安装。
- 3
上线 + 支持
约 2–4 周内上线，并提供上线后的支持期。
关于此产品
Magento 2 ships with only blunt payment controls — a per-method "Applicable Countries" list and a min/max order total. There is no native way to say "hide Cash on Delivery for wholesale customers", "only offer bank transfer above $2,000", "block credit card for hazmat SKUs", or "disable a method on weekends". This extension closes that gap with a real rule engine.
ECOSIRE builds this as a proper Magento 2 module under app/code/Ecosire/PaymentRestrictions, wired through di.xml. The core mechanism is a plugin (interceptor) on Magento\Payment\Model\Method\Adapter::isAvailable() plus an observer on the payment_method_is_active event, so every method — core (Check/Money Order, Bank Transfer, COD) and gateway-based (PayPal, Braintree, Stripe, Authorize.Net, Adyen) — is filtered consistently across the website, REST guest-carts/carts payment-information endpoints, and the GraphQL setPaymentMethodOnCart / availablePaymentMethods resolvers used by PWA Studio and headless storefronts.
Rules are managed in the Adobe Commerce / Magento Open Source admin under a dedicated ACL resource, evaluated against the live quote: billing/shipping country and region, postcode patterns, customer group, cart subtotal/grand total, currency, the products and categories in the cart, the selected shipping method, and an optional active date/time window. Rules support AND/OR conditions, priority ordering, and store-view scope.
Because it is build-to-order, ECOSIRE adapts the rule conditions to your exact catalog, gateways and edge cases, installs it on your environment, runs setup:upgrade and cache/DI compilation, and supports it after launch. Honest lead time below — this is not an instant Marketplace download.
你得到什么
- Custom Magento 2 module Ecosire/PaymentRestrictions installed under app/code (or via Composer artifact)
- di.xml-wired plugin on Payment Method Adapter isAvailable() plus payment_method_is_active observer for consistent filtering
- Admin rule manager UI with grid, condition builder, priority and store-view scope, protected by a dedicated ACL resource
- GraphQL and REST coverage so PWA/headless and API checkouts honor the same rules
- Installation on your Magento 2.4.x environment with setup:upgrade, di:compile and cache flush performed by ECOSIRE
- Configuration of your initial rule set plus admin handover guide and post-launch support window
这是给谁的
B2B / Wholesale Merchant
Needs to expose purchase-order and bank-transfer methods only to specific customer groups while hiding Cash on Delivery and cards from wholesale accounts.
Cross-Border Retailer
Sells into multiple countries and must show region-appropriate gateways (e.g. local methods per country, no COD outside delivery zones) without maintaining brittle core country lists.
Operations / Risk Manager
Wants to block high-risk or high-value payment methods above a cart threshold, for restricted SKUs, or outside business hours to reduce fraud and chargebacks.
Payment Method Restrictions & Rules for Magento 2 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Magento 2 原生 |
|---|---|---|---|---|
| Restrict by country/region | 包含 | 包含 | 包含 | 部分支持 |
| Restrict by customer group | 包含 | 包含 | 部分支持 | 不包括在内 |
| Restrict by product / category in cart | 包含 | 包含 | 部分支持 | 不包括在内 |
| Restrict by shipping method | 包含 | 包含 | 部分支持 | 不包括在内 |
| Schedule-based (date/time window) availability | 包含 | 部分支持 | 不包括在内 | 不包括在内 |
| Zip / postcode pattern rules | 包含 | 包含 | 部分支持 | 不包括在内 |
| Enforced on GraphQL & REST (headless) checkout | 包含 | 部分支持 | 部分支持 | 部分支持 |
| Built, installed & supported for you | 包含 | 部分支持 | 不包括在内 | 不包括在内 |
关于Payment Method Restrictions & Rules for Magento 2的常见问题
How long until the extension is delivered and installed?
Because each build is tailored to your catalog, gateways and rule logic, typical delivery is 5 to 10 business days from requirements sign-off. We scope your exact conditions first, build and test the module against your Magento 2.4.x version, then install it on your staging environment for review before production. Complex multi-gateway or headless GraphQL setups may add a few days — we confirm a firm date in writing before starting.
What ongoing support and updates do I get after launch?
Every build includes a post-launch support window for bug fixes and adjustments to your rules. We test compatibility against your Magento minor-version upgrades and can issue patched releases as your gateways or catalog change. Because you own the module source under app/code, there is no per-seat license lock-in; extended support and maintenance retainers are available if you want ECOSIRE to manage upgrades long term.
Will it work with my payment gateway (PayPal, Stripe, Adyen, Authorize.Net)?
Yes. The module filters at the Magento payment-method abstraction layer (isAvailable() and the payment_method_is_active event), so it applies uniformly to core methods and any gateway built on the standard payment adapter — including PayPal, Braintree, Stripe, Adyen and Authorize.Net. If you run a custom or non-standard gateway, we verify and adapt the integration during the build.
Does this work with a headless / PWA Studio storefront?
Yes. Rules are enforced in the GraphQL resolvers for availablePaymentMethods and setPaymentMethodOnCart, as well as the REST carts payment-information endpoints, so a PWA Studio or custom headless frontend sees the same filtered method list as the default Luma checkout. We test the GraphQL path explicitly when your storefront is headless.
Does it work on both Adobe Commerce and Magento Open Source?
Yes. The module uses only standard framework APIs (service contracts, plugins, observers, ACL, config scopes) that exist in both Magento Open Source and Adobe Commerce, including the B2B customer-group and shared-catalog scenarios. We build and test against your specific edition and 2.4.x patch level.
相关模块
申请报价
Payment Method Restrictions & Rules for Magento 2
Show or hide Magento 2 payment methods using flexible rules based on cart total, country, customer group, product, category, zip code, shipping method or schedule. Custom-built, installed and supported by ECOSIRE.
- Restrict payment methods by billing or shipping country and region
- Postcode / zip pattern rules (ranges, wildcards, exact match)
- Customer-group rules (e.g. hide COD for wholesale, allow PO for B2B)
- Cart subtotal / grand total thresholds with min and max per method