WHMCS MODULES

XUI ONE WHMCS Module: Full Installation and Configuration Guide (2026)

WHMCS MODULES — Mon, 20 Jul 2026 02:15:54 +0000

If you are running an IPTV reseller business on XUI ONE panels, managing subscriptions manually through your panel is not sustainable as your customer base grows. Every new order requires logging in, creating the line, setting the package, and sending credentials manually. Every renewal needs tracking. Every suspension needs manual action.

The XUI ONE Reseller Module for WHMCS eliminates all of that by connecting your WHMCS billing system directly to your XUI ONE panel via API — automating the entire service lifecycle from order placement through renewal, suspension, and termination.

This guide covers everything you need to install, configure, and get the most out of the XUI ONE WHMCS module.

What Does the XUI ONE WHMCS Module Do?

The XUI ONE Reseller Module for WHMCS is a provisioning module that bridges your WHMCS billing system with your XUI ONE reseller panel. Once configured, every billing event in WHMCS triggers a corresponding action on your panel automatically:

Customer pays → line created on XUI ONE panel instantly
Credentials delivered to customer by email automatically
Renewal invoice paid → line expiry extended automatically
Invoice overdue → line suspended automatically
Cancellation → line terminated automatically

Beyond provisioning, the module includes a full client self-service area, admin management tools, billing cycle package mapping, bouquet management, and ISP lock support.

Requirements Before Installation

Make sure you have the following in place before starting:

WHMCS 8.x or 9.x installed on a stable server with SSL
PHP 8.1, 8.2, 8.3, or 8.4 compatible with your WHMCS version
ionCube Loader installed on your server
A valid XUI ONE reseller panel account with API access enabled
Your XUI ONE panel URL, username, and password ready
WHMCS cron job configured and running

Step-by-Step Installation

Step 1 — Purchase and Download

Purchase the XUI ONE Reseller Module from whmcsmodules.org — a 7-day free trial is included so you can test the full module on your live setup before committing. After purchase, download the module package from your client area.

Step 2 — Upload Module Files

Extract the downloaded zip file. The package contains both a server module and an addon module combined. Upload the extracted files directly to your WHMCS root directory:

/whmcs/ (root directory)

Set directory permissions to 755 and file permissions to 644 after upload.

Step 3 — Activate the Addon Module

Go to WHMCS Admin → Setup → Addon Modules. Find the XUI ONE module in the list and click Activate. Assign access permissions to the admin roles that need to manage the module.

Step 4 — Add Your XUI ONE Panel

Go to WHMCS Admin → Setup → Products/Services → Servers. Click Add New Server and select XUI ONE as the module type. Enter your panel details:

Server Name — your reference label for this panel
Panel URL — without trailing slash
Username and Password
Click Save Changes

Step 5 — Test the Connection

Before configuring any products, use the built-in connection test to verify your credentials are correct and your WHMCS server can reach your XUI ONE panel. This prevents provisioning failures before they happen in production.

Step 6 — Create or Configure Your WHMCS Product

Go to Setup → Products/Services → Create New Product or edit an existing one. Under the Module Settings tab:

Select XUI ONE as the module
Choose the panel you added in Step 4
Set the service type — Stream Line (M3U) or MAG device
Configure package mapping per billing cycle
Set bouquet options if offering channel package selection
Configure ISP lock settings if needed
Set credential generation preferences

Step 7 — Configure Billing Cycle Package Mapping

Map each WHMCS billing cycle to the corresponding package on your XUI ONE panel:

Monthly billing cycle    → Monthly XUI ONE package
Quarterly billing cycle  → Quarterly XUI ONE package
Annual billing cycle     → Annual XUI ONE package

This ensures customers on different billing cycles get provisioned with the correct package automatically — no manual adjustments needed.

Step 8 — Configure Bouquet Management

If you want customers to choose their channel packages during ordering or update them after activation, enable bouquet selection in the product module settings:

Set default bouquets per product
Allow customers to select bouquets at checkout
Let active customers update their bouquet from the client area
Organize bouquets into admin-defined categories

Step 9 — Test the Full Order Flow

Before going live, run a complete end-to-end test:

Create a test client account
Place a test order for your XUI ONE product
Complete a test payment
Confirm line is created on your XUI ONE panel automatically
Confirm welcome email with credentials is received
Log into client area and verify all self-service options work
Test suspension by simulating an overdue invoice
Test reactivation by paying the overdue invoice
Test termination via a cancellation request

Only go live after all steps in this list pass cleanly.

Key Features After Setup

ISP Lock Support Create XUI ONE lines with ISP Lock enabled directly from WHMCS for better security and account control. Customers are locked to their ISP, preventing credential sharing.

Stream Line and MAG Device Support The module handles both Stream Line (M3U username/password) provisioning and MAG device provisioning via MAC address. Configure each product type separately in your product settings.

Customer Self-Service Area Once a service is active, customers can access from the WHMCS client area:

Username and password (with reveal option)
M3U playlist URL
Portal URL and Web TV link
App download links
Expiry date with countdown
Password change option
Bouquet update option (where enabled)

Admin Management Tools From the WHMCS admin area, you can manually create, suspend, unsuspend, terminate, or change packages on any XUI ONE service without logging into the panel directly.

Real-Time Status Sync The module keeps service status and expiry dates synchronized between WHMCS and your XUI ONE panel, ensuring billing records always reflect the actual panel state.

Activity Logging Every API request and panel response is logged with timestamps and HTTP status codes. When something goes wrong, the module log is the first place to check.

Common Issues and Fixes

Connection Test Failing Verify your panel URL has no trailing slash. Confirm your username and password are correct. Check whether your server’s firewall is blocking outbound connections to your panel IP address.

Lines Not Being Created on Payment Check your WHMCS cron job first — go to Utilities → Cron Job Log and confirm it is running. If it is running, check the Module Log under Utilities → Logs for specific error messages from the panel.

MAG Address Validation Errors Make sure the custom field for MAC address is created on the product and mapped correctly in module settings. The module validates MAC address format before provisioning — incorrect format will reject the provisioning request.

Expiry Dates Out of Sync Check that the synchronization cron script is running correctly. If dates are still out of sync after the cron runs, check the sync log for error messages.

Credentials Not Delivered to Customer Check your WHMCS product welcome email template and confirm it includes the correct merge fields for username, password, and service details. Also check your WHMCS mail settings to confirm outgoing email is working.

XUI ONE Module vs OTT Master Panel — Which Should You Choose?

If you are running XUI ONE panels exclusively, the dedicated XUI ONE Reseller Module at $99 covers your full automation needs with deep XUI-specific features.

If you run multiple panel types — XUI ONE alongside NXT Dash, Xtream UI, or OneStream — the OTT Master Panel for WHMCS at $249 manages all of them from one module. For two or more panel types, the OTT Master Panel is more cost-effective and significantly easier to manage than running separate modules for each panel.

Pricing and Licensing

The XUI ONE Reseller Module for WHMCS is a one-time purchase at $99 with no recurring fees and a lifetime owned license. It includes a 7-day free trial, multi-level technical support, and instant download after purchase.

Get the XUI ONE Reseller Module for WHMCS →

Related WHMCS IPTV Modules

OTT Master Panel for WHMCS — multi-panel automation for XUI ONE, NXT Dash, Xtream UI, OneStream
NXT Dash Reseller Module for WHMCS — full automation for NXT Dash panels
Stripe Checkout Module for WHMCS — add card payment processing to your IPTV billing

How to Start an IPTV Reseller Business with WHMCS: Complete Setup Guide (2026)

WHMCS MODULES — Fri, 10 Jul 2026 23:44:05 +0000

Starting an IPTV reseller business is one of the most accessible ways to build a recurring revenue stream in the digital services space. The barrier to entry is low, the demand is consistent, and the operational overhead — when set up correctly — is minimal. The key word there is correctly. Most new IPTV resellers start without a proper billing system, manage everything manually, and hit a ceiling within the first few months.

This guide covers how to start an IPTV reseller business the right way — with WHMCS as your billing backbone and proper automation from day one so your business can scale without scaling your workload.

What Is an IPTV Reseller Business?

An IPTV reseller business involves purchasing subscription credits or connections from an IPTV panel provider at wholesale rates and reselling them to end customers at a margin. You are not hosting the content — you are managing the subscriptions, billing, and customer relationships on top of an existing panel infrastructure.

The business model works on recurring revenue. Customers pay monthly, quarterly, or annually for their IPTV subscription. Your job is to manage that billing cycle, provision accounts on your panel, handle renewals, and provide support.

Without automation, every one of those steps requires manual work. With WHMCS and the right modules, all of it runs automatically.

What You Need Before Starting

Before setting up anything, make sure you have these in place:

IPTV Panel Reseller Account You need a reseller account on at least one supported IPTV panel. The most widely used panel types are XUI ONE, NXT Dash, Xtream UI, and OneStream. Your reseller account gives you credits that you use to create customer subscriptions.

A Domain Name Your WHMCS client area and your business need a domain. Choose something that reflects your brand — avoid using generic terms that could be confused with panel providers or competitors.

