Payment Restrictions — Full Control Over Which Payment Methods Your Customers See

Stop showing every customer every payment option. With Payment Restrictions, you decide exactly which payment methods appear at checkout — based on who the customer is, how they're shipping, and how much they're spending.


---

The Problem

OpenCart lets you enable or disable payment methods globally. That's it. You can't show Bank Transfer only to wholesale customers. You can't hide Cash on Delivery for orders above €500. You can't restrict a payment method to a specific store or only when a certain shipping method is selected.

Payment Restrictions closes that gap — without touching core files and without conflicts.

---

How It Works

For each installed payment method, you configure an independent rule. Each rule has one of three modes:

• Show only when conditions match — the payment method is visible only when all selected conditions are met. Invisible otherwise.
  
• Hide when conditions match — the payment method is hidden when all selected conditions are met. Visible otherwise.
  
• No custom rule — OpenCart default behaviour. The payment method is unaffected.
  

---

Available Conditions

Each rule can combine any or all of the following conditions. A condition left blank means "apply to all".

• Customer group — target Retail, Wholesale, VIP, or any custom group. Supports the guest (not logged in) group.
  
• Excluded customers — specific customers who are always exempt from the rule, regardless of their group.
  
• Store — limit the rule to one or more stores in a multi-store setup.
  
• Shipping method — trigger the rule only when a specific shipping method is selected. Matches both exact codes and extension prefixes (e.g. "flat" matches "flat.flat").
  
• Minimum order total — apply the rule only when the cart total is at or above a threshold.
  
• Maximum order total — apply the rule only when the cart total is at or below a threshold.
  

All conditions within a rule must match simultaneously (AND logic). When no conditions are configured for a criterion, that criterion is considered satisfied for all values.

---

Debug Simulator

Before saving, test your rules without placing a real order. The built-in simulator inside the admin panel lets you select a customer group, a specific customer, a shipping method, a store, and an order total — then shows you exactly which payment methods would be visible and why, rule by rule, condition by condition.

---

Live Checkout Debug Panel

Enable the optional checkout debug mode to display a real-time panel on the checkout page (visible to admins only). It shows every installed payment method, whether it was allowed or blocked, and the exact reason — making it fast to diagnose rule issues in a live environment.

---

Feature Summary

• Per-payment-method rules — each method has its own independent configuration
  
• Three rule modes: show only, hide when matched, no rule
  
• Six condition types: customer group, excluded customers, store, shipping method, min total, max total
  
• AND logic across all active conditions
  
• Exclude specific customers from a rule regardless of their group
  
• Multi-store aware
  
• Shipping method prefix matching (e.g. "flat" matches "flat.flat")
  
• Built-in admin debug simulator — test rules before going live
  
• Live checkout debug panel for admin users
  
• Clean install via OpenCart's native extension installer (OCMOD / event system)
  
• No core file modifications
  
• Supports OpenCart 1.5 through 4.1.x
  

---

Compatibility

• OpenCart 4.0.x – 4.1.x
  
• OpenCart 3.0.x
  
• OpenCart 2.3.x
  
• OpenCart 2.0.x – 2.2.x
  
• OpenCart 1.5.x (1.5.6.4)
  

---

Installation

Upload the .ocmod.zip file through Extensions → Installer, then go to Extensions → Modules → Payment Restrictions and click Install. Configure your rules and save. That's it.

For OpenCart 1.5.x: upload the contents of the zip manually to your store root, then go to Extensions → Modules → Payment Restrictions and click Install. The module patches the checkout controller automatically and restores it cleanly on uninstall.