Reseller Automation
Automating a back-connect reseller operation from package to payment
A growing proxy business needed its rotating network, subscription logic, reseller accounts, payment events, and usage reporting to operate as one system rather than a chain of manual tasks.
Network Model
Back-connect delivery
Team Profile
Small operations team
Account Model
Multi-tier users
Traffic Band
High hundreds of GB / month
Proxy Types
Residential + ISP + DC
Session Control
Rotation + persistence
Commercial Model
Subscription + usage
Automation
REST API + webhooks
The challenge
The network could already rotate addresses and serve multiple proxy categories, but the business around it remained fragmented. Plans, authentication rules, renewals, and reseller balances were maintained in separate systems with different sources of truth.
Package changes were risky because commercial state and network enforcement were not connected. A customer could pay for an upgrade before the corresponding limits were applied, while cancellations and expired access depended on delayed cleanup jobs.
The reseller program added another layer of manual work. Parent accounts, child users, commissions, branded access, and usage exports needed consistent boundaries that the existing tools could not enforce.
Previous setup
Business workflow before automation
Static network configuration for package and rotation rules
Subscriptions tracked separately from proxy authentication
Manual upgrades, renewals, suspensions, and balance corrections
Flat reseller accounts without delegated user boundaries
Usage exports assembled for support and billing disputes
Limited operational visibility across sessions, plans, and payments
Architecture after ProxyRequest
Network plane
Back-connect gateways
Geo and session policy
Concurrent connection control
Automatic failover
Commercial controls
Packages and quotas
Subscription lifecycle
Payment event handling
Usage-based adjustments
Reseller layer
Parent and child accounts
Delegated provisioning API
White-label access
Usage and commission reporting
The package definition became the shared contract between billing and traffic enforcement. Payment events update account state, the network applies the resulting limits, and reseller APIs expose only the users and operations allowed within each delegated scope.
Before / After
| Before | After |
|---|---|
| Plans described outside network configuration | Packages directly define traffic behavior |
| Renewals and suspensions applied by scheduled cleanup | Account state follows payment events |
| Rotation settings changed per gateway | Reusable session policies per product |
| Resellers shared broad administrative access | Scoped parent and child account hierarchy |
| Support assembled usage evidence manually | Per-user records available through dashboard and API |
| Business workflows depended on operator intervention | Webhooks and API actions handle the lifecycle |
Outcomes
Commercial events became enforceable network state. Purchases, renewals, limit changes, and suspensions reached the proxy layer without a manual handoff.
Reseller growth no longer widened administrative access. Each reseller could manage isolated child accounts through a scoped interface.
Package experimentation became safer. Product, quota, concurrency, and rotation rules could change through versioned configuration.
Support gained attributable records. Session and usage data connected customer questions to the same state used for billing.