Payment and Shipping Restrictions

The base Sublogin package can store allowed payment and shipping methods for each buyer. Two global switches decide whether Magento enforces those lists.

These are per-sublogin restrictions, not Role rules and not spending limits.

Configure without blocking checkout

1. Leave both global filters disabled.
2. Edit every active sublogin and assign the methods that fit that buyer.
3. Test the buyer's usual cart and delivery address.
4. Enable Payment methods filter in staging and confirm one valid method remains.
5. Enable Shipping methods filter and repeat the test.

A configured method can still disappear because Magento considers it unavailable for the cart, country, currency, customer group or address. Sublogin only narrows Magento's valid result.

Payment examples

A purchasing account might be allowed to use purchase order and bank transfer but not a card. The exact method codes come from installed Magento payment modules.

Budget's Pay on Budget method is separate. It appears only when the Budget add-on is installed, enabled and valid for the current sublogin and cart.

Shipping examples

A warehouse buyer might use a freight method while an office buyer uses parcel delivery. Store the complete carrier and method combination, such as the value Magento exposes for that exact rate.

Address restrictions do not prove that a shipping rate is available. Always test the assigned address with the intended products and quantities.

No method appears

Check in this order:

1. Does Magento offer the method when the Sublogin filter is disabled?
2. Is the full method code assigned to this sublogin?
3. Is the global filter enabled at the correct website or store-view scope?
4. Does the address satisfy the carrier or payment module's own rules?
5. Does another module, such as Budget or a checkout customization, remove the method later?

Related: Address Management, Budget Management, and Common Issues.