Batch USDT payouts.
Your keys never leave your machine.

Payanvil is a desktop app that sends USDT (TRC-20) to hundreds of recipients in one run — no web services, no KYC, no third parties holding your funds.

Follow the build → Telegram Read the code → GitHub

v1 is feature-complete and in final hardening. Release: soon.

Why not just use a web multisender?

Because every existing option asks you to give something up.

Web dApp multisenders

Charge $15–50 per batch — and your addresses, amounts and volumes pass through someone else's website. Every single run.

Custodial processors

Hold your money on their balance and require KYC once your volume matters. Your funds, their rules.

Payroll SaaS

Built for enterprises: per-contractor monthly fees, compliance workflows, onboarding calls. Overkill when you just need to pay people.

The math is simple

Web multisenders charge per batch, forever. Payanvil is a one-time purchase.

4–10 batches
and Payanvil has paid for itself vs. per-batch web fees
$0
per batch after that — you only pay network fees
0 bytes
of your payment data sent to our servers — we don't have servers

Don't trust us. Read the code.

Payanvil asks for your private key — in crypto, that's a red flag. So every line that touches your key or the network is published for audit in payanvil-core.

🔑 Key policy

The key touches exactly two classes — both open source. Kept in memory only, zero-filled after use, never written to disk, never logged. Signing happens locally via trident, the official Tron SDK.

🗄️ Your data stays yours

Payment queue and transfer history live in a locally encrypted database. The encryption password is yours. No telemetry, no analytics, no "phone home".

Complete map of network calls

The application talks to exactly these endpoints — nothing else. Verifiable in the open code.

EndpointPurpose
Tron node (TronGrid)Balances, broadcast, confirmations, USDT blacklist check
api.binance.comTRX→USDT rate — only in "fee from recipient" mode
CoinGeckoFallback rate source
api.gopluslabs.ioRecipient reputation check (phishing / stolen funds / sanctions)
api.telegram.orgOnly if you enable the Telegram intake bot — with your own token

Built for real payout work

For teams paying contractors, e-commerce paying suppliers, OTC desks and anyone who pays many people in USDT.

📄 Excel / CSV / TXT in

Drop a file with names, addresses, purposes and amounts — get a full batch preview before anything is sent.

🤖 Telegram intake

Run your own bot (your token, your privacy): people send payment requests or files, they land in your queue.

⚖️ Fee from sender or recipient

Per-transfer choice of who pays the network fee — recipient-pays mode deducts it from the amount at a rate fixed per batch.

🛡️ Double recipient screening

USDT contract blacklist check plus GoPlus reputation screening (phishing, stolen funds, sanctions) before you confirm.

📊 Excel reports & history

Every batch produces a color-coded report; full searchable history with export — your accounting will thank you.

🌍 4 languages

English, Spanish, Ukrainian, Russian — interface and reports, switchable independently.

Pricing

One-time purchase. No subscription. No per-batch fees.

from $149 one-time
  • Perpetual license — the app is yours forever
  • 1 year of updates included
  • 1–2 machines per license
  • Testnet mode free forever — full functionality on Nile, no license needed
Get notified at release

Final pricing will be announced at launch.

FAQ

Is this a wallet? Do you hold my funds?

No and no. Payanvil is a sending tool: you bring your own Tron wallet's private key, the app signs transactions locally and broadcasts them to the network. We never see your key and never touch your funds — there is no server side.

How do I know the app doesn't steal my key?

You don't have to take our word: every class that touches the key or the network is published at github.com/Payanvil/payanvil-core. The key is handled by exactly two classes, zeroed after use, and signing goes through the official Tron SDK. Official builds are signed (macOS notarized, Windows code-signed).

Why is the core "source-available" and not fully open source?

The security-critical core is published under the Business Source License — free to read, audit, and use for research. The GUI and convenience features stay closed because that's the product we sell. We're upfront about this trade-off: the goal of the open core is auditability, and it becomes Apache 2.0 automatically in 2030.

What exactly can I do for free?

Everything — on the Nile testnet. The full application works without a license on testnet, forever. Sending on mainnet requires a license key. That's the whole difference.

Which networks and tokens are supported?

v1: USDT (TRC-20) on Tron. Multi-chain support (more networks and tokens) is planned as the next major version — v1 license holders will get an upgrade discount.

Who is behind this?

A solo developer, building in the open. Follow the devlog on Telegram and X, or write to hello@payanvil.io.