Web Hosting or VPS WHMCS requires a hosting environment with PHP 8.1 or higher, MySQL, and ionCube Loader installed. A VPS gives you more control and is recommended over shared hosting for WHMCS.

SSL Certificate Your WHMCS installation must run on HTTPS. Most hosting providers include a free SSL certificate — make sure it is active before going live.

A Business Email Set up a professional email address on your domain for customer communication and payment gateway verification.

Step 1 — Choose Your IPTV Panel Type

Your panel choice determines which WHMCS provisioning module you need, so it is worth thinking through before setting up anything else.

XUI ONE One of the most popular panel types for IPTV resellers. Clean interface, good API support, and widely used across the industry. If you are starting fresh and have not yet committed to a panel, XUI ONE is a solid first choice.

NXT Dash Growing in popularity, particularly among resellers who prefer its dashboard design and bouquet management system. Good API coverage and reliable for automated provisioning.

Xtream UI One of the original IPTV panel systems. Widely supported and has a large existing user base. Some operators prefer it for its familiarity and broad compatibility with IPTV apps.

OneStream A newer panel type gaining traction for its clean interface and streaming reliability. Good choice if your panel provider offers it.

Running Multiple Panels If you plan to run more than one panel type — or want the flexibility to add more later — the OTT Master Panel module handles all of the above from one WHMCS installation, which simplifies your setup considerably as you grow.

Step 2 — Install and Configure WHMCS

WHMCS is the billing and client management platform that runs your entire subscription operation. Download it from whmcs.com and install it on your server following their documentation.

Key configuration steps after installation:

General Settings Set your company name, logo, support email, and default currency. These appear on all customer invoices and emails.

Automation Settings This is where you define how your billing cycle behaves:

How many days before due date invoices are generated
How many days overdue before service suspends
How many days suspended before service terminates
Automated reminder email schedule

Cron Job All WHMCS automation runs through a cron job. This must be configured correctly or nothing will automate. Set it to run every 5 minutes:

*/5 * * * * /usr/bin/php -q /path/to/whmcs/cron/cron.php

Email Templates Configure your customer email templates:

Welcome email with credentials after new order
Invoice generated notification
Payment received confirmation
Overdue invoice reminders
Service suspended notification
Service reactivation confirmation

Step 3 — Connect Your IPTV Panel with a WHMCS Module

This step is what separates a manual IPTV operation from an automated one. A WHMCS provisioning module connects your billing system to your panel via API so that every billing event triggers a corresponding action on your panel automatically.

For single panel setups:

If you are running one panel type, install the dedicated module for that panel:

XUI ONE Reseller Module for WHMCS — full automation for XUI ONE panels
NXT Dash Reseller Module for WHMCS — full automation for NXT Dash panels
Xtream UI Reseller Module for WHMCS — full automation for Xtream UI panels

For multi-panel setups:

If you plan to run more than one panel type or want the flexibility to expand later, the OTT Master Panel for WHMCS connects all supported panel types from a single module. One installation, one interface, one set of logs — regardless of how many panels you run.

What the module automates:

Account creation when customer pays
Credential delivery by email
Service renewal when invoice is paid
Service suspension when invoice goes overdue
Service termination on cancellation
Customer self-service portal for credentials and M3U access

All of the above happens without you touching anything once the module is configured.

Step 4 — Set Up Payment Gateways

Your customers need a way to pay. WHMCS supports multiple payment gateways simultaneously — setting up more than one from the start protects you from single point of failure and gives customers payment options.

Stripe Checkout The most reliable option for recurring IPTV subscription billing. Handles failed payment retries automatically, supports most countries, and has clean dispute resolution. The Stripe Checkout Module for WHMCS integrates directly with your WHMCS billing cycle.

Coinbase Commerce For crypto payments. No chargebacks by design, works for customers in any country, and removes payment processor restrictions entirely. Ideal as a secondary gateway alongside Stripe.

Square Good option for US, UK, and Canada based customers. More stable than PayPal for digital service businesses and has a clean WHMCS integration.

Amazon Pay Customers pay with their existing Amazon account — significantly improves checkout conversion for new businesses where customers don’t yet trust your brand.

Avoid relying on PayPal as your primary gateway for IPTV businesses. Accounts in the streaming space get restricted frequently without warning, and the dispute process heavily favours buyers.

Step 5 — Create Your WHMCS Products

With your panel connected and payment gateways active, create your product lineup in WHMCS:

Product Structure Create a product group for your IPTV services. Add individual products per plan tier — for example Basic (1 connection), Standard (2 connections), Premium (4 connections).

Billing Cycles Set pricing per billing cycle — monthly, quarterly, semi-annual, and annual. Offer a discount on longer cycles to encourage annual subscriptions, which improves your cash flow and reduces churn.

Module Settings For each product, assign your provisioning module, select your panel, set the service type (Streamline or MAG), and map each billing cycle to the corresponding package on your panel.

Welcome Email Configure the product welcome email to include the customer’s credentials, M3U URL, portal address, and a link to your client area. This email fires automatically after payment — first impressions matter.

Step 6 — Test Before Going Live

Before launching to customers, run a full end-to-end test:

Create a test client account
Place a test order
Complete a test payment
Confirm account created on your panel automatically
Confirm welcome email received with correct credentials
Log into client area and verify all self-service options work correctly
Test suspension by simulating an overdue invoice
Test reactivation by paying the overdue invoice
Test termination via cancellation request

Only go live after every step in this list passes cleanly. Discovering a broken automation flow after real customers are on your system is significantly harder to fix.

Step 7 — Launch and Get Your First Customers

With your system live and tested, focus on getting your first customers:

Start With Your Network Your first 5-10 customers almost always come from people you already know. Offer a trial period or discounted first month to get initial subscribers on your system and test it under real conditions.

Build a Presence in IPTV Communities Forums and communities where IPTV users discuss services are where your target customers spend time. Provide helpful answers and make your service known — avoid hard selling, focus on being genuinely useful.

Offer a Trial A 24-48 hour trial reduces the barrier for new customers significantly. Most IPTV resellers who offer trials convert a higher percentage of prospects than those who don’t.

Automate Your Renewal Communication WHMCS handles renewal invoice generation and reminder emails automatically. Make sure your email templates are professional and give customers enough notice before their service expires to avoid unnecessary churn.

What Full Automation Looks Like

Once your WHMCS and panel module setup is running correctly, your day-to-day involvement drops to near zero for routine subscription management:

New orders provision and deliver credentials automatically
Invoices generate and reminders send on schedule
Overdue accounts suspend without manual action
Paid renewals reactivate instantly
Customers manage their own credentials and details

Your time shifts from operational tasks to growing the business — finding new customers, improving your service, and expanding your panel capacity.

Summary: What You Need to Launch

Component	Purpose
IPTV panel reseller account	Your subscription inventory
Domain + hosting + SSL	Your WHMCS environment
WHMCS installation	Billing and client management
IPTV provisioning module	Panel automation
Payment gateway module	Customer payments
Configured products	Your service lineup
Tested automation	Reliable operations

All WHMCS modules mentioned in this guide — panel provisioning modules and payment gateway integrations — are available at whmcsmodules.org with 7-day free trials and one-time lifetime licensing.

Ready to set up your IPTV reseller billing system?

Get the OTT Master Panel for WHMCS →

NXT Dash WHMCS Module: Full Installation and Configuration Guide (2026)

WHMCS MODULES — Sun, 05 Jul 2026 13:10:16 +0000

If you are running an IPTV reseller business on NXT Dash panels, managing subscriptions and service provisioning manually through your panel is not a sustainable approach as your customer base grows. The NXT Dash Reseller Module for WHMCS connects your NXT panel directly to your WHMCS billing system, automating the entire service lifecycle from the moment a customer places an order to renewal, suspension, and termination.

This guide covers everything you need to install, configure, and get the most out of the NXT Dash WHMCS module.

What Does the NXT Dash WHMCS Module Do?

The NXT Dash Reseller Module for WHMCS is a provisioning module that automates the connection between your WHMCS billing system and your NXT Dash reseller panels. Once configured, it handles:

Automatic account creation when a customer pays
Streamline and MAG device provisioning
Billing cycle package mapping (monthly, quarterly, annual, and more)
Bouquet management with customer self-selection
Service renewals, suspensions, and terminations triggered by WHMCS
Customer self-service area for credentials, M3U playlists, and device links
Multi-panel management from a single WHMCS installation
Synchronization of credentials and expiry dates between the panel and WHMCS

Requirements Before Installation

Before you begin, make sure the following are in place:

WHMCS 8.x or 9.x installed on a stable server with a valid SSL certificate
PHP version compatible with your WHMCS release
A valid and authorized NXT Dash reseller panel account with API access enabled
Your NXT Dash panel URL, credentials, and sufficient reseller credits
WHMCS cron job configured and running correctly

Step-by-Step Installation

Step 1 — Purchase and Download

Purchase the NXT Dash Reseller Module from whmcsmodules.org — it includes a 7-day free trial so you can test on your live setup before committing. After purchase, download the module zip file from your client area.

Step 2 — Upload Module Files

