Show the right payment methods to the right customers every time
Combine customer, customer group, country, product and sales-channel criteria in one rule to block or allow payment methods at checkout — with impact preview and conflict detection before you save.
Odoo's built-in payment configuration is global or country-based at best. Compliance teams need certain gateways blocked in certain countries, sales needs COD withheld from high-risk customers, and B2B accounts need invoice-only terms — but combining customer, product, country and channel criteria into one rule isn't possible out of the box, so admins end up testing changes live at checkout.
Payment Method Restriction adds a rule engine that combines customer, customer group, country, product, product category and sales channel in a single Block or Allow-Only rule. Every rule shows its impact — affected customers and providers — and warns about conflicts with existing rules before it goes live, so admins configure with confidence instead of guessing.
Everything you need to control checkout payments
Every capability below is implemented in the module.
Multi-Criteria Rules
Combine customer, customer group, country, product, product category and sales channel in one rule, evaluated in priority order.
Block or Allow-Only Modes
Remove specific payment providers and methods from checkout, or restrict checkout to only the ones you list.
Dynamic Checkout Filtering
Restricted providers and methods never appear at checkout — enforced directly on Odoo's payment compatibility hooks for Website and Sales orders.
Impact Preview
See the affected customer count and a plain-language summary of what a rule blocks or allows before you activate it.
Conflict Detection
Get a warning when two active rules produce contradictory behavior for the same customer, product or country combination.
Rule Templates
Start from ready-made presets like "Block COD for new customers" or "B2B invoice-only" instead of building every rule from scratch.
Bulk Assignment
Apply a restriction across one or more customer groups in a single wizard instead of creating rules one at a time.
Centralized Management
One dedicated menu covers every restriction type, replacing settings scattered across unrelated configuration screens.
Audit Trail
Every rule change is tracked in the chatter, showing who changed what and when.
How it works
Define Criteria
Pick the customers, countries, products or sales channels a rule should apply to.
Choose Providers
Select the payment providers or methods to block, or the ones to allow exclusively.
Review Impact
Check the affected-customer count and conflict warnings before activating.
Activate
Save the rule; restricted payment methods disappear from checkout immediately.
See it in action
Restriction rules, templates and bulk assignment — all from one dedicated menu.
The Restriction Rules list shows every active rule with its mode, channel and targeted providers at a glance.
Each rule form surfaces a live impact summary and a conflict warning banner, plus a smart button to the affected customers — no more configuring blind.
Country and product criteria combine with customer and channel criteria in the same rule — here restricting a provider to Belgium only.
Pre-built templates like "Block COD for new customers" and "B2B invoice-only" give admins a starting point instead of a blank rule.
The Bulk Assignment wizard applies a restriction across multiple customer groups in one step.
Frequently asked
Does this work with Website Sales checkout?
Yes. Restricted providers and payment methods are removed from checkout on Website Sales and standard sales orders as soon as a matching rule is active.
What happens when two rules overlap?
The rule form shows a conflict warning when active rules produce contradictory behavior for the same customer, product or country combination, so you can adjust priority or scope before it affects a live checkout.
Can I combine multiple criteria in one rule?
Yes. A single rule can combine customer, customer group, country, product, product category and sales channel criteria — evaluated together, not as separate rules.
Is there an audit trail of rule changes?
Yes. Every restriction rule inherits chatter tracking, so changes to mode, providers, and criteria are logged with who made them and when.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Empowering growth through technology.
Payment Method Restriction gives Odoo admins a single, self-service rule engine to control which payment methods appear at checkout — by customer, country, product and channel — with impact preview and conflict detection built in.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 599 |
| Technical Name |
cerevantix_payment_method_restriction |
| License | OPL-1 |
| Website | https://www.cerevantix.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module