Selling proxies inside your Discord server

2026-10-27 · Bazyl

A Discord server is a good shop for proxies. The buyers are already there, they already talk about drops, and they trust the people who run the server. What breaks most server shops is not demand. It's the setup: hand delivery, one giant support channel, and credentials pasted into DMs at the worst possible moment.

Here is the layout I'd build if I started a proxy brand in a server today.

Four channels, not twelve

New shops tend to open a channel for every product, region and question. Members can't find anything, and you answer the same message five times. Start with four.

#buy-proxies     read-only: what you sell, one payment link per size
#setup           read-only: how to paste lines into the bots your members run
#drop-status     read-only on quiet days, live updates on drop nights
tickets          private, one per member problem

Everything else can wait until members ask for it twice.

#buy-proxies: one link per size

Members on a drop night don't read paragraphs. Give them a short list of sizes, each with its own payment link, and nothing else.

With a revenue-share partner account you make those links in the partner portal. The member pays you, our share comes out of that order, and the data lands on their account on its own. You don't need any money in the bank to post the first link. The no-capital post walks through that model.

Pin the message. Edit it when sizes change; never post a new one, or old links float around in screenshots.

#setup: answer the first question before it's asked

The first thing a new buyer asks is "where do I paste this". Answer it once, per bot your members actually run. A short block per bot is enough:

Bot: <the bot your group uses>
Proxy format:   host:port:user:pass
One line per task. Use sticky lines for checkout tasks,
rotating lines for monitors and queue entry.

Add the one mistake you see most often under each block. In ticket groups that's usually rotating lines on a checkout task, which changes the IP mid-purchase.

#drop-status: say what's happening

On a big on-sale or a Pokémon Center restock, members ask "is it just me" every thirty seconds. One channel where you post short updates saves you dozens of DMs.

Keep the messages factual. "Queue is up on the UK site, sticky lines are holding" is useful. "We're the best proxies" is not.

Tickets: one problem, one channel

Anything about a single order goes in a private ticket: a payment that didn't go through, data that didn't arrive, a member who wants a refund. It keeps payment details out of public channels and gives you a record per member.

Write the three answers you'll give most often into a saved reply:

• "My proxies say login failed." A brand-new account can take a minute or two before it works everywhere. Wait, then retry.
• "I ran out of data." Lines stop when the balance hits zero and start again after a top-up. Point them back to #buy-proxies.
• "Can I get a refund?" Your terms decide. On revenue share you are the seller, so your refund policy is yours to write.

Delivery: let the payment do it

Hand delivery is the thing that breaks first. Twenty people buy in the same five minutes before a ticket on-sale and you're copying credentials into twenty DMs while your own tasks are running.

On a partner account, payment triggers delivery. The member's gigabytes land after payment, and their lines work on your own hostname. If you run a bot, it can fetch the lines and DM them; if not, members read them from where you've set things up.

Two rules keep it clean:

1. One member, one proxy account. Top up the same account on every repeat order. Never create a new one per purchase.
2. Reclaim from people who stop paying. Suspend takes back every unused gigabyte to your side. Use it instead of arguing in DMs.

Rotating or sticky: decide for your members

Most new buyers don't know which kind of line to use, and they will guess. Make the choice for them in the setup channel, per kind of task.

• Monitors and queue entry: rotating lines. A fresh IP per request spreads the load.
• Logged-in accounts and checkouts: sticky lines. One IP for the whole session, up to 24 hours on our network.
• Ticket queues: sticky, set long. A queue can run for an hour or more, and the purchase has to finish on the IP that joined it.

Say it as a rule, not as an option. Members who are told "sticky for checkout" follow it. Members who are told "it depends" open a ticket.

Brand it like a product, not a side channel

Members screenshot bot settings all day. If those screenshots show your hostname, your server is the brand. If they show someone else's, members go and buy there instead.

Put your own hostname on the proxy lines. The gateway's login prompt names no supplier, and members never get a dashboard or email from us.

Next step

See how the proxy reseller program is set up for servers like yours, then open a ticket in our Discord.