Extract the downloaded zip file. The package contains both a server module and an addon module combined. Upload the extracted files directly to your WHMCS root directory — the installer will place each component (addon and server module) into its correct location automatically.

/whmcs/ (root directory)

Set directory permissions to 755 and file permissions to 644 after upload.

Step 3 — Add Your NXT Dash Panel in WHMCS

Go to WHMCS Admin → Setup → Products/Services → Servers. Click Add New Server and select NXT Dash as the module type. Enter your panel details:

Server Name (your reference label)
Panel URL (without trailing slash)
Username and Password or API token
Click Save Changes

Step 4 — Test the Panel Connection

Before configuring any products, use the built-in connection test to verify your credentials are correct and your WHMCS server can communicate with your NXT Dash panel. This prevents provisioning failures before they happen.

Step 5 — Create or Configure Your WHMCS Product

Go to Setup → Products/Services → Create a New Product (or edit an existing one). Under the Module Settings tab:

Select NXT Dash as the module
Choose the panel you added in Step 3
Set the service type — Streamline or MAG
Configure package mapping per billing cycle (monthly, quarterly, annually, etc.)
Set bouquet options if offering channel package selection
Configure credential generation settings

Step 6 — Set Up Billing Cycle Package Mapping

One of the most powerful features of this module is the ability to map different NXT Dash packages to different WHMCS billing cycles. For example:

Monthly → NXT Monthly Package
Quarterly → NXT Quarterly Package
Annually → NXT Annual Package

This means a customer buying a monthly plan gets provisioned with the monthly NXT package automatically, while an annual customer gets the annual package — all without manual intervention.

Step 7 — Configure Bouquet Management

If you want customers to choose their channel packages during ordering or after activation, enable bouquet selection in the product module settings. You can:

Set default bouquets per product
Allow customers to select bouquets at checkout
Let active customers update their bouquet selection from the client area
Organize bouquets into admin-defined categories

Step 8 — Verify Cron Job

Your WHMCS cron job must be running for automated renewals, suspensions, and terminations to trigger correctly. Go to WHMCS Admin → Utilities → Cron Job Log to confirm it is running on schedule. Without this, automation will not work even if everything else is configured correctly.

Step 9 — Test the Full Order Flow

Create a test client, place a test order, and complete a test payment. Confirm:

Account is created on your NXT Dash panel
Credentials are delivered to the customer by email
Service shows as active in both WHMCS and the panel
Client area shows the correct subscription details, M3U link, and expiry date

Key Features After Setup

Customer Self-Service Area

Once a service is active, customers can log into the WHMCS client area and access their full subscription details including username, password, MAG address, expiry date, M3U playlist, portal URL, and device app download links. They can also change their Streamline password and update bouquet selections if enabled.

Synchronization Tools

If credentials or expiry dates get out of sync between WHMCS and your NXT panel, the module includes synchronization tools to realign them. This is useful after manual panel changes or after resolving provisioning issues.

Admin Dashboard

The module includes an overview dashboard showing total services broken down by status — Active, Pending, Suspended, Terminated, Free, and One-Time — across all connected panels. This gives you a clear picture of your IPTV business health without logging into each panel separately.

Activity Logs

Every panel request and response is logged with the endpoint, HTTP status, execution time, and timestamp. When something goes wrong, these logs are the first place to check to identify whether the issue is authentication, insufficient credits, duplicate values, or a panel-side error.

Common Issues and Fixes

Provisioning Not Triggering
Check your cron job first — this is the most common cause. Go to Utilities → Cron Job Log and confirm the cron is running. If it is, check the Module Log under Utilities → Logs for specific error messages from the panel.

Connection Test Failing
Verify your panel URL does not have a trailing slash. Confirm your username and password are correct. Check whether your server’s firewall is blocking outbound connections to your panel IP.

MAG Address Validation Errors
The module validates MAC address format before provisioning. Make sure the custom field for MAG address is created on the product and that customers are entering addresses in the correct format.

Credentials Not Delivered to Customer
Check your WHMCS product welcome email template and confirm it includes the correct merge fields for username, password, and service details.

Renewal Not Extending Expiry on Panel
Confirm the billing cycle package mapping is correctly set for the customer’s billing period. Check the Module Log for any rejection messages from the panel, which may indicate insufficient credits.

One-Time Payment, Lifetime License

The NXT Dash Reseller Module for WHMCS is a one-time purchase at $99 with no recurring fees and a lifetime owned license. It includes a 7-day free trial, multi-level technical support, and instant download after purchase.

Get the NXT Dash Reseller Module for WHMCS →

Related WHMCS IPTV Modules

If you are running multiple panel types or looking to expand your IPTV automation setup, these modules work alongside the NXT Dash module:

OTT Master Panel for WHMCS — multi-panel automation covering several IPTV panel types from one module
XUI ONE Reseller Module for WHMCS — full automation for XUI ONE panels
Stripe Checkout Module for WHMCS — add card payment processing to your IPTV billing setup

OTT Master Panel for WHMCS: Complete Setup Guide for IPTV Resellers (2026)

WHMCS MODULES — Mon, 29 Jun 2026 13:35:31 +0000

If you are running an IPTV reseller business across multiple OTT panels, managing users, MAG devices, resellers, credits, and renewals manually is not sustainable. The OTT Master Panel for WHMCS solves this by connecting your WHMCS billing system directly to your OTT panels and automating the entire service lifecycle.

This guide covers what the OTT Master Panel does, who it is for, how to install it, and how to get the most out of it after setup.

What Is the OTT Master Panel for WHMCS?

The OTT Master Panel for WHMCS is a provisioning module that bridges your WHMCS billing system with multiple supported OTT panels. Once configured, it handles the full service lifecycle automatically — from the moment a customer pays, through renewals, suspensions, and terminations — without any manual work from your team.

It supports Streamline and MAG device provisioning, bouquet management, reseller credit systems, and multi-panel connections from a single WHMCS installation.

Who Is It For?

The OTT Master Panel module is built for:

IPTV resellers running one or more OTT panels who want to stop provisioning accounts manually
OTT operators who need a professional billing front-end for their customers
Hosting businesses that have added IPTV or streaming services to their product lineup
Anyone currently using spreadsheets or Telegram to manage subscriptions and renewals

If you are activating more than 10–15 IPTV accounts per month manually, automation will pay for the module in the first week.

Key Features

Multi-Panel Support
Connect multiple OTT panels to a single WHMCS installation. Assign each WHMCS product to a specific panel or distribute load across panels automatically.

Streamline and MAG Device Provisioning
Create and manage both Streamline accounts and MAG device registrations from WHMCS. Customers receive their credentials automatically after payment.

Reseller and Credit Management
Manage reseller accounts and credits directly from the WHMCS admin area. Allocate, adjust, and monitor credits per reseller without logging into each panel separately.

Bouquet Management
Assign, update, and manage bouquets (channel packages) per customer from WHMCS. Changes sync to the panel automatically.

Automated Renewals and Suspensions
When an invoice is paid, the service renews on the panel. When an invoice goes overdue, the service suspends. When cancelled, it terminates. All without manual intervention.

Client Self-Service
Customers can view their subscription details, change passwords, download M3U playlists, and manage connections directly from the WHMCS client area.

7-Day Free Trial
Try the full module before committing. No credit card required during the trial period.

Requirements Before You Install

Before installing the OTT Master Panel for WHMCS, make sure you have:

WHMCS 8.x or 9.x installed on a stable server
PHP version compatible with your WHMCS release
Valid SSL certificate on your WHMCS domain
API access enabled on your OTT panel
API URL, username, and password ready

Step-by-Step Installation

Step 1 — Download the Module
After purchase, download the module from your WHMCS Modules client area. You will receive a zip file containing the module files.

Step 2 — Upload to Your Server
Extract the zip and upload the module folder to your WHMCS /modules/servers/ directory. Set directory permissions to 755 and file permissions to 644.

Step 3 — Activate in WHMCS
Go to WHMCS Admin → Setup → Products/Services → Servers. Add a new server, select OTT Master Panel as the module type, and enter your OTT panel API URL and credentials.

Step 4 — Test the Connection
Use the built-in connection test before going live. This confirms your API credentials are correct and your panel is reachable from your WHMCS server.

Step 5 — Configure Your Products
Go to Setup → Products/Services and edit or create your IPTV product. Under the Module Settings tab, select OTT Master Panel and configure the package — connection limits, bouquets, trial settings, and billing cycle.

Step 6 — Set Up Automation Rules
Make sure your WHMCS cron job is running correctly. The cron job handles automatic renewals, suspensions, and terminations. Without it, automation will not trigger.

Step 7 — Test the Full Order Flow
Create a test client, place a test order, and complete a test payment. Confirm the account is created on your OTT panel, credentials are delivered by email, and the service shows as active in both WHMCS and your panel.

Common Issues and How to Fix Them

Connection Failed
Check your API URL format — most panels require the URL without a trailing slash. Verify your API username and password are correct. Check if your server firewall is blocking outbound connections to your panel IP.

