Restrictions to cash on delivery and
Use Payment Suite for the documented workflow it is designed to support, without adding unrelated complexity.
Apply restrictions to cash on delivery and other Magento 2 payment methods, then add extra fees at checkout. Payment Suite combines payment availability controls with order-cost adjustments in one commercial toolkit for varied order situations.
Apply restrictions to cash on delivery and other Magento 2 payment methods, then add extra fees at checkout. Payment Suite combines payment availability controls with order-cost adjustments in one commercial toolkit for varied order situations.
Payment Suite combines two checkout functions: restricting payment methods and adding extra fees. Merchants can apply controls to cash on delivery or other payment options and introduce an additional charge where their checkout policy requires it.
This pairing is useful when the cost or availability of a payment method depends on the order context. A merchant can limit an unsuitable choice and account for an added operational cost through a checkout fee, rather than treating payment selection as identical for every cart.
The customer-facing result should remain transparent. Restrictions need to leave the shopper with a valid way to pay, and any fee should be clearly identified before the order is placed.
Payment Suite is most useful when merchants connect its documented capability to a real store workflow. Keep payment handling more controlled. The setup should remain understandable for both shoppers and store teams.
The extension stays focused on the documented capability above rather than adding unrelated complexity. Support a clearer payment experience. Merchants should keep labels, settings, and customer-facing behavior aligned with actual requirements.
Before wider rollout, merchants should validate representative scenarios that exercise this capability. The goal is a predictable Magento 2 workflow that remains clear across the relevant customer or admin journey.
A strong implementation starts with the store's real catalog, checkout, customer, or operational needs. Payment Suite should be configured around those needs and reviewed in context rather than treated as a generic one-size-fits-all feature.
Use Payment Suite for the documented workflow it is designed to support, without adding unrelated complexity.
Payment Suite can support a clearer experience when its core capability is matched to the store's real requirements.
Keep the workflow easier to understand for the people who use it, whether that is shoppers, administrators, or both.
Configure the extension around representative store scenarios and keep the resulting behavior aligned with business needs.
Use clear labels, settings, and validation so the extension behaves consistently across the relevant Magento 2 journey.
Test representative scenarios before wider use and confirm that the documented capability fits the store's version, data, and workflow.
Apply restrictions to cash on delivery and other Magento 2 payment methods, then add extra fees at checkout. Payment Suite combines payment availability controls with order-cost adjustments in one commercial toolkit for varied order situations.
Configure Payment Suite around the Magento 2 workflow the store actually needs.
Keep labels and presentation understandable wherever the feature appears.
Validate realistic products, customers, carts, orders, or admin actions before wider rollout.
Use the extension for its documented purpose rather than adding unrelated complexity.
Review the feature together with the store's existing catalog, checkout, customer, or operational setup.
Keep the feature understandable across the relevant customer or admin journey.
Introduce the capability in a controlled way and review representative scenarios before wider use.
Confirm that the documented capability matches the store workflow it is intended to support.
Payment Suite can support this scenario when its documented capability matches the store's actual requirements.
Use the extension to make this workflow clearer and more repeatable without extending beyond the verified feature scope.
This is a practical fit when the merchant already has a defined Magento 2 process that benefits from the extension's core capability.
Validate representative store data and user journeys so the feature supports the intended outcome in real use.
Tell us what you need and our Magento team will get back to you.
Sample current maintenance update record for Payment Suite. This test changelog entry does not add claims beyond the documented product capabilities and is used to validate the MageHex Change Log layout.
Sample workflow refinements record for Payment Suite. This test changelog entry does not add claims beyond the documented product capabilities and is used to validate the MageHex Change Log layout.
Sample compatibility maintenance record for Payment Suite. This test changelog entry does not add claims beyond the documented product capabilities and is used to validate the MageHex Change Log layout.
Sample stability improvements record for Payment Suite. This test changelog entry does not add claims beyond the documented product capabilities and is used to validate the MageHex Change Log layout.
Sample storefront refinements record for Payment Suite. This test changelog entry does not add claims beyond the documented product capabilities and is used to validate the MageHex Change Log layout.
Sample configuration refinements record for Payment Suite. This test changelog entry does not add claims beyond the documented product capabilities and is used to validate the MageHex Change Log layout.
Sample responsive presentation update record for Payment Suite. This test changelog entry does not add claims beyond the documented product capabilities and is used to validate the MageHex Change Log layout.
Sample maintenance release record for Payment Suite. This test changelog entry does not add claims beyond the documented product capabilities and is used to validate the MageHex Change Log layout.
Sample usability improvements record for Payment Suite. This test changelog entry does not add claims beyond the documented product capabilities and is used to validate the MageHex Change Log layout.
Initial sample release record for Magento 2 Payment Suite Extension in the MageHex catalog test dataset.
Join MageHex updates and receive your discount code.
MAGEHEX20
Use this code on your first order.