How to resell proxies with zero capital

2026-10-27 · Bazyl

Most people who want to sell proxies in their Discord stop at the same wall: you have to buy a block of bandwidth before you sell a single gigabyte. If nobody buys, that money sits in a pool doing nothing. Revenue share removes that wall. Your customer pays you, our share comes out of that same order, and you never hold stock.

This post walks through how it works, what you need on day one, and when it stops being the right model.

The old way needs money you don't have yet

The classic reseller deal is wholesale. You buy a pool of gigabytes, then hand them out to customers and charge whatever you like. The margin is good. The problem is the order of events: you pay first, you sell later.

For a new server that is backwards. You don't know yet whether your members will buy on a Pokémon restock night or wait for a ticket on-sale. Guess wrong and you are sitting on data you paid for weeks ago.

Revenue share flips the order

On revenue share nothing happens until a customer pays. The flow looks like this:

member pays you ──▶ your payment account (your name on the receipt)
                     ├─ our share   ──▶ taken from this order, automatically
                     └─ the rest    ──▶ your balance
payment confirmed ──▶ data lands on the member's proxy account ──▶ order completed

Three things follow from that picture.

• You are the seller. The money lands in your own payment account, under your brand. Your terms, your refunds.
• Our share is per order. There is no monthly fee and nothing to prepay. A month with no sales costs you nothing.
• Delivery is automatic. Once the payment clears, the gigabytes land on that customer's account on their own. You don't copy credentials at 2 a.m. while a drop is live.

What you need on day one

Less than most people expect.

1. A partner account. Open a ticket in our Discord, tell us what you sell and who to. We set the account up and agree the share with you.
2. Your payment account connected. In the partner portal, Settings, Integrations. One onboarding flow, then the status turns ready.
3. A page after payment. Where the buyer lands once they've paid. A thank-you channel link or your own site works.
4. A way to sell. Either a payment link you make in the portal and post in your server, or a checkout your bot creates through the API.

That is it. No pool, no invoice from us, no stock to watch.

Selling from a bot instead of by hand

If your server already runs a bot, it can create the payment page itself. One call per order, server-side only:

curl -X POST https://api.basilproxies.com/api/reseller/v1/checkout \
  -H "Authorization: Bearer $KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: order-8831" \
  -d '{"customerId":"CUSTOMER_ID","amountGb":10,"priceMinor":2500}'

The answer carries a checkoutUrl. Your bot DMs it to the member. When they pay, the order turns completed and the customer's proxy lines work. priceMinor is your price, in your own currency's minor units: you set it per order, and an order whose price can't cover the share is refused before anyone pays.

Keep the Idempotency-Key one per order. A retry with the same key never makes a second payment page.

Your brand stays yours

A member who buys from you should never land on our site. On a partner account they don't.

• Proxy lines can carry your own hostname, so the member pastes your domain into their bot.
• The gateway's login prompt names no supplier.
• The member gets no Basil dashboard, login or email. They are your customer.

For a Discord brand that matters more than it sounds. Members screenshot their bot settings into channels all day.

Why this network, for this traffic

I run ticket and Pokémon traffic myself, and so does the rest of the team. The network was tuned around what drop nights do to a gateway: sudden surges at on-sale time, long queues, checkouts that must keep one IP.

• Sticky sessions hold up to 24 hours, so a session survives a long ticket queue.
• Targeting goes down to city and ISP, for sites that care where a buyer is.
• Gateways in Europe, the US and Asia-Pacific, so members pick the one nearest their bot server.

You are not reselling a scraping product and hoping it holds on release day. See the ticket drops use case for how the pool behaves on an on-sale.

When to switch to a prepaid pool

Revenue share is the right start. It is not always the right finish.

Once your server sells every week and you can predict roughly how much, a wholesale pool pays you more per gigabyte: you keep the whole difference instead of sharing each order. Pool data never expires, so a slow week costs nothing once you're there.

A simple rule: stay on revenue share while you're still finding out what sells. Ask about a pool once three or four quiet weeks wouldn't worry you. Both live on the same partner account, so switching is a conversation, not a migration.

Start

Read how the proxy reseller program works, then open a ticket in our Discord.