Account Creation Not Triggering
Make sure the module is correctly assigned to the product under Module Settings. Confirm your cron job is running — go to WHMCS Admin → Utilities → Cron Job Log to verify.

Renewals Not Processing
This is almost always a cron job issue. If the cron is running but renewals are still failing, check the module log under Utilities → Logs → Module Log for specific error messages.

MAG Devices Not Provisioning
MAG device provisioning requires MAC address validation. Make sure the custom field for MAC address is created on the product and mapped correctly in the module settings.

Why Choose OTT Master Panel Over Individual Panel Modules?

If you only run one panel type, a single panel module like the XUI ONE or NXT Dash module may be enough. But if you run multiple panel types or plan to scale across panels, the OTT Master Panel gives you:

A single module to manage all panel connections
Consistent automation logic across every panel
One place to manage resellers and credits regardless of which panel they are on
Easier upgrades as your panel stack grows

It is the better choice for operators who are already running at scale or planning to.

Start With a Free Trial

The OTT Master Panel for WHMCS includes a 7-day free trial so you can test the full module on your live setup before purchasing. There are no recurring fees — it is a one-time payment with a lifetime license.

Get the OTT Master Panel for WHMCS →

WHMCS Security Best Practices to Protect Your Billing System

WHMCS MODULES — Thu, 25 Jun 2026 22:16:57 +0000

WHMCS is the center of your billing, customer management, invoices, orders, support tickets, and service automation. Because it handles sensitive business and client data, keeping your WHMCS installation secure is extremely important. Whether you run a hosting company, IPTV business, SaaS platform, or digital service store, weak WHMCS security can lead to fake signups, spam orders, fraudulent accounts, payment abuse, account misuse, and unnecessary support work. In this guide, we’ll cover practical WHMCS security best practices to help protect your billing system and create a safer experience for your business and customers.

Why WHMCS Security Matters

Your WHMCS system contains important information such as client accounts, invoices, services, domains, support tickets, payment history, and automation workflows. If attackers abuse your system, it can affect both your operations and your reputation. Common WHMCS security risks include:

Fake client registrations
Spam orders and bot signups
Fraudulent purchases
Disposable email abuse
Multiple account abuse
Payment disputes and chargebacks
Unverified customer accounts
Unauthorized access attempts
Weak admin access protection

1. Keep WHMCS Updated

One of the most important security steps is keeping WHMCS updated. Updates often include security fixes, compatibility improvements, and stability enhancements. Before updating, always:

Create a full backup of files and database
Check module compatibility
Confirm PHP version support
Test updates on staging when possible
Review custom hooks and templates after updating

Outdated WHMCS installations are more likely to face compatibility issues, security problems, and module failures.

2. Use Strong Admin Access Protection

Your WHMCS admin area should be protected carefully. Admin access controls billing, clients, products, modules, automation, and system settings. Recommended admin security steps include:

Use strong admin passwords
Enable two-factor authentication for staff
Limit admin access to trusted users only
Use unique staff accounts instead of shared logins
Restrict admin permissions based on staff roles
Rename or protect your admin directory where appropriate

3. Block Fake Signups and Spam Registrations

Fake signups can create a messy client database, increase support load, and lead to abusive orders. Spam users may use temporary emails, suspicious names, repeated IP addresses, or automated scripts. To reduce spam registrations, use rules that block suspicious email domains, spam keywords, repeated IP activity, and fake form submissions. For stronger protection, you can explore our WHMCS addon modules, including tools designed for spam control, email verification, fraud prevention, and client account security.

4. Require Email Verification

Email verification helps confirm that customers are using real and reachable email addresses. This reduces fake accounts, bot signups, and orders created with invalid contact details. Email verification can help with:

Reducing fake registrations
Improving client database quality
Preventing orders from invalid emails
Improving billing communication
Reducing support problems caused by unreachable clients

This is especially useful for hosting providers, IPTV resellers, SaaS platforms, and digital product businesses.

5. Add Fraud Protection for Orders

Fraudulent orders can cause chargebacks, resource abuse, spam activity, and service misuse. A good fraud protection workflow should check risk signals before services are activated. Useful fraud checks may include:

Device fingerprinting
Disposable email detection
VPN or proxy detection
IP and location mismatch checks
Repeated account detection
Risk scoring and order review

Fraud protection is important for businesses that sell hosting, VPS, IPTV, OTT services, software, subscriptions, or digital services.

6. Control Public Registration Access

Some businesses do not want fully open public registration. If you run a private service, beta launch, invite-only platform, or high-risk product, open registration may not be ideal. Invite-only registration can help you control who can access your WHMCS system. This is useful for:

Private hosting providers
Exclusive membership platforms
IPTV and SaaS businesses
Beta launches
Fraud-sensitive services

By allowing only invited users to register, you can reduce random signups and keep customer onboarding more controlled.

7. Use Clear Terms Agreement During Checkout

Customers should agree to your Terms and Conditions, Privacy Policy, Refund Policy, or Acceptable Use Policy before placing orders. This helps set clear expectations and supports your business policies. Terms agreement is useful for:

Refund policy confirmation
Acceptable use agreement
Privacy policy acknowledgment
Service usage terms
Legal and compliance clarity

This is especially important for digital services, hosting, IPTV, SaaS, and subscription businesses.

8. Protect Payment and Billing Workflows

Payment security is another important part of WHMCS protection. Customers should use secure payment methods, and invoices should update automatically after successful payment. Good payment security practices include:

Use trusted payment gateways
Configure webhook or callback URLs correctly
Monitor failed or suspicious payments
Use gateway logs for troubleshooting
Review chargebacks and payment disputes
Limit manual payment approval where possible

You can browse secure billing integrations in our WHMCS payment gateways category.

9. Secure File Permissions and Configuration Files

Correct file permissions help reduce the risk of unauthorized file changes or exposure of sensitive configuration files. Common recommendations include:

Use secure permissions for files and folders
Protect configuration files
Remove backup files from public directories
Do not leave old installation files online
Keep unused modules and themes removed
Avoid unsafe permissions such as 777

Also make sure old backup files such as .bak, .save, or old configuration copies are not accessible from the web.

10. Monitor Logs and Suspicious Activity

Logs help you understand what is happening inside your WHMCS system. If something goes wrong, logs can help identify failed logins, module errors, payment issues, suspicious orders, and automation problems. Review these regularly:

WHMCS activity logs
Gateway logs
Module logs
Admin login activity
Server access logs
Security and firewall events

Regular monitoring helps catch problems before they become serious.

11. Keep Modules Updated and Trusted

WHMCS modules extend your system, but poorly maintained modules can create compatibility and security risks. Only use modules from trusted providers and keep them updated. Before installing a module, check:

WHMCS version compatibility
PHP version compatibility
ionCube Loader requirements
License status
Support availability
Update history

If a module is outdated or unused, remove it from your installation.

12. Use Automation Carefully

Automation can save time, but security rules should be configured carefully. For example, automatic service creation should not activate clearly fraudulent orders, and automatic renewals should depend on successful invoice payment. For IPTV and OTT businesses, WHMCS automation can be very powerful when combined with proper fraud checks, verified customer data, and reliable payment confirmation. You can explore automation products in our WHMCS OTT modules category.

Quick WHMCS Security Checklist

Keep WHMCS updated
Use strong admin passwords and two-factor authentication
Limit staff permissions
Block spam signups and fake registrations
Require email verification
Use fraud protection for risky orders
Use invite-only registration when needed
Require terms agreement during checkout
Use secure payment gateways
Review file permissions and remove backup files
Monitor logs regularly
Keep modules updated

Final Thoughts

WHMCS security is not just one setting. It is a combination of updates, access control, fraud protection, email verification, spam prevention, secure payments, proper file permissions, and regular monitoring. By following these WHMCS security best practices, you can reduce fake signups, prevent abusive orders, protect billing workflows, and create a safer experience for your customers. If you need help improving your WHMCS security, setting up protection modules, or building a custom security workflow, visit our WHMCS services page for professional support.

WHMCS Module Not Working After Installation? Common Fixes

WHMCS MODULES — Thu, 25 Jun 2026 22:08:13 +0000

If a WHMCS module is not working after installation, it can usually be traced to a setup issue such as wrong upload path, missing files, incorrect permissions, PHP version mismatch, ionCube Loader problem, license validation issue, template conflict, or configuration mistake. This can happen with WHMCS addon modules, payment gateways, server/provisioning modules, hooks, notification tools, IPTV/OTT modules, and custom integrations. In this guide, we’ll cover the most common reasons a WHMCS module does not work after installation and how to fix them step by step.

Common Signs a WHMCS Module Is Not Working

A module problem may appear in different ways depending on the module type and your WHMCS setup. Common signs include:

The module does not appear in WHMCS admin
The module page shows a blank screen
The payment gateway does not show at checkout
The addon module cannot be activated
The server module does not create services
The hook does not change anything on the client area
License invalid or license verification error appears
Module actions fail without clear output
Client area templates look broken
Errors appear after updating WHMCS or PHP

1. Check the Correct Upload Path

One of the most common installation mistakes is uploading the module files to the wrong folder. WHMCS modules must be placed in the correct directory based on module type. Common WHMCS module paths include:

