How to Build an ISP Reseller and Sub-Account Management System with Billing Platforms
Resellers and local agents can help an internet service provider expand into new neighborhoods, buildings, cafés, rural communities, and business areas without placing every sales and support task on the central team.
A reseller may sell WiFi vouchers, register customers, collect payments, manage local installations, or provide first-line support. But reseller growth creates a new management challenge. The ISP needs to control permissions, pricing, customer ownership, voucher stock, commissions, payment reconciliation, service access, and reporting.
An ISP reseller and sub-account management system solves this by giving each reseller a controlled account or sub-account while keeping the provider in charge of the main platform, plans, network policies, financial rules, and security.
Internet providers can
Important: Reseller features, commissions, payment methods, permissions, and sub-account controls vary by platform, country, plan, account configuration, and rollout. Confirm the current functionality available to your business before publishing reseller terms or assigning live customer data.
What is an ISP reseller system?
An ISP reseller system lets independent agents or partner businesses sell and manage selected internet services under rules set by the primary provider.
The reseller may be able to:
•Register new customers
•Sell prepaid vouchers
•Assign service packages
•Collect or initiate payments
•View assigned customers
•Track sales
•Earn commissions
•Monitor voucher inventory
•Open support requests
•Review account status
•Manage local sub-accounts
The parent ISP retains control over pricing, package definitions, network profiles, customer data, payment rules, refunds, suspension policies, and overall reporting.
A well-designed system separates reseller convenience from provider governance. Resellers should have enough access to complete their work but not enough access to compromise other customers, financial records, or network security.
Providers building this type of workflow can
Why ISPs use resellers and agents
Expand local sales
A reseller may already have relationships with residents, businesses, students, hotel guests, cafés, or community groups. This makes it easier to sell packages in locations where the central ISP team has limited reach.
Support cash and local payments
Some customers prefer cash, bank deposits, mobile money, or assisted purchases. A local reseller can help customers choose a package and complete the payment process.
Sell WiFi vouchers
Agents can distribute prepaid hotspot codes through shops, reception desks, events, retail locations, and community networks.
Reduce installation and support pressure
A trained local partner may perform basic customer onboarding, collect installation information, and escalate technical issues to the ISP.
Build a multi-location business
A reseller model can help the ISP operate several locations while central management keeps consistent packages, access policies, customer records, and reports.
Design the reseller hierarchy
Before creating sub-accounts, define how the business is structured.
A simple hierarchy may include:
•Primary ISP account: owns the platform, network, packages, and commercial policies.
•Regional manager: oversees several locations or resellers.
•Reseller account: sells services and manages assigned customers.
•Agent account: sells vouchers or performs limited registration.
•Technician account: handles installations and support without financial access.
•Finance account: reconciles payments and commissions.
•Customer account: manages the customer’s own service through a portal.
Do not create a large hierarchy before testing a small model. Start with one parent account, one reseller, and a limited customer group.
Define whether a customer belongs to one reseller, one location, one region, or the central ISP. Ownership rules affect support, commissions, data access, and customer reassignment.
Sub-account permissions
Sub-accounts should use least-privilege access. A reseller needs access to assigned functions, not the entire ISP system.
Reseller permissions may include
•Create or invite customers
•View assigned customer profiles
•Sell assigned vouchers
•View package availability
•Initiate approved payments
•View personal sales reports
•Submit support tickets
•Request a customer transfer
Reseller permissions should usually exclude
•Changing global package prices
•Editing network-wide profiles
•Viewing unrelated customers
•Accessing full payment credentials
•Issuing unauthorized refunds
•Changing RADIUS secrets
•Managing router administrators
•Exporting the entire customer database
•Creating unlimited vouchers without controls
Finance permissions may include
•Review collections
•Reconcile payments
•Calculate commissions
•Approve refunds
•Review reseller balances
•Export financial reports
Technician permissions may include
•View installation details
•Update work orders
•Record equipment
•View service location
•Escalate network issues
Role separation reduces fraud, accidental changes, and data exposure.
For providers comparing sub-account and access-control workflows,
Customer ownership and assignment
The platform should clearly identify who owns or manages each customer.
A customer record may include:
•Parent ISP
•Reseller
•Agent
•Service location
•Package
•Account manager
•Registration source
•Installation technician
•Payment channel
•Support responsibility
Ownership affects who can view the customer, sell a renewal, earn a commission, receive a support request, and request a transfer.
Define reassignment rules before the first dispute. For example, a customer may move when a reseller stops operating, a service area changes, a customer requests central support, or a commission arrangement ends.
Keep a history of ownership changes. Never silently move a customer between reseller accounts without an audit record and appropriate business authorization.
Reseller package and pricing controls
The parent ISP should define the available packages. A reseller may receive the right to sell selected plans but should not change the network policy without approval.
A package can include:
•Customer price
•Reseller purchase price
•Commission or margin
•Billing period
•Download speed
•Upload speed
•Data allowance
•Device limit
•Expiry
•Installation fee
•Equipment charge
•Refund rule
Use clear pricing models:
Commission model
The reseller sells at the provider’s price and receives a defined commission after a qualifying payment.
Wholesale margin model
The reseller purchases voucher or service inventory at a wholesale price and sells at an approved retail price.
Revenue-share model
The provider and reseller share a defined portion of collected revenue according to location, plan, or customer type.
Fixed service fee
The reseller receives a fixed amount for a defined activity, such as installation or new customer registration.
Document when a commission is earned. Possible conditions include successful payment, completed activation, non-refunded transaction, minimum service period, or customer retention period.
Voucher stock management
For hotspot operations, resellers often need voucher inventory. A centralized platform should track the entire voucher lifecycle.
Useful statuses include:
•Created
•Allocated
•Assigned
•Sold
•Activated
•Used
•Expired
•Cancelled
•Returned
•Blocked
Assign vouchers in controlled batches. The reseller should see available stock, sold codes, remaining inventory, expiry, and commission where permitted.
If a code is lost or compromised, the provider should be able to block it without affecting unrelated vouchers. Do not use predictable codes or distribute untracked batches.
A reseller should not be able to generate unlimited codes outside the approved package, price, location, or validity rules.
To evaluate voucher and reseller management,
Payment and collection management
The reseller system must distinguish between selling a package and receiving a confirmed payment.
A reseller may use:
•Online card payments
•Mobile money
•Bank transfer
•Cash collection
•Payment links
•Customer portal
•Prepaid account balance
•Assigned voucher stock
The billing platform should record who initiated the payment, which customer or invoice was involved, the amount, channel, reference, status, and commission result.
Use payment states such as pending, successful, failed, refunded, reversed, disputed, and unmatched. Do not credit the reseller’s commission or activate service from an unverified screenshot.
Cash collections require additional controls. Record the collection, collector, customer, invoice, amount, date, receipt, deposit status, and reconciliation result.
Commission calculation and settlement
Commission reports should be transparent. The reseller should understand what was earned and why an amount is pending or reversed.
A commission ledger may show:
•Customer or invoice reference
•Package
•Sale date
•Gross amount
•Gateway fee where relevant
•Eligible commission base
•Commission rate
•Commission amount
•Status
•Refund or reversal
•Settlement date
Define the settlement cycle: daily, weekly, monthly, or after a customer retention period. Make clear whether commissions apply to new sales, renewals, upgrades, installation, vouchers, or only certain packages.
A refunded or reversed payment may require commission reversal. The system should show the adjustment rather than silently changing the balance.
Set minimum withdrawal amounts, supported payout methods, approval rules, and identity requirements according to the provider’s market and terms.
Customer support in a reseller model
The reseller may provide first-line support, but the central ISP must retain an escalation path.
Define who handles:
•Payment questions
•Voucher problems
•Login failures
•Speed complaints
•Installation delays
•Equipment faults
•Outages
•Refund requests
•Account transfers
•Security incidents
The support system should show the parent ISP, reseller, customer, package, payment status, router, location, and previous communication.
Do not allow a reseller to resolve a technical issue by changing a network-wide profile or sharing administrator credentials. Use approved support actions and escalation procedures.
Network access and reseller provisioning
If the reseller sells PPPoE or HotSpot service, the customer account must connect to the correct network policy.
For PPPoE, the reseller may register the customer and select an approved package. The billing or RADIUS workflow can then create or authorize the username, assign a profile, allocate an IP, and apply expiry.
For HotSpot, the reseller may sell a voucher or package. The system can generate the code, assign the validity and speed rules, and connect it to a router or location.
The reseller should not directly manage RADIUS secrets, router administrators, firewall rules, or global bandwidth profiles. Use a controlled provisioning workflow that applies only approved policies.
Providers evaluating reseller-linked provisioning can
Reseller dashboards and reports
A reseller dashboard should show the information needed to operate the business without exposing the parent ISP’s full data.
Useful reseller reports include:
•Active customers
•New registrations
•Renewals
•Voucher inventory
•Vouchers sold
•Revenue or collections
•Pending payments
•Commission earned
•Commission pending
•Refunds and reversals
•Customer churn
•Open support requests
•Installation pipeline
•Customers by location
The parent ISP dashboard should show aggregated and detailed views:
•Revenue by reseller
•Collection rate by reseller
•Customer growth
•Churn by reseller
•Support volume
•Voucher usage
•Commission liability
•Outstanding collections
•Fraud or unusual activity
•Reseller performance comparison
Reports should use consistent definitions. For example, distinguish sales value from collected cash and earned commission from pending commission.
Security and data protection
Sub-accounts increase the number of people who can access customer and business information. Security must be designed into the reseller model.
Use unique accounts, strong passwords, multi-factor authentication where available, role-based permissions, session controls, and login monitoring.
Limit data by parent account, region, reseller, location, or assigned customer. Do not let an agent search the full customer database by default.
Protect payment credentials, API keys, RADIUS secrets, router credentials, voucher stock, customer phone numbers, and account exports.
Log important actions:
•Customer creation
•Package change
•Voucher allocation
•Payment edit
•Refund
•Commission adjustment
•Account suspension
•Customer transfer
•Permission change
•Data export
Remove access when a reseller contract ends. Reconcile outstanding voucher stock, customer ownership, payments, equipment, and commission before closing the account.
For providers reviewing reseller security and permissions,
Reseller onboarding process
A professional reseller program should have a documented onboarding process.
Step 1: Verify the business or individual
Collect the information required for identity, contact, payment, tax, and compliance purposes.
Step 2: Define the territory or customer group
Specify the service area, locations, customer types, package access, and support responsibility.
Step 3: Sign commercial terms
Document prices, commissions, payment collection, refunds, customer data, support, branding, termination, and dispute processes.
Step 4: Create the sub-account
Assign only the required roles, packages, locations, voucher stock, and reports.
Step 5: Train the reseller
Explain customer registration, payment confirmation, voucher handling, support escalation, security, and reconciliation.
Step 6: Run a pilot
Start with a small customer group and limited inventory. Review sales, payments, support, and commission before increasing access.
Automated reseller lifecycle
The system should manage more than account creation.
Reseller activation
Verify identity, assign roles, configure packages, issue access, and record agreement status.
Inventory allocation
Assign vouchers or customer capacity with an owner, quantity, validity, and audit trail.
Customer registration
Capture required information, assign ownership, select package, and begin installation or activation.
Payment and commission
Confirm payment, activate service, calculate eligible commission, and update the reseller ledger.
Renewal
Attribute renewals according to the agreed rule. Decide whether the original reseller, current owner, or central ISP receives credit.
Suspension
If the reseller account or customer account becomes overdue, restrict service according to the provider’s policy. Do not automatically remove reseller inventory without reviewing active customers and unresolved payments.
Offboarding
Disable login, reconcile data, transfer customers, block unused vouchers, recover equipment, and settle commission.
Common mistakes to avoid
Do not give every reseller full administrator access. Use sub-accounts, roles, scopes, and approval workflows.
Do not allocate untracked voucher stock. Every batch should have an owner, status, and reconciliation record.
Do not pay commission on pending, refunded, reversed, or fraudulent transactions without a documented rule.
Do not let resellers change global package pricing or network policies without approval.
Do not transfer customers silently. Keep ownership and commission history.
Do not rely on manual spreadsheets for commission settlement when transaction volume grows.
Do not give agents access to payment credentials, RADIUS secrets, router management, or unrelated customer data.
Do not launch a reseller network without a clear support escalation and offboarding process.
Choosing a billing platform for resellers
When evaluating SopraEnt, Xenfi, or another ISP billing platform, ask for a demonstration of:
1.Parent ISP account
2.Reseller sub-account
3.Agent role
4.Customer assignment
5.Voucher allocation
6.Online and manual payment
7.Commission calculation
8.Renewal attribution
9.Customer transfer
10.Support escalation
11.Report filtering
12.Permission controls
13.Audit logs
14.Account closure
Also confirm current features, plan limits, country support, payment methods, customer-volume capacity, network integration, data export, support, and terms.
For a controlled evaluation,
Implementation roadmap
Phase 1: Define the program
Choose reseller types, territories, packages, pricing, commissions, support roles, payment methods, and customer ownership rules.
Phase 2: Create the hierarchy
Set up parent, regional, reseller, agent, technician, finance, and customer roles.
Phase 3: Configure packages and inventory
Create approved service plans, assign reseller visibility, and generate a small voucher batch if required.
Phase 4: Test payments and commissions
Run successful, pending, failed, refunded, and reversed transactions. Confirm service activation and commission status.
Phase 5: Test access and support
Verify PPPoE, HotSpot, RADIUS, package enforcement, customer search, support escalation, and account transfers.
Phase 6: Pilot and scale
Launch with one reseller or location. Review performance, reconciliation, security, and customer feedback before expanding.
Conclusion
An ISP reseller and sub-account management system can help internet providers expand sales, distribute WiFi vouchers, serve local communities, and manage multiple service areas without giving every partner full platform access.
The strongest design combines clear hierarchy, least-privilege roles, customer ownership, controlled packages, tracked vouchers, verified payments, transparent commissions, network provisioning, support escalation, reports, audit logs, and a documented offboarding process.
Start small. Create one reseller account, assign a limited package set, issue controlled inventory, test payment and commission workflows, and monitor customer support before building a larger partner network.
Frequently asked questions
What is an ISP reseller management system?
It is a platform workflow that lets agents or partner businesses sell, register, support, or manage selected internet services under permissions and commercial rules set by the primary ISP.
What is an ISP sub-account?
A sub-account is a controlled user or partner account under the main ISP account. It can access assigned customers, locations, packages, vouchers, reports, and actions without seeing the full platform.
How should ISPs manage reseller commissions?
Define the commission base, rate, qualifying event, settlement schedule, refund and reversal rules, and customer ownership. Record every sale and adjustment in an auditable ledger.
Can resellers sell WiFi vouchers?
Yes, when the billing platform supports voucher allocation and reseller permissions. Assign tracked batches, monitor sales and expiry, and block lost or compromised codes.
Can resellers register PPPoE customers?
A reseller may register customers and select approved packages when the platform and provider authorize that workflow. Network provisioning should apply only predefined profiles and policies.
How do I protect customer data in a reseller model?
Use separate accounts, least-privilege roles, customer-scoped access, strong authentication, audit logs, secure integrations, limited exports, and immediate offboarding when access ends.
Who owns a customer registered by a reseller?
The provider should define ownership in the reseller agreement and system rules. Track the parent ISP, reseller, location, registration source, support responsibility, and any ownership transfers.
Can SopraEnt and Xenfi support reseller workflows?
Feature availability depends on the platform, account, country, plan, permissions, and current rollout. Confirm support for sub-accounts, agents, vouchers, commissions, customer assignment, payments, reports, and network access before launch.
Where can I evaluate ISP reseller platforms?
You can
