Smart Gateway Manager for WHMCS

$49.00 USD

The Smart Gateway Manager For WHMCS controls payment gateway availability based on cart products, product groups, and client account age for a cleaner, more relevant checkout.

Included:

  • 7-Day Free Trial Access
  • Multi-Level Technical Support
  • One-Time Payment, No Recurring Fees
  • Lifetime Owned License
  • Instant Download After Purchase
  • Latest WHMCS Compatible

Description

Product Description

The Smart Gateway Manager For WHMCS gives administrators precise control over which payment methods customers can use for selected products and product groups.

Create an eligibility rule for each payment gateway and assign the products or groups that permit it. You can also require a minimum client account age, allowing sensitive or higher-risk payment methods to remain hidden from new customers until their account meets your requirement.

The module automatically filters gateways during checkout and on invoice payment pages, selects an eligible fallback when necessary, and validates the submitted payment method before the order is accepted.

How It Works

  1. Select a Gateway: Choose one of the active payment gateways configured in WHMCS.
  2. Assign Products or Groups: Select the products and product groups that make the gateway available.
  3. Set Client Eligibility: Optionally require the customer’s WHMCS account to be a minimum number of days old.
  4. Customer Starts Checkout: The module compares the cart products and client account age with every configured gateway rule.
  5. Gateways Are Filtered: Only eligible payment options remain available to the customer.
  6. Checkout Is Validated: The selected gateway is checked again before the order is accepted.
  7. Invoice Rules Continue: The same product and account eligibility rules are applied when customers view or change payment methods on invoices.

Key Features

  • Product-Based Gateway Rules: Make a payment method available only when selected products are present.
  • Product Group Rules: Apply one gateway rule to every product within selected WHMCS product groups.
  • Combined Product Selection: Use individual products and complete product groups within the same rule.
  • Minimum Client Age: Require a customer account to exist for a specified number of days before a gateway becomes available.
  • Guest Checkout Defaults: Select the payment methods shown to visitors who have not logged in.
  • Dynamic Checkout Filtering: Adjust the payment gateway list according to the products currently in the cart.
  • Invoice Gateway Filtering: Apply eligibility rules to payment choices displayed on WHMCS invoice pages.
  • Automatic Fallback Selection: Replace an ineligible selected gateway with the first available valid option.
  • Checkout Validation: Prevent an unavailable payment method from being submitted or retained through a bypass attempt.
  • Invoice Gateway Protection: Restore an eligible fallback if an invalid gateway change is attempted on an invoice.

Product and Group Control

Create broad or highly specific payment rules according to your product catalog.

  • Entire Product Groups: Enable a gateway for all current products inside a selected group.
  • Individual Products: Target precise services, including hidden WHMCS products.
  • Mixed Cart Evaluation: Make the gateway available when at least one product in the cart matches its rule and all other eligibility requirements are satisfied.
  • Invoice Product Detection: Identify hosting products associated with invoice items and apply the appropriate gateway rules.
  • Unrestricted Gateways: Keep gateways without a configured rule available to logged-in customers.

Client Account Age Rules

Product eligibility can be combined with customer account history for additional payment control.

  • Set a separate minimum account age for each managed gateway.
  • Use zero days when new clients should receive immediate access.
  • Hide selected payment methods until the account reaches the required age.
  • Require both a matching product and sufficient account age before displaying the gateway.

Guest Checkout Management

  • Choose multiple default gateways for customers who are not logged in.
  • Limit initial checkout options before WHMCS can evaluate a known client account.
  • Leave the guest selection empty to retain the normal WHMCS default gateway behavior.
  • Manage guest payment defaults from the same addon administration page.

Checkout and Invoice Protection

  • Filtered Gateway Arrays: Modify the gateway data supplied by WHMCS before the checkout page is rendered.
  • Selected Method Correction: Change the current selection when it is no longer eligible or displayed.
  • Gateway Type Preservation: Retain important credit-card and remote-input gateway information when building the filtered list.
  • Final Validation Layer: Return a clear error if the submitted payment method is not valid for the cart or account.
  • Invoice Dropdown Filtering: Remove unavailable methods from invoice gateway selectors.
  • Safe Invoice Fallback: Prevent an invoice from remaining assigned to an ineligible payment method.