/modules/addons/ for addon modules
/modules/gateways/ for payment gateways
/modules/servers/ for server or provisioning modules
/includes/hooks/ for standalone hook files
/templates/your-template/ for template files, if included

If the folder structure is wrong, WHMCS may not detect the module at all.

2. Confirm All Files Were Uploaded

Sometimes a module does not work because not all files were uploaded. This can happen if the upload was interrupted, files were skipped by FTP, or the archive was not extracted correctly. Check that:

The full module folder exists
Required PHP files are present
Template files were uploaded if included
Language files were uploaded if included
Vendor or library folders were uploaded if included
File names match the documentation exactly

For best results, upload the original module folder again and overwrite missing files carefully.

3. Check Module Activation

Addon modules usually need to be activated from the WHMCS admin area. Payment gateways also need to be enabled and configured before they appear for customers. Check the correct WHMCS admin area:

Addon modules: activate from the addon modules section
Payment gateways: activate and configure from payment gateway settings
Server modules: assign the module to the product in product configuration
Hooks: confirm the PHP hook file is inside /includes/hooks/

A module can be uploaded correctly but still not work if it has not been activated or assigned properly.

4. Check PHP Version Compatibility

WHMCS modules depend on your server PHP version. If the module was built for a different PHP version, it may fail, show errors, or not load correctly. Check:

Your current WHMCS version
Your server PHP version
The module’s supported PHP versions
Whether the module supports the latest WHMCS version

If the module stopped working after a PHP upgrade, compatibility should be one of the first things to review.

5. Check ionCube Loader

Many commercial WHMCS modules require ionCube Loader. If ionCube is missing, outdated, or not enabled for the correct PHP version, encoded modules may not run. Check that:

ionCube Loader is installed
ionCube Loader supports your PHP version
ionCube is enabled for web PHP and PHP CLI if needed
The module files are compatible with your ionCube version

If you see encoded file errors or blank screens, ionCube should be checked immediately.

6. Review File and Folder Permissions

Incorrect permissions can prevent WHMCS from reading module files, writing logs, or loading templates correctly. Common safe permissions are:

Folders: 755
Files: 644
Configuration files: more restricted when needed

Avoid using 777 permissions unless a trusted server admin confirms it is absolutely necessary. In most cases, it is not required and creates security risk.

7. Check License Validation

If the module is licensed, it may not work until the license is validated. A license issue can happen if the domain, IP address, installation path, or license key does not match the provider’s records. Common license-related issues include:

Incorrect license key
License assigned to another domain
Server IP changed after migration
WHMCS installation path changed
License needs to be reissued
Server firewall blocking license verification

If you see a license error, read our guide on how to fix license invalid error in WHMCS.

8. Enable Error Display Temporarily

If the module causes a blank page or silent failure, enable error reporting temporarily to find the exact error. WHMCS may also show errors in logs depending on your configuration. Useful places to check include:

WHMCS activity log
Module logs
Gateway logs
PHP error logs
Server web server logs
Browser console for front-end issues

After debugging, turn off public error display on live websites to avoid exposing sensitive information.

9. Check Product Configuration for Server Modules

Server and provisioning modules usually need to be assigned to a WHMCS product. If the product is not configured correctly, the module may not run during order activation or service management. Check:

The correct module is selected in product settings
Required product fields are filled
Server group is assigned if needed
Package IDs or plan IDs are correct
Welcome email and automation settings are configured
Create/suspend/terminate actions are enabled where required

This is especially important for IPTV, OTT, hosting, and automation modules.

10. Check Payment Gateway Settings

If a WHMCS payment gateway does not appear at checkout, it may not be configured correctly or may be restricted by product, currency, country, or invoice status. Check:

The gateway is active
API keys or credentials are correct
Webhook or callback URL is configured
Supported currency matches the invoice currency
The gateway is not restricted by product or group rules
Test/sandbox mode is configured correctly

You can browse our WHMCS payment gateways for supported payment integrations.

11. Check Hooks and Template Conflicts

Some modules use hooks or template files to display client area content. If a hook does not run or the template does not match your WHMCS theme, the feature may not appear correctly. Check for:

Hook file uploaded to the correct folder
Hook priority conflicts
Template overrides missing or outdated
Theme compatibility issues
JavaScript or CSS conflicts
Cache preventing changes from appearing

If the issue appears only in the client area, template or theme compatibility may be involved.

12. Clear WHMCS and Browser Cache

After installing or updating a module, cached templates or browser files may cause old output to appear. Try clearing:

WHMCS template cache
Browser cache
Server cache
Cloudflare cache, if enabled
Any optimization plugin cache

Then reload the WHMCS admin area and client area again.

13. Check Module Documentation

Every module may have its own setup steps. Some modules require cron jobs, API credentials, webhook URLs, product configuration, custom fields, or callback permissions. Before assuming the module is broken, review the installation guide and confirm all setup steps were completed. Common missing setup steps include:

API credentials not entered
Webhook URL not configured
Custom fields not created
Product module settings not saved
Cron command not added
License not activated

14. Use Updated Module Versions

If you are using an old module version with a newer WHMCS or PHP version, compatibility problems can happen. Always use a module version that supports your current WHMCS environment. For modern WHMCS setups, modules should be maintained, compatible with the latest WHMCS version, and tested with supported PHP versions. You can explore updated modules in our WHMCS products section.

Quick Checklist to Fix WHMCS Module Not Working

Check the correct upload path
Confirm all files were uploaded
Activate the module in WHMCS admin
Check WHMCS and PHP compatibility
Verify ionCube Loader is enabled
Review file and folder permissions
Check license validation
Review PHP and WHMCS logs
Confirm product or gateway configuration
Check hooks and template compatibility
Clear WHMCS and browser cache
Follow the module documentation
Update to the latest module version

Final Thoughts

When a WHMCS module is not working after installation, the issue is often caused by setup, compatibility, permissions, licensing, or configuration. Start with the basics: upload path, activation, PHP version, ionCube Loader, permissions, and logs. If the module is a payment gateway, check credentials and webhook settings. If it is a server or IPTV module, check product configuration and automation settings. If it is an addon or client area module, check hooks, templates, and cache. If you need help with WHMCS module installation, troubleshooting, or custom development, visit our WHMCS services page for professional support.

WHMCS Cron Job Not Working? How to Fix Automation Issues

WHMCS MODULES — Thu, 25 Jun 2026 22:00:14 +0000

If your WHMCS cron job is not working, important automation tasks may stop running. This can affect invoices, payment reminders, overdue notices, service suspensions, domain renewals, support notifications, and other scheduled actions. For hosting companies, IPTV resellers, SaaS platforms, and digital service providers, WHMCS cron automation is very important. If the cron is misconfigured or failing silently, your business may experience missed invoices, delayed renewals, and more manual admin work. In this guide, we’ll explain how to troubleshoot and fix WHMCS cron job issues step by step.

What Does the WHMCS Cron Job Do?

The WHMCS cron job is responsible for running scheduled automation tasks in the background. It allows WHMCS to perform routine actions without requiring an admin to trigger them manually. Common WHMCS cron tasks include:

Generating invoices
Sending invoice reminders
Sending overdue notices
Processing service suspensions
Processing service terminations
Sending domain renewal reminders
Running module automation tasks
Updating system activity reports
Sending automation summary emails

If the cron job stops working, these tasks may not run on time.

Common Signs Your WHMCS Cron Is Not Working

WHMCS cron problems are not always obvious immediately. In many cases, you notice the issue only after invoices or reminders are missing. Common signs include:

Invoices are not generating automatically
Overdue reminders are not being sent
Services are not suspending after non-payment
Automation summary emails are missing
WHMCS admin shows cron warning messages
Domain reminders are not being sent
Module automation tasks are not running
Email notifications are delayed or missing

1. Check the WHMCS Cron Command

The first step is to confirm that the cron command is correct. WHMCS usually provides the recommended cron command inside the admin area. In WHMCS, check the automation or system health area for the correct command. It usually points to a cron PHP file inside your WHMCS installation. A typical cron command may look similar to:

*/5 * * * * /usr/bin/php -q /home/username/public_html/billing/crons/cron.php

Your command may be different depending on your server path, WHMCS directory, PHP path, and hosting control panel.

2. Use the Correct PHP Path

One common reason WHMCS cron jobs fail is an incorrect PHP path. The cron may be trying to use a PHP binary that does not exist or uses the wrong PHP version. Common PHP paths include:

/usr/bin/php
/usr/local/bin/php
/opt/cpanel/ea-php82/root/usr/bin/php
/opt/plesk/php/8.2/bin/php

If you are unsure, ask your hosting provider or server admin for the correct PHP CLI path.

3. Confirm the Cron File Path

The cron command must point to the correct WHMCS cron file. If WHMCS was moved to another folder, migrated to a new server, or restored from backup, the file path may have changed. Check that the path points to the correct file location, such as:

/home/username/public_html/billing/crons/cron.php

If the file path is wrong, the cron will not run even if the schedule itself is correct.

4. Check Cron Schedule Frequency

