Magento 2 Extension Payment Profiles / Payment Restrictions

It controls which installed payment methods Magento may show for a particular checkout. SoftwareSilo uses allow-list profiles assigned to customer groups or individual accounts and refined by website, cart conditions, and priority.

No. It neither processes transactions nor stores cards. The product name refers to profiles of allowed Magento payment methods, not customer payment credentials.

It suits B2B, wholesale, dealer, mixed B2B/B2C, and multi-website stores where invoice, bank transfer, purchase order, card, PayPal, cash on delivery, or other installed methods depend on the buyer and order.

Magento Open Source includes payment methods and method-level settings, but not a general profile workflow for assigning an approved set to selected customer accounts and groups. SoftwareSilo adds that layer.

Yes. A profile can be assigned to one or more Magento customer groups, including the guest group when a controlled public policy is required.

Yes. The Admin form includes a customer assignment grid so a profile can be attached directly to selected accounts without creating another customer group.

Yes. Multiple customer accounts can be assigned to the same profile, and an account may be covered by both direct and group assignments.

Yes. Profiles use Magento's sales-rule condition model and can evaluate the quote address, totals, quantities, product combinations, and attributes available in the Magento condition tree.

Yes, when the desired total is available in the condition builder. The profile can allow invoice only when its complete assignment and condition context matches.

Yes. Product combination and attribute conditions can narrow a profile. Test configurable, bundle, virtual, and mixed carts with the exact attributes used by the project.

Yes. Every profile belongs to one Magento website. Its method choices are loaded for that website, and profiles assigned to another website are ignored for the current quote.

It supports website-specific profiles. Country and address logic can also come from Magento conditions or the payment method itself. Plan separate profiles when websites have distinct gateway configurations.

Priority accepts values from 1 to 999, with lower numbers evaluated first for the primary matching assigned rule. Use a documented numbering scheme and test overlapping assignments.

The module validates assigned profiles against the current quote. Where a rule-derived set and explicitly assigned sets both contribute, the result is narrowed to methods allowed by both contexts.

A store configuration controls the no-match behavior. Depending on that setting, Magento can retain its normal methods or end with no allowed profile methods. Choose and test the policy deliberately.

No. Payment Profiles narrows Magento's available choices. It does not reactivate a method disabled by its gateway, country, currency, total, credentials, configuration, or another valid availability check.

Yes, through the Magento Not Logged In customer group and applicable conditions. Create and test a guest profile if guests should receive a controlled set.

The module uses Magento's payment-method availability pipeline and has integration coverage for admin-order quote contexts. Custom admin workflows and installed gateways should still be tested in the project.

It filters Magento payment availability in REST and headless contexts that use the standard quote pipeline. The module does not provide a separate public API for creating or managing profiles.

No public profile-management endpoints are included. The module contains internal repositories and a protected Admin AJAX endpoint for website-specific method options.

No. It controls availability only and does not change quote or order totals. Use a dedicated payment-fee solution when surcharges are required.

No. Credit decisions, limits, open receivables, and collection remain in ERP, accounting, Adobe Commerce B2B, or another dedicated system. Payment Profiles should consume a reliable customer status.

No. It can control whether an installed purchase-order payment method is available, but it does not create approval chains. Adobe Commerce B2B provides broader company PO workflows.

SoftwareSilo centers an allowed set assigned to customer groups and individual accounts. Amasty centers blocking rules and publishes schedules, messages, purchase-history checks, and a broader restriction catalog.

SoftwareSilo is a focused account-aware allow-list module. Mageplaza publishes broader show/hide rules and offers Payment Suite capabilities such as payment fees. Compare the exact conditions and checkout channels required.

No. It offers focused payment availability rules. Adobe Commerce B2B also includes company accounts, Payment on Account, company credit, permissions, and purchase-order approvals.

Test a matrix of customer, group, website, cart, product, address, total, guest status, admin orders, API carts, and gateway states. Verify the final visible methods, not only the saved Admin configuration.

The license is valid for one Magento installation, including multi-website operation. In addition, the module may be installed on any number of development or staging servers. You can find further details in our license terms.

Installation and configuration are not included in the price. On request, we can support you with a smooth integration into your system.

Composer is PHP's package manager, and Magento 2 uses it to install modules and their dependencies. After purchase, the commands for your module are available under Licenses in your customer account. First add the private SoftwareSilo repository and your license token. Then install the listed package with composer require and run php bin/magento setup:upgrade and php bin/magento cache:clean.

You can pay by credit card (Stripe) or bank transfer (prepayment). For credit card payments, the order is processed immediately and the access credentials are provided directly in a separate follow-up email.

After credit card payment, you immediately receive access credentials to obtain the module via Composer. For bank transfer, access is granted once the invoice is paid.

Custom requests are no problem. We tailor our Magento 2 modules to your project and maintain a dedicated internal version so we always know exactly what runs on your system for support.

On each module detail page, you can request your own demo instance and test the module intensively for 7 days. However, we do not provide a local demo version.

No, the source code of our modules is not encrypted. If you need a customization, feel free to send us a request. We will get back to you promptly with a non-binding quote.

You can add a support package to your order. It includes assistance as well as updates and upgrades related to the module. No continuous subscription is required.

You can complete the license update here. If you have an active support package, you receive updates automatically via Composer. If your support package has expired, you can renew your license here or in your account.

You can reach us anytime via eMail.