Administrator Features

  • Central Rule Dashboard: View configured gateways, account-age requirements, assigned products, groups, and notes.
  • Active Gateway Detection: Load the payment methods currently available in WHMCS.
  • One Rule Per Gateway: Keep gateway configuration clear and prevent conflicting duplicate rules.
  • Multi-Select Product Controls: Assign several products and groups to one payment gateway.
  • Admin Descriptions: Add an internal note explaining the purpose of each gateway rule.
  • Edit and Delete Actions: Update or remove payment restrictions whenever requirements change.
  • Immediate Rule Application: Use saved database rules during the next checkout or invoice request.
  • Token-Protected Administration: Validate admin rule-management requests using WHMCS security tokens.

Common Use Cases

  • High-Risk Products: Restrict sensitive services to payment methods with stronger protection.
  • New Client Restrictions: Hide selected gateways until the customer account has established sufficient history.
  • Offline Payments: Offer bank transfer or manual methods only for suitable products.
  • Product-Specific Gateways: Connect specialized payment providers with the services they support.
  • Group-Wide Policies: Apply consistent payment options across hosting, VPS, licensing, or other product categories.
  • Cleaner Guest Checkout: Limit the initial payment list to selected default methods.

Business Benefits

  • Create a Cleaner Checkout: Remove payment methods that are not relevant to the customer’s purchase.
  • Reduce Payment Errors: Prevent clients from selecting gateways unsuitable for particular services.
  • Improve Risk Control: Restrict payment access according to products and account age.
  • Simplify Management: Apply one rule to an entire product group instead of configuring every product separately.
  • Protect Invoice Payments: Continue enforcing gateway eligibility after checkout.
  • Avoid Template Replacement: Apply filtering through WHMCS hooks and server-side gateway data.

Ideal For

  • Web hosting and reseller hosting companies
  • VPS, cloud, and dedicated server providers
  • Businesses selling higher-risk products or services
  • Agencies using several payment providers
  • SaaS and digital service platforms
  • Any WHMCS business requiring product-specific payment control

Why Choose Smart Gateway Manager For WHMCS?

Smart Gateway Manager provides a structured way to control payment availability throughout the WHMCS purchase and invoice lifecycle. Its product, group, account-age, and guest rules help ensure that customers are offered payment methods appropriate to their purchase and eligibility.

With automatic filtering, fallback selection, checkout validation, invoice protection, and a straightforward rule-management interface, the module creates a more controlled and relevant payment experience without replacing order-form templates.

What does Smart Gateway Manager for WHMCS do?

It controls which payment gateways are displayed at checkout according to the products or product groups in the customer’s cart.

Is this module compatible with the latest WHMCS version?

Yes, the module is compatible with the latest supported WHMCS version.

Is this module compatible with current PHP versions?

Yes, it supports the PHP versions compatible with the latest WHMCS release.

Can payment gateways be assigned to individual products?

Yes, you can select which payment gateways are available for each supported WHMCS product.

Can gateway rules be applied to an entire product group?

Yes, you can assign gateway visibility rules at the product-group level.

Why would I restrict payment gateways by product?

It lets you show only suitable payment options based on product type, risk level, pricing, processing cost, or business requirements.

Can different products display different payment gateways?

Yes, each supported product can use its own payment gateway rules.

Can different product groups use different payment gateways?

Yes, separate product groups can have different gateway configurations.

Does the module hide gateways that are not eligible?

Yes, payment methods that do not match the applicable product or group rules are removed from the checkout selection.

Are gateway rules applied automatically?

Yes, gateway visibility is adjusted dynamically according to the customer’s cart.

Does the customer need to select the product before the rules apply?

Yes, the module evaluates the products currently included in the cart.

What happens when a customer changes the products in the cart?

The available payment options are recalculated according to the updated cart contents.

What happens if the cart contains multiple products?

The module evaluates the applicable rules for the products or product groups in the cart and displays gateways allowed by the configured logic.

Can I decide how gateway conflicts are handled in a mixed cart?

Mixed-cart behavior depends on the rule logic provided by the installed module version and should be tested with your product combinations.

What happens if two products permit different gateways?

