MidnightStreamer Reseller Module for WHMCS

It connects WHMCS with MidnightStreamer reseller panels to automate Streamline and MAG provisioning, renewals, lifecycle actions, package assignment, bouquets, and customer service delivery.

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

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

Yes, you need authorized access to a compatible MidnightStreamer reseller panel.

It uses the configured panel URL, reseller username, and password.

No, this integration uses the supported panel login workflow rather than API-key authentication.

No, reseller-panel access must be obtained separately from an authorized provider.

No, required panel credits must be purchased and maintained separately.

Yes, the module can test the supplied panel credentials before saving the connection.

Yes, administrators can add and manage multiple panel connections.

Yes, each product can be assigned to an appropriate configured MidnightStreamer panel.

Yes, administrators can update existing panel details.

Yes, panel connections that are no longer required can be deleted.

Separate MAG Portal, M3U, and Web Portal URLs can be configured for each connection.

Yes, supported panel information includes the available reseller credit balance.

Yes, supported services can be created through the WHMCS activation workflow.

Yes, it can provision username-and-password-based Streamline accounts.

Yes, it can provision MAG services using customer-provided MAC addresses.

Yes, each WHMCS product can be configured for the appropriate service type.

Yes, available panel packages can be loaded during WHMCS product configuration.

Yes, the module displays supported package information to help administrators select the appropriate option.

Yes, each WHMCS product can be assigned its own MidnightStreamer package.

No, WHMCS controls product pricing while package selection controls what is provisioned on the panel.

Yes, it loads bouquets available for the selected package.

Yes, supported products can be configured with multiple bouquet selections.

Yes, the configured bouquets are applied when creating supported services.

Yes, supported renewal actions use the configured package and bouquet selections.

Yes, supported package actions use the updated package and bouquet configuration.

Customer-facing bouquet selection should only be advertised if enabled by your installed module configuration.

Client-side bouquet editing should only be advertised if supported by your installed version.

Yes, it can generate usernames and passwords automatically.

Yes, supported generation rules include numeric formats.

Yes, supported generation rules include alphanumeric formats.

Yes, administrators can set the desired generated credential lengths.

Yes, supported product fields can allow customers to submit preferred credentials during ordering.

Yes, administrators can rely on automatic generation instead.

Yes, administrators can customize the field names used for usernames, passwords, and MAG addresses.

Yes, supported password storage uses the WHMCS encryption workflow.

Yes, supported MAG products validate the customer-provided MAC address format.

Yes, the returned Streamline or MAG identifier is saved with the corresponding WHMCS service.

Yes, supported service creation can include reseller notes generated from WHMCS information.

Supported variables include service ID, client ID, customer name, email address, and telephone number.

Yes, existing Streamline subscriptions can be extended through the supported renewal action.

Yes, supported MAG subscriptions can also be renewed.

Yes, supported renewal and package actions update the relevant WHMCS service dates using panel expiry information.

Yes, supported Streamline and MAG services can be disabled through the WHMCS suspension action.

Yes, the supported unsuspension action can re-enable the corresponding panel service.

Yes, the supported termination action removes the corresponding service from the panel.

Yes, supported package changes can be initiated from WHMCS.

No, supported creation, renewal, suspension, unsuspension, package-change, and termination actions are handled through WHMCS.

The module returns the available panel error and records supported activity for troubleshooting.

Yes, returned expiry dates can update WHMCS next due and next invoice dates.

Service information is synchronized during supported provisioning and lifecycle actions.

Yes, supported provisioning and lifecycle actions are stored in a dedicated activity log.

Logs can include the action, service ID, client ID, status, request information, response, and timestamp.

Yes, administrators can review panel requests and responses to identify connection, package, credential, or credit problems.

Yes, access to module logs should be limited to trusted administrators.

Customers can view their IPTV username, password, due date, portal links, playlist formats, and setup information.

Yes, the supported client interface provides convenient credential visibility controls.

Yes, the configured M3U portal or DNS address can be displayed.

Yes, the configured Web Portal can be opened for supported online viewing.

Yes, the client area displays the applicable WHMCS due-date information.

Yes, the client interface can link customers to the WHMCS knowledgebase.

Yes, supported Streamline customers can access multiple playlist and device formats.

Yes, Simple List output is available with supported HLS, MPEG-TS, and RTMP options.

Yes, M3U Plus output is available with supported HLS, MPEG-TS, and RTMP options.

Yes, the supported client tools include Enigma2 OE 2.0 setup scripts.

Yes, supported GigaBlue output formats are included.

Yes, a supported DreamBox OE 2.0 format is available.

Yes, a WebTV List format is included among the supported customer options.

Yes, supported client controls make playlist and device information easier to select and copy.

MAG delivery uses the configured MAC address and portal information, while available client tools depend on the product template.

WHMCS can send the configured product welcome email after successful activation.

Yes, supported WHMCS merge fields can include the assigned username, password, and service information.

No, payments remain handled by WHMCS and the selected payment gateway.

No, payment-card information is not required for MidnightStreamer provisioning.

Yes, the panel may reject account creation or renewal when the reseller balance is insufficient.

No, administrators must maintain sufficient panel credits separately.

No, it automates service management for your authorized MidnightStreamer reseller panel.

No, streaming and content delivery remain handled by the connected panel infrastructure.

No, the business using the module is responsible for content rights, licensing, and legal compliance.

Yes, it must communicate with the configured MidnightStreamer panel.

Yes, HTTPS is strongly recommended to protect customer credentials and administrative data.

Provisioning, renewal, lifecycle, and information requests may fail until communication is restored.

Yes, supported failures are returned through WHMCS and recorded in the module activity log.

Yes, scheduled billing, invoice, suspension, and renewal workflows depend on normal WHMCS cron operation.

No separate custom cron is normally required for the core provisioning and lifecycle actions.

No, it operates through WHMCS addon and provisioning-module functionality.

Standard installation does not require editing WHMCS core files.

Yes, supported client-area tools are designed for standard WHMCS structures.

Compatibility should be tested with your specific Lagom version and customizations.

Yes, heavily customized client-area layouts may require visual changes.

Yes, it is suitable for existing resellers who want to connect ordering, billing, provisioning, and customer delivery with WHMCS.

Automatic import should only be advertised if it is available in your installed module version.

No automatic cross-panel migration should be assumed; migration may require manual work or custom development.

Yes, it automates supported provisioning, renewals, lifecycle actions, package and bouquet assignment, credential handling, and customer delivery.

No, but connection validation, credential rules, package selection, and activity logs help reduce and diagnose common problems.

It is suitable for MidnightStreamer IPTV resellers, hosting providers offering IPTV services, and businesses seeking complete WHMCS-based provisioning and lifecycle automation.