WHMCS recommends running the cron frequently so scheduled tasks can run reliably. Many setups use every 5 minutes. Example:

*/5 * * * * /usr/bin/php -q /path/to/whmcs/crons/cron.php

If the cron runs too rarely, tasks may be delayed. If it does not run at all, automation will fail completely.

5. Check File Permissions

Incorrect file permissions can stop the cron from running. The server user running the cron must be able to access the WHMCS files and execute PHP. Check that:

The cron file exists
The file is readable by the cron user
Parent folders are accessible
WHMCS files have correct ownership
Server security rules are not blocking execution

Do not use unsafe permissions like 777 unless a trusted server admin specifically confirms it is required, which is rarely the right solution.

6. Run the Cron Manually for Testing

To identify errors, you can run the cron command manually from SSH. This helps show whether the command works or returns an error. Example:

/usr/bin/php -q /path/to/whmcs/crons/cron.php

If the command fails, the terminal output may show useful details such as missing files, wrong PHP version, permission issues, or PHP extension problems.

7. Check WHMCS Automation Status

WHMCS usually shows automation status inside the admin area. Check whether the last cron run time is recent. If WHMCS says the cron has not run recently, the server cron may be missing, disabled, or pointing to the wrong command. Also check whether daily automation tasks are completing successfully or stopping halfway through.

8. Review Cron Output and Server Logs

Server logs can help identify why a cron job is failing. Depending on your hosting environment, cron errors may be sent by email, stored in system logs, or visible inside the hosting control panel. Check:

cPanel cron job email output
Server cron logs
PHP error logs
WHMCS activity logs
Hosting control panel logs

If cron output is being emailed, review those messages for errors.

9. Check PHP Version and Extensions

If the command uses the wrong PHP version, WHMCS automation may fail. This often happens after server upgrades or migrations. Check that the PHP CLI version used by cron is compatible with your WHMCS version and installed modules. Also confirm important PHP extensions are enabled, such as:

cURL
ionCube Loader
OpenSSL
PDO/MySQL
mbstring
zip

If a required extension is missing from PHP CLI, the website may work in the browser while the cron fails in the background.

10. Check WHMCS Automation Settings

Even if cron is running, automation behavior depends on your WHMCS settings. Review your automation configuration to make sure tasks are enabled and scheduled correctly. Check settings for:

Invoice generation
Payment reminders
Overdue notices
Service suspension
Service termination
Domain renewal reminders
Automation summary emails

If a specific task is not running, the issue may be the automation setting rather than the cron itself.

11. Check Module-Specific Cron Jobs

Some WHMCS modules use their own cron files in addition to the main WHMCS cron. For example, AI automation, notification modules, sync tools, and some provisioning modules may require separate scheduled tasks. Check the module documentation or dashboard for custom cron commands. You can explore automation tools in our WHMCS addon modules and WHMCS OTT modules categories.

12. Confirm Emails Are Working

Cron tasks often trigger emails such as invoices, reminders, and automation reports. If cron runs successfully but emails are not received, your issue may be email delivery rather than cron execution. Check SMTP settings, email templates, mail logs, SPF, DKIM, and DMARC records if scheduled emails are missing. For more details, read our guide on email not sending in WHMCS.

Quick Checklist to Fix WHMCS Cron Job Not Working

Check the cron command from WHMCS admin
Confirm the correct PHP CLI path
Confirm the correct cron file path
Set the cron schedule correctly
Check file permissions and ownership
Run the cron manually via SSH
Check WHMCS last cron run status
Review cron output and server logs
Confirm PHP CLI version and extensions
Review WHMCS automation settings
Check module-specific cron jobs
Confirm email delivery is working

Final Thoughts

When the WHMCS cron job is not working, billing and automation can quickly become unreliable. Invoices may not generate, reminders may not send, and service lifecycle actions may stop running. Start by checking the cron command, PHP path, file path, schedule, permissions, and server logs. Then review WHMCS automation settings and any module-specific cron requirements. If you need help with WHMCS cron setup, automation troubleshooting, or module configuration, visit our WHMCS services page for professional support.

Email Not Sending in WHMCS? Here’s How to Fix It

WHMCS MODULES — Mon, 22 Jun 2026 10:35:46 +0000

If emails are not sending in WHMCS, your customers may miss important invoices, password resets, order confirmations, support ticket replies, and renewal reminders. This can create billing delays, support confusion, and a poor customer experience.

WHMCS email issues can happen because of incorrect SMTP settings, wrong mail provider credentials, blocked ports, DNS problems, cron issues, email template settings, or server mail restrictions.

In this guide, we’ll explain how to troubleshoot and fix email not sending in WHMCS step by step.

Why WHMCS Emails Are Important

WHMCS uses email for many important customer and admin notifications. If email delivery stops working, your billing and support workflow can be affected quickly.

WHMCS emails may include:

Invoice created notifications
Payment confirmation emails
Order confirmation emails
Account welcome emails
Password reset emails
Support ticket replies
Service renewal reminders
Overdue invoice notices
Suspension and termination notices

For hosting companies, IPTV resellers, SaaS platforms, and digital service providers, email delivery should be tested regularly.

Common Reasons Emails Are Not Sending in WHMCS

Before changing many settings, it helps to understand the common causes behind WHMCS email problems.

Incorrect SMTP hostname, port, or encryption
Wrong SMTP username or password
Mail provider blocking login attempts
Server firewall blocking outgoing mail ports
PHP mail disabled or restricted by hosting provider
Missing SPF, DKIM, or DMARC DNS records
WHMCS cron not running correctly
Email templates disabled or misconfigured
Admin or client email address entered incorrectly
Mail is sent but landing in spam or junk folder

1. Check WHMCS Mail Settings

Start by checking your WHMCS mail configuration. In WHMCS admin, go to the mail settings area and confirm whether you are using PHP Mail or SMTP.

For most production websites, SMTP is usually recommended because it is more reliable and easier to troubleshoot.

Check these settings carefully:

Mail type
SMTP hostname
SMTP port
SMTP username
SMTP password
SMTP SSL or TLS setting
From name and from email address

A small typo in the hostname, username, password, or port can stop WHMCS from sending emails.

2. Use the Correct SMTP Port and Encryption

Different mail providers require different SMTP ports and encryption settings. Using the wrong combination can cause connection failures.

Common SMTP settings include:

Port 587 with TLS
Port 465 with SSL
Port 25 without encryption or with server-specific rules

Many hosting providers block port 25 to reduce spam, so port 587 or 465 is usually better when using SMTP.

3. Confirm SMTP Username and Password

If WHMCS cannot authenticate with your mail provider, emails will not send. Make sure the SMTP username and password are correct.

Also check whether your provider requires:

Full email address as username
App password instead of regular account password
Two-factor authentication compatible mail password
Authorized sending domain
Verified sender identity

If you recently changed your email password, update it inside WHMCS as well.

4. Test Email Sending From WHMCS

After checking mail settings, send a test email from WHMCS if the option is available. This helps confirm whether WHMCS can connect to the mail provider and send messages successfully.

If the test fails, note the exact error message. It may mention authentication failure, connection timeout, SSL error, blocked port, or invalid sender address.

These error messages can help identify whether the problem is inside WHMCS, your mail provider, or the server network.

5. Check WHMCS Email Templates

Sometimes WHMCS can send emails, but a specific email type is not being sent because the related template is disabled or customized incorrectly.

Check your email templates for:

Disabled templates
Missing subject lines
Broken merge fields
Incorrect sender settings
Custom template errors

If one email type does not work but others do, the template may be the issue.

6. Check WHMCS Cron Jobs

Some WHMCS emails depend on automation tasks. If your WHMCS cron is not running correctly, renewal reminders, overdue notices, and other scheduled emails may not send.

Check that your WHMCS cron is configured on the server and running at the recommended interval.

Cron-related email issues may affect:

Invoice generation emails
Payment reminder emails
Overdue invoice notices
Service suspension notices
Domain renewal reminders
Automation task notifications

If manual emails send but scheduled emails do not, cron should be checked first.

7. Review Mail Logs and Activity Logs

WHMCS and your server may keep logs that help identify email problems. Logs can show whether WHMCS tried to send an email and whether the server accepted or rejected it.

Check:

WHMCS activity log
WHMCS email message log, if available
Server mail logs
SMTP provider logs
Hosting control panel email logs

If WHMCS says the email was sent but the customer did not receive it, the issue may be spam filtering, DNS authentication, or provider delivery rules.

8. Check SPF, DKIM, and DMARC Records

Email delivery depends heavily on DNS authentication. If SPF, DKIM, or DMARC records are missing or incorrect, emails may be rejected or sent to spam.

Important DNS records include:

SPF: Defines which servers are allowed to send email for your domain
DKIM: Adds a digital signature to verify email authenticity
DMARC: Tells receiving mail servers how to handle failed authentication

For better delivery, configure these records according to your mail provider’s instructions.

9. Check Spam and Junk Folders

Sometimes WHMCS emails are being sent successfully but are landing in spam or junk folders. This often happens when DNS records are incomplete, the sender domain has low reputation, or the email content looks suspicious.

