Rule-Based Restrictions

Use payment profiles to control which payment methods are available for specific customer and cart situations.

Screenshot placeholder: checkout filtered by the matching payment profile File: ./_screenshots/rule-based-restrictions.png

How It Works

At checkout, the extension evaluates profiles by priority. When a profile matches the current website, customer context, and optional conditions, its configured methods are used.

Matching Inputs

A profile can match based on:

Website
Customer groups
Individually assigned customers
Optional conditions (for example subtotal, country, product attributes)

Typical Rule Types

1. Customer Group Rules

Create profiles for groups like Wholesale, Corporate, VIP, or NOT LOGGED IN.

2. Individual Customer Rules

Add selected customers to a profile when you need account-level exceptions.

3. Condition-Based Rules

Use conditions to make profiles context-aware, such as:

Minimum subtotal
Shipping country
Product category
Shipping method

Priority System

If more than one profile could apply, priority decides evaluation order:

Lower number = evaluated first
First matching profile controls the result

Example:

Priority 10: VIP profile
Priority 50: Wholesale profile
Priority 999: Fallback profile

Practical Setup Pattern

Create specific profiles first (VIP, high-value orders, special regions)
Create broader profiles next (standard wholesale/retail)
Keep a fallback profile with low priority (high number)

Best Practices

Keep profile names explicit (who + when + what)
Avoid many overlapping profiles with similar conditions
Use unique priorities
Test at least one checkout path per target customer type

Limitations

The core Payment Profile module does not provide its own REST API endpoints.
If you need API-based management, use a dedicated add-on or custom integration.