Payment Method Restrictions & Rules for Magento 2

Key Features

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

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Magento 2.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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.

What you get

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

Who this is for

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.

How Payment Method Restrictions & Rules for Magento 2 Compares

Criterion	ECOSIRE	Custom Build	Competitor
Restrict by country/region	Included	Included	Included
Restrict by customer group	Included	Included	Partial support
Restrict by product / category in cart	Included	Included	Partial support
Restrict by shipping method	Included	Included	Partial support
Schedule-based (date/time window) availability	Included	Partial support	Not included
Zip / postcode pattern rules	Included	Included	Partial support
Enforced on GraphQL & REST (headless) checkout	Included	Partial support	Partial support
Built, installed & supported for you	Included	Partial support	Not included

Frequently Asked Questions about 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.