To reduce spam placement:

Use SMTP instead of basic PHP mail
Configure SPF, DKIM, and DMARC
Use a professional sender email address
Avoid spammy subject lines
Do not use too many links in system emails
Keep email templates clean and professional

10. Check Server Firewall and Hosting Restrictions

Your server or hosting provider may block outbound SMTP ports. This is common on VPS, cloud servers, and shared hosting environments.

Ask your hosting provider or server admin to confirm whether outbound SMTP is allowed on the required port.

Commonly checked ports:

25
465
587

If the port is blocked, WHMCS will not be able to connect to your SMTP provider even if your credentials are correct.

11. Check PHP Mail If You Are Not Using SMTP

If you are using PHP Mail, delivery depends on the server’s mail configuration. Many hosts limit or disable PHP mail because it can be abused for spam.

PHP mail can fail because of:

Missing mail server configuration
Hosting restrictions
Server reputation problems
Incorrect sender address
Messages rejected by receiving mail servers

If PHP Mail is unreliable, switch to SMTP with a trusted email provider.

12. Use a Reliable Mail Provider

For business websites, it is better to use a reliable transactional email provider or professional SMTP service instead of relying only on server mail.

A good mail provider can improve:

Email delivery reliability
Authentication setup
Log visibility
Bounce tracking
Spam reputation
Sending performance

This is especially important for WHMCS websites that send invoices, renewal reminders, support emails, and service notifications.

13. Email Notifications Beyond Standard Email

If your business depends on fast alerts, you can also use notification integrations alongside email. For example, Telegram, Discord, or SMS alerts can notify admins about new orders, invoices, tickets, and important system events.

You can explore related tools in our WHMCS addon modules category.

Quick Checklist to Fix Email Not Sending in WHMCS

Check WHMCS mail settings
Use correct SMTP hostname, port, and encryption
Confirm SMTP username and password
Send a test email from WHMCS
Check email templates
Confirm WHMCS cron is running
Review WHMCS and server mail logs
Configure SPF, DKIM, and DMARC
Check spam or junk folders
Confirm SMTP ports are not blocked
Switch from PHP Mail to SMTP if needed
Use a reliable mail provider

Final Thoughts

Email not sending in WHMCS can affect billing, support, renewals, and customer communication. The most common causes are incorrect SMTP settings, blocked ports, wrong credentials, missing DNS authentication, cron issues, or mail provider restrictions.

Start with SMTP settings, test email sending, review logs, and confirm your DNS records. If scheduled emails are not sending, check the WHMCS cron job. If emails are sent but not received, focus on spam filtering and domain authentication.

If you need help with WHMCS email setup, module configuration, or troubleshooting, visit our WHMCS services page for professional support.

How to Fix License Invalid Error in WHMCS

WHMCS MODULES — Sun, 21 Jun 2026 20:46:35 +0000

The WHMCS license invalid error usually appears when WHMCS cannot verify your license details correctly. This can happen because of an incorrect license key, changed domain, changed IP address, changed installation directory, server firewall issue, or connection problem with the license verification system. If you recently moved WHMCS to a new server, changed your domain, restored a backup, updated DNS, or installed a licensed WHMCS module, you may see a license invalid message until the license details are corrected. In this guide, we’ll explain the common reasons behind the WHMCS license invalid error and the steps you can follow to fix it.

What Does License Invalid Mean in WHMCS?

A license invalid message means WHMCS or a WHMCS module could not validate the license against the expected license details. Most license systems check information such as domain name, IP address, installation directory, and license key. If one of these values does not match the licensed record, the system may show a license invalid error.

Common Reasons for WHMCS License Invalid Error

The error can happen for several reasons. Before making major changes, check the most common causes first.

Incorrect license key entered
Domain name does not match the licensed domain
Server IP address changed after migration
WHMCS installation path changed
License needs to be reissued
Firewall is blocking license verification
cURL or SSL issue on the server
DNS has not fully propagated
Module license is expired, suspended, or assigned to another domain

1. Check the License Key

Start by checking that the license key is entered correctly. A missing character, extra space, or wrong license key can trigger the license invalid message. Make sure:

The license key is copied exactly
There are no spaces before or after the key
You are using the correct license for the correct product
The license is active in your client account

If you purchased a WHMCS module from us, log in to your client area and confirm the license status from your services list.

2. Confirm the Licensed Domain

Most WHMCS license systems are linked to a specific domain. If your WHMCS installation is running on a different domain or subdomain than the licensed record, the license may fail. For example, these may be treated as different locations:

example.com
www.example.com
billing.example.com
client.example.com

Check that the domain used in your browser matches the domain assigned to the license.

3. Check the Server IP Address

If you recently migrated WHMCS to a new VPS, hosting account, or server, the server IP address may have changed. Many license systems store the IP address as part of license validation. If the old IP is still attached to the license, you may need to reissue the license or update the allowed IP from the provider’s client area.

4. Check the WHMCS Installation Directory

Some license systems also validate the installation path. If WHMCS was moved from one folder to another, the license may need to be reissued. Examples of path changes include:

/home/user/public_html/whmcs/ to /home/user/public_html/billing/
/var/www/html/ to /var/www/domain/public_html/
Moving from a subfolder to the root domain

If your domain, IP, or directory changed, reissuing the license is often the fastest fix.

5. Reissue the License

Many WHMCS license providers allow you to reissue a license from the client area. Reissuing clears the old domain, IP, or path lock so the license can bind to the new installation details. General steps:

Log in to the provider’s client area
Open the related product or service
Find the license management section
Click reissue license, if available
Refresh your WHMCS admin area or module page

If you do not see a reissue option, contact the provider and ask them to reset the license for your new domain, IP, or installation path.

6. Check Firewall and Server Connections

License verification usually requires your server to connect to the license server. If outgoing connections are blocked, WHMCS or the module may not be able to validate the license. Check for:

Server firewall restrictions
Blocked outgoing HTTPS requests
Cloudflare or security rules affecting callbacks
Hosting provider network restrictions
ModSecurity rules blocking license requests

If you are using a VPS, confirm that outbound HTTPS connections are allowed.

7. Verify cURL and SSL Support

WHMCS modules often use cURL to communicate with license servers. If cURL is disabled or SSL verification fails, license checks may not work correctly. Ask your hosting provider or server admin to confirm:

PHP cURL extension is enabled
OpenSSL is enabled
CA certificates are installed and updated
The server can make HTTPS requests successfully

These checks are especially important after server migrations or PHP version changes.

8. Clear WHMCS Cache and Module Cache

Some modules cache license responses for performance. After fixing the license details, you may need to clear cache before the updated license status appears. You can try:

Clearing WHMCS template cache
Refreshing the module admin page
Logging out and back into WHMCS admin
Clearing server cache if enabled
Clearing Cloudflare cache if the module loads assets through the website

9. Check Module Compatibility

If the license error appears after updating WHMCS, PHP, or the module itself, compatibility may be involved. Make sure the module supports your current WHMCS and PHP versions. For best results, keep your WHMCS installation and modules updated. You can browse our WHMCS addon modules and WHMCS OTT modules to find modules built for modern WHMCS environments.

10. Contact the Module Provider

If you checked the license key, domain, IP, path, firewall, and cURL settings but the issue remains, contact the module provider. Share the exact error message and your environment details so they can check the license record. Useful information to provide:

License key or order ID
Licensed domain
Current WHMCS URL
Server IP address
WHMCS version
PHP version
Screenshot of the error
Whether the site was recently migrated

If you need help with WHMCS setup, module installation, or troubleshooting, you can contact us through our WHMCS services.

Quick Checklist to Fix WHMCS License Invalid Error

Check the license key is correct
Confirm the licensed domain matches
Check if the server IP changed
Check if the installation directory changed
Reissue the license if available
Confirm cURL and OpenSSL are enabled
Allow outbound HTTPS connections
Clear WHMCS and server cache
Check WHMCS and PHP compatibility
Contact the license provider if the issue remains

Final Thoughts

The WHMCS license invalid error is usually caused by a mismatch between the license record and your current installation details. In most cases, checking the license key, domain, IP address, installation path, and server connectivity will help you find the issue quickly. If your WHMCS installation was recently moved or restored, reissuing the license is often the simplest solution. If the issue is server-related, checking firewall, cURL, SSL, and outbound connections can help restore license verification. For professional help with WHMCS troubleshooting, module setup, or custom development, visit our WHMCS services page.

Best WHMCS Payment Gateway Modules for Seamless Billing

WHMCS MODULES — Sun, 21 Jun 2026 20:35:30 +0000

Payment processing is one of the most important parts of any WHMCS-based business. Whether you sell hosting, IPTV subscriptions, SaaS services, digital products, or custom development services, customers need a simple and secure way to pay invoices online. WHMCS payment gateway modules help you connect your billing system with different payment providers, allowing customers to pay through cards, crypto, wallets, hosted checkout pages, and local payment methods. In this guide, we’ll look at why WHMCS payment gateway modules matter, what features to look for, and how they can help create seamless billing for your business.

Why WHMCS Payment Gateway Modules Matter

