← All products

For owners of account, BM and proxy stores

An accounts and proxy store that delivers the goods right after payment

Suppliers upload TXT and ZIP files, buyers pay from their balance and download the file instantly. Replacements, refunds and supplier payouts live in one system, and buyers only ever see your brand.

teamshop · catalog
TeamShop storefront: categories, filters and product cards with the buyer’s own price
4staff roles with separate permissions
AES-256encryption for every unit in stock
7 daysdefault hold on supplier earnings
TXT · ZIPstock and delivery formats, one unit per line or archive

Sound familiar?

A store that only runs as long as you do

A supplier drops a file with 200 lines. You cut out what you need, send it to the buyer and mark it as sold in a spreadsheet. An hour later the buyer writes: “2 out of 10 won’t log in”. Which lines did you actually send? Time to scroll through the chat.

With a few sales a day it’s manageable. With three suppliers and dozens of buyers, you lose track of who you owe, who got a replacement and what’s left in stock.

So I built a store where stock, balance, delivery and refunds live in one database.

Supplier · 10:14fb_ua_7d.txt, 200 lines
Sheet · Stockrows 140–152 sent?
Buyer · 11:022 out of 10 won’t log in
Bank card+$100 — from whom?
Notesowe supplier B $?
Buyer · 11:20any bulk discount?
1One store instead of a bot, a sheet and chatsstock, balance, delivery and refunds in one database

How it works

From the supplier’s file to the buyer’s file

Goods enter the store unit by unit, and every unit has its own ID. You always know what was sold, to whom and when, and a complaint can be handled down to a specific account.

  1. 01

    The supplier uploads stock

    Every TXT line or every ZIP becomes a unit. Duplicates are dropped, and the batch goes to moderation.

  2. 02

    The buyer tops up

    A request for USDT TRC20 or a Monobank card. A manager checks the incoming payment and credits it.

  3. 03

    Buys and gets the file

    One transaction: units are locked, money is debited, and the buyer downloads a TXT or ZIP.

  4. 04

    Reports what doesn’t work

    Marks the faulty units; a manager decides on each one: replace, refund or reject.

  5. 05

    The supplier gets paid

    After the hold period the money becomes available, the supplier requests a payout, finance pays it.

Suppliers see their earnings right after a sale, but the money stays on hold for a few days. If a replacement or refund happens during that time, their share is reduced automatically.

Storefront

Every buyer sees their own price

Filters by country, kit, farm age or proxy type, exact stock and the data format before purchase. The price on the card already includes this buyer’s discount.

  • The line format is shown upfront: login:password:email:2fa…
  • Warranty and replacement terms are written on every card
  • Bulk discounts by quantity are set per product
teamshop · product
Product page: specs, discounted price, bulk tiers and buy buttons

Delivery

Pay, and the file is yours

A purchase is one transaction against the balance: units are locked, money is debited, and the supplier’s share goes on hold. The same unit can never be sold twice.

  • TXT — one line per unit, ZIP — a separate archive for each account
  • The file can be downloaded again anytime from “My purchases”
  • Neutral file names like order-1225_fb-101.txt
teamshop · order
Order page: “Payment received, goods delivered” with TXT and ZIP download buttons

Discounts & promo codes

Teams get their own price, no manual math

Customer group, personal discount or fixed price, loyalty discount and bulk tiers. The system applies the single best one. A promo code replaces it when it gives more, or stacks on top when set up that way.

  • A supplier’s product never sells below their price plus the minimum margin
  • Every line keeps a snapshot of price and discount, so rule changes never rewrite old orders
  • If the price changes between cart and checkout, the order is refused
Cart on a phone: promo code applied, personal proxy discount kept

Replacements & refunds

A decision for every unit, not the whole order

The buyer marks the exact accounts that don’t work. A manager sees their data and decides on each one: replace it from the same stock, refund it to the balance, or reject with a reason.

  • The replacement lands in the same order file
  • A unit can be compensated only once
  • A refund automatically deducts the supplier’s share
  • Reply templates and internal notes the buyer never sees
teamshop · support
Support ticket in the admin panel: two units under review with Replace, Refund and Reject options

Stock

Upload a file, get units in stock

Every TXT line or every ZIP becomes a separate unit. An archive of archives or folders is split into units automatically. Duplicates are caught both within the file and against the entire stock.

  • Every batch comes with a report: added, duplicates, errors
  • Unit contents are encrypted with AES-256-GCM and decrypted only on delivery
  • The unsold rest of a batch can be pulled from sale with one click