The displayed options depend on how the module combines product-level rules. Administrators should configure at least one compatible gateway for expected mixed carts.

What happens if no payment gateway matches the cart?

The customer may be unable to complete checkout, so every restricted product or expected cart combination should have at least one permitted gateway.

Can I assign more than one payment gateway to a product?

Yes, a product can be configured to display multiple eligible gateways.

Can I allow only one payment gateway for a product?

Yes, you can restrict a product to a single supported payment method.

Can one gateway remain available for every product?

Yes, you can include the same gateway in all relevant product and group rules.

Can I disable a gateway rule later?

Yes, administrators can update or remove gateway assignments when business requirements change.

Do gateway-rule changes apply immediately?

Yes, updated gateway visibility rules apply to subsequent checkout evaluations.

Is cache clearing required after changing a rule?

No, the module is designed to apply supported changes without requiring manual cache clearing.

Does the module activate or configure payment gateways?

No, payment gateways must first be installed and activated through the standard WHMCS payment settings.

Can it display a payment gateway that is disabled in WHMCS?

No, it only controls visibility for gateways already available in your WHMCS installation.

Does it change gateway credentials or API settings?

No, gateway credentials and provider settings remain managed through WHMCS.

Does the module process customer payments?

No, the selected WHMCS payment gateway continues to process the payment.

Does it add payment gateway surcharges?

No, it controls payment-method visibility. Gateway charges require a separate surcharge module.

Can it be used with Payment Gateway Charges For WHMCS?

Yes, Smart Gateway Manager can control which gateways appear while a gateway-charges module applies the relevant fees.

Can it help reduce customer confusion?

Yes, hiding irrelevant gateways creates a cleaner checkout with fewer unsuitable options.

Can fewer payment choices improve checkout conversions?

Yes, displaying only relevant payment methods can simplify decision-making and reduce checkout friction.

Can the module prevent customers from using a risky gateway for selected products?

Yes, you can hide that gateway for the applicable products or product groups.

Can it be used for high-risk products?

Yes, high-risk products can be limited to payment methods that match your risk-management policy.

Can it be used for low-cost products?

Yes, low-value products can be restricted to gateways with suitable processing costs.

Can it control gateways based on the customer’s country?

The supplied module functionality confirms product and product-group rules. Country-based control should only be advertised if available in your installed version.

Can it control gateways based on currency?

Currency-based rules should only be advertised when they are included in the installed module version.

Can it control gateways based on client groups?

Client-group targeting should only be advertised if supported by your installed version.

Can it control gateways based on invoice value?

Amount-based rules should only be advertised if the installed module provides minimum or maximum total conditions.

Can it automatically choose a payment gateway for the customer?

The module primarily controls which gateways are visible. Automatic selection depends on the checkout behavior and available options.

Can administrators manage rules from the WHMCS admin area?

Yes, gateway assignments are managed through the module’s administrative interface.

Is coding required to create gateway rules?

No, standard product and product-group assignments can be configured without coding.

Are template modifications required?

No, the module dynamically controls gateway visibility without requiring template edits.

Does the module modify WHMCS core files?

No, it operates as a WHMCS addon without modifying WHMCS core files.

Does it work with standard WHMCS order-form templates?

Yes, it is designed for standard WHMCS checkout workflows.

Does it work with custom order forms?

It may work with custom forms that use the standard WHMCS gateway workflow, but heavily modified checkout templates should be tested.

Does it support third-party payment gateways?

It is designed to work with WHMCS-supported gateways, including compatible third-party gateways that follow standard WHMCS behavior.

Does it support offline payment methods?

Offline gateways can be included in product rules when they are active and available in WHMCS.

Will it affect existing invoices?

It controls gateway visibility during supported checkout and payment selection. It does not rewrite invoice amounts or completed transactions.

Will it affect recurring automatic payments?

Existing recurring agreements continue according to their gateway and provider settings. The module mainly controls gateway availability during selection.

Can it help international businesses?

Yes, international providers can assign suitable gateways to products intended for different markets, although geographic rules require separate supported conditions.

Who should use this module?

It is suitable for hosting providers, SaaS companies, resellers, agencies, international businesses, and high-risk service sellers that need product-based payment control.