Payment Restriction Pro for Magento 2
SKU: MGD-M2XP-PMT-PR
12 Months Included Support, with options to extend · 30 Days money-back guarantee · Renewals 40% off
Overview
Not every payment method belongs on every order.
Enhance your Magento 2 store’s payment flexibility and improve customer satisfaction with MagedIn Payment Restriction Pro. This powerful extension allows you to restrict payment methods based on a variety of conditions, giving you the control to tailor payment options to specific customer segments and business needs.
Why offering every method to everyone backfires
Each open method looks harmless. Together, they invite fraud and cost.
Fraud-prone methods
A high-chargeback method left open on risky orders quietly funds your fraud losses.
COD where it fails
Cash on delivery in regions with high refusal rates turns into returns and shipping you eat.
Offline methods, wrong hands
Bank transfer or purchase order exposed to retail and guests invites unpaid, stuck orders.
Costly gateways on thin orders
An expensive processor handling low-value orders can spend more in fees than the order makes.
Why choose this extension
Turning a method off is the easy 20%. This is built for the other 80%.
It respects your store
No checkout fork, no core rewrites. It listens on Magento's own payment_method_is_active event through a single observer — so it survives upgrades and any developer can reason about it.
It speaks Magento, not a DSL
Rules are built in the native condition builder you already use for cart price rules, combining cart, product and customer conditions with AND/OR logic. There is nothing proprietary to learn.
It targets with precision
Scope rules per website, order them by priority, schedule them with From/To dates, and choose whether each applies to the storefront only or to admin-created orders too.
The alternative is blunt
Disabling a method in payment config removes it for everyone; declining orders by hand at the payment step is slow and error-prone. Rules hide the right method for the right order, automatically.
Features
Everything you need to control checkout — nothing to hand-hold.
Restrict methods by rule
Hide a payment method the instant an order matches — evaluated on Magento's standard method-availability check, wherever it runs.
No learning curve
The native Magento condition builder — the same AND/OR interface you already know from cart price rules.
Cart & order conditions
Match on subtotal, quantity, weight, shipping method and destination country, region or postcode.
Customer conditions
Target by customer group, email, or logged-in versus guest status.
Product conditions
Restrict based on specific products, categories, or product-attribute combinations in the cart.
Pick the exact methods
Choose precisely which payment methods each rule hides — one, several, or a whole group.
Scope & priority
Scope each rule per website and process them in the priority order you set — only active rules apply.
Schedule & admin control
From/To dates switch rules on and off, and an apply-in-admin toggle extends a rule to admin-created orders.
Manage rules like a pro
A full admin grid — search, filter, sort, page — with Edit / Delete / Duplicate and status mass actions.
How it works
Define who sees a method and who doesn't — Magento does the rest.
Rules are built with the native Magento condition builder — the same interface you use for cart price rules. No proprietary syntax to fight.
- Combine cart, product and customer conditions with AND/OR — evaluated against the quote at checkout.
- Scope by website, order rules by priority, and schedule them with From/To dates.
- Pick exactly which payment methods a rule hides — storefront only, or in admin too.
What the shopper sees
The right methods appear — the restricted ones simply aren't offered.
$40 basket
New region
$5,000 PO
Low value
Runs on Magento's own check
Restrictions are evaluated on the standard payment_method_is_active event, so a hidden method is hidden everywhere Magento asks — no checkout fork to maintain.
Scoped, ordered, dated
Only active rules, scoped to the current website and sorted by priority, are evaluated — and only a rule that targets the method under check can hide it.
Storefront or admin, your call
An apply-in-admin flag decides whether a rule also constrains admin-created orders, or applies to the storefront alone.
Use cases
Three rules you could set up this afternoon.
Hide COD in high-risk regions
Cash on delivery in certain areas comes back as refusals, returns and shipping you absorb.
Add a rule with shipping country or region conditions that restricts Cash on Delivery.
COD disappears for those destinations and stays available everywhere else.
Wire transfer for wholesale only
Offline bank transfer should be a B2B privilege — not something retail or guests can pick and leave unpaid.
Restrict Bank Transfer whenever the customer group is Retail or Guest.
Only wholesale customers ever see the offline method.
Block a gateway above a threshold
One gateway should not handle very large orders — for cost, limits or risk.
Restrict that method when the subtotal is greater than your threshold.
Above the line it is hidden; the appropriate methods remain.
Compatibility
Confirmed to run where you run.
Driven by this product's real edition and version compatibility attributes. Confirm the exact tested patch range with MagedIn for your environment.
- Magento Open Source (Community)
- Magento Commerce (Enterprise)
- Magento Commerce Cloud
- Magento B2B
- Magento 2.3.x
- Magento 2.4.x
Installation
Four commands. No static deploy on Hyvä.
Require the package with the Composer key you receive by email, enable, upgrade, and flush.
- 01 Require the package via Composer using the key you received by email.
- 02 Enable the module with bin/magento module:enable.
- 03 Run setup:upgrade to apply the module's schema and data.
- 04 Flush the cache and you're done.
$ composer require magedin/module-payment-restriction
$ bin/magento module:enable
$ bin/magento setup:upgrade
$ bin/magento cache:flush
✓ No static content deploy needed on Hyvä
Specifications
The kind of extension a developer signs off on.
- Support Period
- 12 Months Included Support, with options to extend
- Refund Period
- 30 Days
- Extension Code
- 100% Open Source Code
- Editions Compatibility
- Magento Open Source (Community), Magento Commerce (Enterprise), Magento Commerce Cloud, Magento B2B
- Versions Compatibility
- Magento 2.3.x, Magento 2.4.x
Changelog
What's changed, release by release.
Release notes for this extension are coming soon.
FAQ
Questions, answered.
Still unsure whether it fits your setup? Talk to our team before you buy.
Do I have to customize checkout or edit my payment configuration?
No. The extension listens on Magento's own payment-method availability event through a single observer, so it works with the native checkout and your existing payment methods — no core rewrites, no checkout fork.
How do I define when a payment method is restricted?
With Magento's native condition builder — the same interface you know from cart price rules. Combine conditions with AND/OR logic over cart, product and customer attributes, then choose which methods the rule hides.
Which payment methods can I restrict?
Any active payment method in your store. Each rule targets exactly the methods you select — one, several, or a whole group — so a rule can hide, say, only Cash on Delivery while leaving everything else available.
Can I restrict by customer group, destination country or order total?
Yes. Conditions cover customer attributes (customer group, email, logged-in vs. guest), cart attributes (subtotal, quantity, weight, shipping method and destination country, region or postcode) and product attributes (specific products, categories, or product-attribute combinations).
Can I run more than one restriction rule?
Yes. Only active rules are evaluated, scoped to the current website and processed in the priority order you set. Each rule targets its own set of payment methods, so several rules can coexist without stepping on each other.
Can I schedule restrictions, or limit them to the storefront?
Yes. Every rule supports optional From/To dates so it switches itself on and off, and an apply-in-admin toggle decides whether it also constrains admin-created orders or applies to storefront checkout only.
Does it work with third-party payment methods?
Yes. It operates on Magento's standard method-availability check rather than any one gateway, so any method registered through the normal payment system — including PayPal, Braintree, Stripe and Authorize.Net — can be restricted.
Can a developer add custom condition types?
Yes. The condition option list is dispatched through the magedin_payment_restrictions_select_options_before_return event, so a developer can add custom conditions from their own module without editing this one. Rules are managed in the admin.
Customer Reviews
We previously paid developers to write custom logic to restrict payment methods based on cart conditions. That’s expensive and hard to maintain. This module replaced all that with a clean UI and full flexibility. We’ve since created different rules for promotions, loyalty customers, and even flash sales. It’s like having a payment rule engine baked into Magento.
I’ve worked with a lot of Magento extensions, and Payment Restriction Pro stands out. It’s lightweight, well-coded, and fits seamlessly into the admin panel. We’re using it to restrict high-risk payment methods by country, subtotal, and even specific SKUs. The fact that it supports rule duplication and mass actions from the grid is just icing on the cake. Our client couldn’t be happier.
We needed to hide specific payment options for wholesale customers and show them only to retail shoppers. This extension made it incredibly easy. The rule builder is familiar — just like Magento’s promo engine — and the conditions are flexible enough to target almost anything. We now run cleaner checkouts, reduce failed payments, and support different regions without confusion. Game-changer!
Write Your Own Review
Only registered users can write reviews. Please Sign in or create an account