teamshop · stock
Product in the admin panel: in stock, sold, TXT upload and the batch table

Supplier dashboard

Suppliers stay hidden, but see their money

Buyers only see the store’s brand: no supplier names, no contacts. Suppliers upload goods and see their sales in their own dashboard, but never see the buyers.

  • Earnings show up right away; the hold period is set per supplier
  • New supplier listings and batches go through moderation
  • Payouts are requested; finance marks them paid with the transfer hash
teamshop · supplier dashboard
Supplier dashboard: on hold, available, requested, paid out, and a sales table

Admin panel

Sales, margin and what you owe suppliers on one screen

Sales for 7, 30 or 90 days, store margin, liabilities to suppliers and a list of what needs attention: top-ups, moderation, payout requests, products running low.

  • 4 roles: owner, admin, manager, finance — each sees only their sections
  • Money moves only through ledger entries; a balance can’t just be edited
  • Manual balance adjustments: owner or finance only, and only with a reason
teamshop · overview
Store overview: 7-day sales, orders, margin, chart and a “Needs attention” list

Details

The things usually left for later

01

2FA code generator

The buyer pastes an account line, the key is found automatically, and the code is computed in the browser. The key never reaches the server.

02

Prices in UAH or EUR

The system checks the National Bank of Ukraine rate every hour. Balance and payments stay in USD.

03

Loyalty and referrals

A loyalty discount grows with purchases. Partners earn a percentage of their referrals’ purchases, credited to their balance after a hold.

04

No double crediting

An explorer link, a hash with 0x or in a different case — the system recognizes the same payment.

05

Ad slots

Five places for banners or GIFs: above the catalog, in the product grid, on the product page. Impressions and clicks are counted.

06

Store documents

Replacement rules, terms of service and privacy policy are edited in the admin panel and appear in the site footer.

Who it’s for

Everyone works in their own section

Store owner

Runs several suppliers under one brand and earns on the markup. Markup rules can be set per product, supplier, category or globally.

Manager and finance

The manager handles tickets and moderation, finance handles top-ups and payouts. Sections without access simply don’t show up in the menu.

Supplier

Uploads TXT or ZIP, sees their sales, holds and payouts. Never sees buyers or their contacts.

Buyer

A media buyer or a team: tops up, buys in bulk, downloads the file right away and contacts support straight from the order.

Numbers and limits

What’s under the hood

Stack
Next.js, TypeScript, PostgreSQL
Money
Double-entry: every operation is a set of entries that sum to zero. No floating-point amounts
Goods
Unit contents are encrypted with AES-256-GCM. Staff can open only units that were already sold, and every view is logged
Top-ups
Manual: USDT TRC20 or a Monobank card. A manager checks the payment and credits it
Currency
Balance and payments in USD. Prices can be shown in UAH or EUR at the NBU rate
Import
Up to 50,000 units at once, files up to 50 MB, zip-bomb protection
Not there yet
A Telegram bot, automatic payments, a public API and 2FA for staff

FAQ

Questions

Will buyers find out who they’re really buying from?

No. The storefront, cart and files show only the store’s brand. Supplier names are visible to staff only, and suppliers never see buyers.

How do buyers top up their balance?

They create a request for USDT TRC20 or a Monobank card and see the payment details. A manager checks the incoming payment and credits it. There’s no crypto gateway with automatic crediting yet.

What if some of the accounts don’t work?

The buyer opens a ticket from the order and marks the faulty units. A manager decides on each: replacement, refund to balance, or rejection with a reason. The warranty is text on the product card — the system doesn’t run timers.

Can one account be sold to two buyers?

No. A purchase is a single database transaction: free units are locked and marked as sold right away. A dedicated test covers two buyers racing for the last unit.

When do suppliers get paid?

Earnings show up right after a sale. For a few days (7 by default) the money stays on hold so replacements and refunds can be deducted from their share. Then the supplier requests a payout, and finance marks it paid with the transfer hash.

Is there a Telegram bot?

Not yet. The store is a mobile-friendly website. A bot and a Mini App are planned, but they don’t exist today.

Can I use my own name and colors?

Yes. The store name, one of 4 themes and light or dark mode are all changed in the admin panel.

Let’s talk about launching your store

I’ll walk you through the storefront, supplier dashboard and admin panel, and we’ll figure out what your catalog needs.

Discuss on Telegram