Build your own customer experience around proxy-user provisioning, bandwidth allocation, usage records, and source-IP whitelists. Databay reseller access is qualified by sales; your business keeps ownership of checkout, billing, tax, support, and end-user controls.
Content reviewed . Approval is not automatic; commercial terms and KYC requirements depend on the proposed account.
It fits a business that already owns its customer and commercial systems and needs programmable proxy infrastructure behind them. The table separates API-backed capabilities from decisions your team must make before sales can qualify the account.
| Requirement | Databay scope | Your qualification check |
|---|---|---|
| Separate customer access | Approved reseller accounts can create, list, update, and delete proxy users through the account API. | Define how your system maps one customer to one proxy user and protects credentials. |
| Allocate purchased traffic | The API can read a proxy user’s traffic allocation and transfer bandwidth with a product and expiration. | Model failed transfers, expiration, balance checks, and idempotent retries before launch. |
| Measure consumption | The API exposes traffic details and bandwidth logs for a specified proxy user. | Decide how often to reconcile usage and how your customer-facing meter handles delay or disagreement. |
| Authorize source IPs | Proxy-user whitelist records can be listed and added; account APIs also support removing whitelist entries. | Build validation, ownership checks, audit history, and a safe removal path into your application. |
| Commercial reseller terms | Pricing, account approval, product scope, limits, and onboarding are handled through sales. | Bring a volume forecast, target markets, required networks, concurrency, and launch timeline. |
The API handles infrastructure operations. It does not replace the commercial and compliance gates around those operations.
Tell sales what you plan to resell, expected volume, markets, customer profile, technical architecture, and support model. Approval is not automatic, and KYC may apply.
Keep your customer record, plan, payment state, tax treatment, and support history in your own system. Store the Databay proxy-user identifier as an infrastructure reference.
Create the proxy user, transfer the approved bandwidth, and configure source-IP whitelists only after your onboarding and payment rules pass.
Read traffic details and logs on a documented schedule. Preserve allocation, transfer, usage, and whitelist events so support and disputes can be investigated.
Apply your customer limits and stop conditions, investigate misuse, and suspend access when required. Databay’s Terms and Acceptable Use Policy still govern every end user.
A serious reseller plan makes ownership explicit before integration. These columns are intentionally asymmetric: Databay supplies a bounded infrastructure layer, while the reseller owns the customer business built on top of it.
Databay scope
Reseller scope
The commercial-reselling section of the Databay Terms of Use makes the reseller responsible for end-user activity and requires a written end-user agreement at least as restrictive as Databay’s Terms and Acceptable Use Policy. Review those obligations with qualified counsel for your business and jurisdictions.
A concrete brief makes it possible to assess product fit, account controls, compliance review, and commercial scope without implying that every requested capability is available.
Send sales the products, markets, traffic forecast, customer model, required controls, and launch timeline. The reply can then address scope, review, and commercial terms.
Contact-sales pricing. KYC may apply. No instant approval or unconfirmed white-label feature is promised.