WHMCS already provides a strong billing system for invoices, products, services, renewals, and customer accounts. But to collect payments efficiently, you need payment gateways that match your business model and customer preferences. A good WHMCS payment gateway module can help you:

Accept online payments directly from WHMCS invoices
Update invoice status automatically after payment
Support different customer payment preferences
Reduce manual payment verification
Improve checkout experience
Speed up service activation and renewals
Keep billing records organized inside WHMCS

You can explore available solutions in our WHMCS payment gateways category.

1. Card Payment Gateway Modules

Card payments are one of the most common online payment methods. Many customers prefer paying with credit or debit cards because the process is familiar and fast. WHMCS card payment gateway modules can connect your billing system with providers that support secure checkout, payment confirmation, invoice updates, and in some cases recurring billing. Card payment gateways are useful for:

Hosting companies
SaaS platforms
Digital service businesses
Subscription-based services
International customers

When choosing a card payment gateway, check supported countries, transaction fees, fraud controls, refund handling, and recurring payment support.

2. Crypto Payment Gateway Modules

Crypto payments are popular for businesses that serve global customers or want to accept digital currencies such as Bitcoin, stablecoins, or other supported cryptocurrencies. WHMCS crypto payment gateway modules allow customers to pay invoices using supported crypto networks. Depending on the gateway, payment confirmation can be sent back to WHMCS automatically so invoices can be marked as paid. Crypto payment gateways may be useful for:

Global digital service providers
IPTV and OTT businesses
Privacy-focused customers
Businesses with international payment challenges
Companies that want alternative payment methods

Before using a crypto gateway, review confirmation times, supported coins, conversion options, fee structure, and local compliance requirements.

3. Hosted Checkout Payment Modules

Hosted checkout gateways redirect customers to a secure payment page hosted by the payment provider. After payment, the customer is returned to WHMCS and the invoice can be updated automatically. This approach is popular because sensitive payment details are handled by the provider, while WHMCS manages invoices, services, and customer records. Hosted checkout modules can help with:

Simpler PCI responsibility
Clean checkout flow
Provider-managed payment pages
Better trust for customers
Automatic payment callbacks or webhooks

For many businesses, hosted checkout is a practical balance between security, simplicity, and customer convenience.

4. Local and Regional Payment Gateways

Not every customer wants to use international card or crypto payments. Some markets rely heavily on local banks, wallets, QR payments, or country-specific payment providers. Local WHMCS payment gateway modules help businesses accept payments from customers in specific regions. This can improve conversion rates because customers are more likely to pay using familiar local methods. Local payment gateways are useful when:

Your customers are based in a specific country
International cards are not widely used
Local wallet payments are popular
You want to reduce payment friction
You need region-specific checkout options

5. Recurring Payment Support

Recurring payments are important for subscription-based businesses. If your customers pay monthly, quarterly, or annually, recurring billing can reduce missed payments and improve renewal consistency. Some WHMCS payment gateway modules support recurring payments or subscription billing. This allows customers to authorize future payments, helping renewals happen with less manual action. Recurring payment support is especially useful for:

Web hosting plans
SaaS subscriptions
IPTV and OTT renewals
Maintenance services
Membership-based services

If recurring billing is important for your business, always confirm that the gateway and module both support it properly.

6. Automatic Invoice Status Updates

One of the biggest benefits of WHMCS payment gateway modules is automatic invoice updating. When a customer pays successfully, WHMCS can mark the invoice as paid without admin involvement. This can trigger other WHMCS workflows such as:

Order activation
Service provisioning
Renewal processing
Unsuspension after payment
Payment confirmation emails
Automation hooks and module actions

For businesses using provisioning modules, payment automation is especially important because it connects billing with service delivery.

7. Payment Gateway Charges and Fee Control

Different gateways charge different transaction fees. Some payment methods may cost more than others, especially international cards, crypto processors, or high-risk payment providers. WHMCS addons can help apply payment method charges so businesses can recover processing costs transparently. This can be useful when you want to:

Add fixed or percentage-based gateway charges
Recover transaction costs
Encourage lower-cost payment methods
Show fees clearly on invoices
Protect profit margins

You can explore related tools in our WHMCS addon modules category.

8. Choosing the Best WHMCS Payment Gateway Module

The best payment gateway module depends on your business type, target customers, supported countries, risk level, and preferred payment methods. Before choosing a module, consider:

Does the gateway support your country?
Does it support your customer countries?
Are card, crypto, wallet, or local payments supported?
Does it update WHMCS invoices automatically?
Does it support recurring billing if needed?
Are refunds supported?
Are webhooks or callbacks reliable?
Does it work with the latest WHMCS version?
Does it require any special server configuration?

Answering these questions will help you choose a gateway that fits your billing workflow instead of creating extra admin work.

9. Payment Gateways for IPTV and OTT Businesses

IPTV and OTT businesses often need fast payment confirmation because customers expect quick activation and renewal. When WHMCS payments are automated, service delivery becomes smoother. For example, after a customer pays an IPTV invoice, WHMCS can mark the invoice as paid and trigger the connected OTT module to create, renew, or reactivate the service. You can browse IPTV automation products in our WHMCS OTT modules category.

10. Benefits of Seamless WHMCS Billing

Seamless billing is not just about accepting payments. It is about creating a smooth connection between checkout, invoices, payment confirmation, service activation, renewals, and customer communication. A well-configured WHMCS payment setup can help your business:

Improve checkout conversion rates
Reduce unpaid invoices
Speed up service delivery
Reduce support tickets
Improve customer trust
Keep financial records organized
Support customers in different regions

Final Thoughts

WHMCS payment gateway modules are essential for businesses that want secure checkout, automatic invoice updates, smoother renewals, and less manual billing work. Whether you need card payments, crypto payments, hosted checkout, local gateways, or recurring billing, the right WHMCS payment gateway module can make your billing system more professional and efficient. Explore our WHMCS payment gateways to find secure and reliable payment integrations for your WHMCS business.

WHMCS MODULES

XUI ONE WHMCS Module: Full Installation and Configuration Guide (2026)

What Does the XUI ONE WHMCS Module Do?

Requirements Before Installation

Step-by-Step Installation

Key Features After Setup

Common Issues and Fixes

XUI ONE Module vs OTT Master Panel — Which Should You Choose?

Pricing and Licensing

Related WHMCS IPTV Modules

How to Start an IPTV Reseller Business with WHMCS: Complete Setup Guide (2026)

What Is an IPTV Reseller Business?

What You Need Before Starting

Step 1 — Choose Your IPTV Panel Type

Step 2 — Install and Configure WHMCS

Step 3 — Connect Your IPTV Panel with a WHMCS Module

Step 4 — Set Up Payment Gateways

Step 5 — Create Your WHMCS Products

Step 6 — Test Before Going Live

Step 7 — Launch and Get Your First Customers

What Full Automation Looks Like

Summary: What You Need to Launch

NXT Dash WHMCS Module: Full Installation and Configuration Guide (2026)

What Does the NXT Dash WHMCS Module Do?

Requirements Before Installation

Step-by-Step Installation

Key Features After Setup

Common Issues and Fixes

One-Time Payment, Lifetime License

Related WHMCS IPTV Modules

OTT Master Panel for WHMCS: Complete Setup Guide for IPTV Resellers (2026)

What Is the OTT Master Panel for WHMCS?

Who Is It For?

Key Features

Requirements Before You Install

Step-by-Step Installation

Common Issues and How to Fix Them

Why Choose OTT Master Panel Over Individual Panel Modules?

Start With a Free Trial

Related Products

WHMCS Security Best Practices to Protect Your Billing System

Why WHMCS Security Matters

1. Keep WHMCS Updated

2. Use Strong Admin Access Protection

3. Block Fake Signups and Spam Registrations

4. Require Email Verification

5. Add Fraud Protection for Orders

6. Control Public Registration Access

7. Use Clear Terms Agreement During Checkout

8. Protect Payment and Billing Workflows

9. Secure File Permissions and Configuration Files

10. Monitor Logs and Suspicious Activity

11. Keep Modules Updated and Trusted

12. Use Automation Carefully

Quick WHMCS Security Checklist

Final Thoughts

WHMCS Module Not Working After Installation? Common Fixes

Common Signs a WHMCS Module Is Not Working

1. Check the Correct Upload Path

2. Confirm All Files Were Uploaded

3. Check Module Activation

4. Check PHP Version Compatibility

5. Check ionCube Loader

6. Review File and Folder Permissions

7. Check License Validation

8. Enable Error Display Temporarily

9. Check Product Configuration for Server Modules

10. Check Payment Gateway Settings

11. Check Hooks and Template Conflicts

12. Clear WHMCS and Browser Cache

13. Check Module Documentation

14. Use Updated Module Versions

Quick Checklist to Fix WHMCS Module Not Working

Final Thoughts

WHMCS Cron Job Not Working? How to Fix Automation Issues

What Does the WHMCS Cron Job Do?

Common Signs Your WHMCS Cron Is Not Working

1. Check the WHMCS Cron Command

2. Use the Correct PHP Path

3. Confirm the Cron File Path