Complete Documentation

1. Getting Started

CP Binary MLM combines product sales, member registration, sponsor relationships, binary placement, Product Volume, wallet operations, withdrawals, content management and administration in one responsive PHP/MySQL application.

Core journey

1. Create a member account with a valid sponsor.
2. Open the qualifying Products page.
3. Purchase a qualifying product using the configured payment or Purchase Wallet workflow.
4. The order records price and Product Volume (PV).
5. The member is activated according to the configured product activation rule.
6. The member is placed on the Left or Right binary leg.
7. PV contributes to binary leg volume and matching volume is evaluated.
8. Eligible pair commission is credited according to Binary Settings.

2. System Requirements

• PHP 7.4+ recommended; PHP 8.x recommended for production.
• MySQL 5.7+ or compatible MariaDB.
• Apache with mod_rewrite enabled.
• PDO/MySQLi database support.
• PHP extensions required by the installed payment and application modules.
• Writable runtime/upload/backup locations used by the application.
• SSL/HTTPS strongly recommended for production.

Before production deployment, configure the correct timezone, database credentials, mail settings and payment credentials.

3. Installation

Fresh installation

1. Upload the application files to the document root.
2. Create an empty MySQL database and database user.
3. Open the installer and enter the database credentials.
4. Run the installer and create the initial administrator account.
5. Verify the public site, admin panel and member login.
6. Change all demo credentials before production use.

Production checklist

• Enable HTTPS.
• Disable or protect installer access after installation.
• Use strong administrator credentials.
• Configure scheduled backups according to your hosting environment.
• Configure payment gateway production credentials only after successful sandbox testing.

4. Admin Panel

The admin control panel provides centralized management of users, products, product orders, Binary Settings, content, activations, withdrawals, wallet transactions, reports, settings and system updates.

Dashboard

The dashboard provides operational counters, recent member activity, withdrawal queues, income activity and quick links to the main modules.

Users

Administrators can review member profiles, status, sponsor information, activation state and network-related records. Use the dedicated Add/Edit pages for record changes.

5. Product Management

Products are the commercial qualification mechanism for this system. Create products with a name, SKU, price, PV, stock, description, image and active/featured state.

Recommended product fields

• Product Name — customer-facing product title.
• SKU — unique product reference.
• Price — selling price.
• PV — qualifying Product Volume.
• Stock — available quantity; use unlimited stock only where supported.
• Status — controls whether the product can be purchased.

The demo installation includes four product offers: Binary Starter Pack, Binary Growth Pack, Binary Pro Pack and Binary Elite Pack. These are product offers, not separate compensation plans.

6. Product Orders

Every purchase creates an order and order-item record. The order should retain the product name, SKU, quantity, unit price, line total, PV and payment method so the transaction can be audited later.

Order lifecycle

Pending → Paid → activation/PV processing → completed. Failed, cancelled or refunded orders must not create duplicate commission events.

7. Binary Compensation

CP Binary MLM uses one Product-Based Binary compensation model. There are no selectable Unilevel, Matrix, Generation or Single-Leg compensation plans.

Placement

The binary tree has two positions under each member: Left and Right. The administrator can configure automatic placement or a preferred leg.

PV and matching

Qualifying product PV is attached to the purchaser and contributes to the appropriate binary leg. When both legs contain qualifying volume, the engine can match the configured pair volume unit and calculate the configured pair commission.

Carry/flush

After a successful pair, the configured carry-forward/flush rule determines how remaining volume stays available for future matching.

Daily limits

If a daily binary income limit is configured, commission credits are capped according to that setting.

8. Binary Genealogy

The genealogy page displays the actual Left/Right binary structure. Member cards can show member ID, name, position, activation state and PV. Hover details can expose additional member information without cluttering the tree.

Empty Left and Right positions are displayed as available placement slots where appropriate.

9. Member Workflow

1. Register using a valid sponsor/referral link.
2. Log in to the member dashboard.
3. Complete profile and required payment/wallet details.
4. Open Shop Products.
5. Select a qualifying product.
6. Complete payment.
7. Review the order and activation state.
8. Use My Team and Binary Genealogy to follow the network.
9. Review Income and Wallet transactions.
10. Submit eligible withdrawal requests.

10. Wallet & Payments

The wallet area records credits and debits associated with purchases, income, transfers and other supported transactions. The Purchase Wallet is used where the configured product workflow requires wallet funding before checkout.

Payment gateways

Configure supported gateways such as PayPal, Stripe, Razorpay or manual payment according to the installed module. Gateway credentials should never be exposed in public content.

11. Withdrawals

Members can submit eligible withdrawal requests using the configured withdrawal method. Administrators can review, approve or reject requests. Keep bank/payment details accurate and verify requests according to your business process.

12. Franchisee Module

The franchisee area can be used for controlled business/franchise operations where enabled. Franchisees may manage assigned members, wallet funding, activation workflows, reports and withdrawals according to their permissions.

13. CMS & Legal Content

The Content module manages the public website pages and their database-backed HTML content. Editable content can include Home, About, How It Works, Products, Income, FAQ, Contact, Privacy Policy, Terms and Documentation.

Use the dedicated content editor to update Main Content / Legal HTML. HTML is sanitized before display to reduce unsafe markup and scripting risks.

14. Settings

Platform settings are organized into tabs so administrators can manage general branding, support/contact details, payment information, banking information and social links without placing every field in one long form.

15. System Updater

The built-in System Update module accepts an official ZIP package containing a newer VERSION.txt. The updater validates the package, rejects older versions and unsafe paths, creates a backup, preserves database configuration/runtime data, replaces application files and executes the included database migration.

Update process

1. Download the official update ZIP.
2. Open Admin → System Update.
3. Select the ZIP and review the upload status.
4. Validate the package.
5. Allow the automatic backup to complete.
6. Allow file replacement and database migration to finish.
7. Confirm the new version in the admin header/sidebar.

Never interrupt an update while files or migrations are being applied. Always keep an external backup before a major production update.

16. Security & Best Practices

• Use HTTPS in production.
• Use unique, strong administrator passwords.
• Keep payment secrets outside public HTML and source control.
• Review admin and withdrawal activity regularly.
• Restrict writable directories where possible.
• Keep regular database and file backups.
• Install only trusted official update packages.
• Test updates on a staging installation before production when practical.

17. Multi-Language

The frontend is prepared for translation workflows. If a translation provider or gTranslator integration is enabled, configure it according to the provider requirements and verify translated navigation, forms and dynamic content before publishing.

18. Troubleshooting

Blank documentation content

Open Admin → Content → Documentation and save the page content. The current release also seeds the full documentation HTML into the CMS database during migration.

Updater rejects a package

Confirm that the ZIP contains a root-level VERSION.txt, the version is newer than the installed version, and the archive contains no unsafe absolute or parent-directory paths.

Products do not appear

Confirm that the product is active, has a valid price/PV and that the database migration has completed successfully.

Binary volume does not change

Confirm that the order is paid/completed, the product has PV, the member is activated and the member has a valid Left/Right placement.

19. Support & Customization

For deployment-specific support, provide the installed version, PHP/MySQL versions, relevant error message and the exact module/page where the issue occurs. Never send production passwords, payment secrets or database credentials.

20. Legal & Business Notice

Configure your own Terms & Conditions, Privacy Policy, refund rules, product policies, income disclosures and applicable regulatory notices before commercial launch. The software's compensation configuration is a technical mechanism; it does not guarantee income or financial results.