Private technical walkthroughs are now open for brokers and exchanges. Request A Demo
Zero-Custody Wallet Infrastructure
Broker Wallet gives every customer a unique on-chain USDT deposit address, detects payments across TRON and BNB Smart Chain, notifies your CRM in real time, and consolidates funds into treasury wallets controlled by your operation.
Deployed on your infrastructure · Validated on testnet before a single mainnet transfer
Illustration of the Broker Wallet operations console: a CRM customer record with an assigned TRON deposit address, a confirmed incoming USDT deposit with its webhook delivered to the business backend, and a treasury panel showing the sweep to the operator's Master treasury.
The Collection Problem
USDT settlement has become the default funding path for brokers and exchanges. But each of the standard ways to collect it carries a structural cost — in custody risk, in dependency, or in engineering time.
A processor takes custody of your customers' funds, sits between you and settlement, gates features behind its own roadmap, and can freeze or offboard your flow at its discretion. Your funding rail lives on someone else's terms.
Reusing a single wallet across every customer turns reconciliation into guesswork — deposits arrive with no identity attached, and a single compliance flag against that one address puts the entire flow at risk at once.
Smart contracts, chain scanners, key management, webhook retries, and an operations console represent months of specialist engineering — all of it before the first production deposit is collected.
The Gap
The missing option was infrastructure you operate yourself: non-custodial by architecture, integrated through a plain REST API, and validated end to end on testnet before a single mainnet transfer. Broker Wallet was built to be exactly that.
The Platform
Broker Wallet issues on-chain deposit wallets to your users, tracks every payment in an immutable ledger, and consolidates funds to your treasury — wrapped in an administrative console and a REST API that plugs into the systems you already run.
Every customer identity receives a permanent, unique deposit address. Allocation is idempotent — the same UserId and email always resolve to the same wallet, so requests are safe to retry.
Background scanners watch TRON and BNB Smart Chain continuously, confirm deposits at a configurable block depth, and record every movement in an append-only transaction ledger.
The moment a deposit confirms, your backend receives a GET or POST callback carrying the wallet, customer identity, amount, transaction hash, and timestamp — retried automatically until delivery.
Collected USDT moves to your Master or Backup treasury — individually, in bulk, or by balance threshold — signed by an operational worker wallet that only you control.
Console Preview
A complete preview of the operations console — every menu works: dashboard, wallets, the transaction ledger, sweeps, webhook deliveries, and locked settings.
Ledger-First Accounting · Balances Derive From Transactions, Never Stored Totals
Batch #12 · 250 Wallets · Idempotent Allocation — The Same Identity Always Gets The Same Address
Dedup Guard · TxHash + LogIndex · Every Entry One Click From Its Block Explorer
Signed By The Operational Worker · Destinations Fixed On-Chain
Payload: WalletAddress · UserId · EmailAddress · Amount · Tx · ReceivedDate
Lock-After-Save Active — Treasury And Worker Settings Cannot Rotate Quietly
Illustrative Preview — Not Live Data · Every Menu Is Clickable · Workflows Validate On Nile And Chapel First
How It Works
The entire integration surface is a single API call to hand out an address and a single webhook to hear about deposits. Everything in between is automated by the platform.
01
Your backend requests a wallet using customer identity details — a UserId and an email address.
02
Broker Wallet returns the existing address for a known identity, or assigns an available pre-provisioned wallet.
03
The customer sends USDT. The network scanner confirms the deposit at the configured block depth and records it in the ledger.
04
Broker Wallet delivers the configured webhook payload to your backend, retrying automatically until it is acknowledged.
05
The operator sweeps available balances to the Master or Backup treasury according to its own operational policy.
Zero-Custody Architecture
Zero-custody is not a policy statement — it is a property of the design. The application and the chain each hold exactly what they should, and nothing more. The boundary between them is enforced by the contracts themselves.
Runs On Your Servers
Holds records — never funds.
Lives On-Chain, Under Your Keys
Holds funds — never records.
Deposit addresses are EIP-1167 proxy contracts. They have no private key, so there is no key to steal and no hot wallet to empty.
Treasury destinations are baked into contract bytecode as immutables. A sweep can only ever land at your Master or Backup treasury.
The platform runs on your servers with your database. No processor, no managed custodian, no external service between customer and treasury.
Capability Deep-Dive
Four disciplines make up a production stablecoin collection system: allocation, detection, notification, and consolidation. Broker Wallet treats each as a first-class subsystem.
Wallets are pre-provisioned in batches so an address is ready the instant a customer asks to fund. Assignment is permanent and idempotent: a known UserId and email always resolve to the same address, and every wallet's lifecycle — requested, created, activated, allocated — is tracked with live fee estimation before creation runs.
Each network runs two scanner threads around the clock — one catching up on history, one following the chain head. Deposits are confirmed at a configurable block depth to protect against reorganizations, deduplicated by transaction hash and log index, and written to a ledger that is never edited after the fact. Balances are always derived from ledger entries, never stored as drift-prone totals.
Webhooks are configured separately per network, as GET or POST — whichever your endpoint expects. Every event carries the wallet address, customer identity, amount, transaction hash, and timestamp. Failed deliveries are retried automatically, and every attempt is recorded with its HTTP status and error message in a searchable delivery log.
Sweep a single wallet, a selected set, or every activated wallet at or above a balance threshold — with a live match count and fee estimate before anything moves. Execution is signed by the operational worker in the background; administrators never paste a private key to run a sweep. Destinations are limited to the Master and Backup treasuries fixed at deployment.
Supported Networks
Rather than spreading thin across a dozen chains, Broker Wallet is engineered specifically for the two networks that carry the deepest USDT liquidity at the lowest transfer cost — with fewer moving parts and deeper hardening as the result.
Security
The on-chain design removes entire classes of risk before they can exist, and every layer above the chain — application, session, key, and operations — is hardened independently. Built with established OpenZeppelin primitives and a compartmentalized security model.
Deposit addresses are minimal proxy contracts with no per-proxy initializer — removing an entire class of proxy-initialization attacks.
No private key is associated with any deposit proxy address. There is nothing to leak, phish, or exfiltrate at the collection layer.
No user ledger or mutable configuration lives on-chain. Treasury and authority addresses are baked into bytecode as immutables — impossible to overwrite.
Only owner-approved operational wallets can execute sweeps. Revoke a compromised worker once and it loses access to every proxy instantly.
Workers spend gas only on tokens the owner has explicitly approved. Spam and malicious tokens are rejected before any balance is read.
Full-balance sweeps are protected against reentrancy and remain compatible with both standard and legacy token implementations.
Email and password authentication with bcrypt hashing, plus TOTP two-factor codes. No default credentials ship with the platform.
HttpOnly session cookies with expiration and session-version invalidation — change the password and every other session ends immediately.
The operational worker key is stored encrypted. Deployment and owner keys are held in memory only for the duration of an operation and never logged.
Master, Backup, worker, and token contract settings lock after the first save — preventing accidental or quiet treasury rotation.
Every administrative change is captured with actor, IP address, timestamp, and a before-and-after record — searchable and filterable.
Security headers, SameSite cookies, and POST-only logout — with an administrative console designed to live behind a VPN, never on the open internet.
Administrative Control Center
One responsive console gives an operator full command of contracts, wallets, the ledger, background jobs, settings, and logs — with four workers keeping everything running underneath.
Live per-network status, active wallet counts, total derived balances, and recent activity at a glance.
Pre-flight-checked deployment of the Factory and Implementation contracts, with live progress streamed to the browser.
A searchable, sortable, paginated wallet table with per-row copy, sweep actions, and block explorer deep links.
The full deposit and withdrawal history with filters — and every entry one click from its on-chain proof.
Live job batches and tasks with progress tracking and one-click retry for anything that fails.
Network, allocation, webhook, and security settings — beside searchable webhook delivery and audit logs.
Automation · Four Background Workers
REST API Integration
Broker Wallet exposes a plain REST API for requesting addresses and querying balances, and pushes deposit events by webhook. No SDK is required — any brokerage CRM, exchange back office, or internal system that can make an HTTP call can integrate.
curl -G "https://gateway.example.com/Api/Wallets/Request" \
--data-urlencode "Network=TRON" \
--data-urlencode "EmailAddress=user@example.com" \
--data-urlencode "UserId=12345" \
-H "Authentication: YOUR_API_KEY"{
"WalletAddress": "TXyz...",
"UserId": "12345",
"EmailAddress": "user@example.com",
"Amount": "100.500000",
"Tx": "abc123...",
"ReceivedDate": "2026-05-26 14:30"
}Requesting a wallet for a known customer returns the existing address — timeouts and duplicate calls are safe to retry.
A single static API key in the Authentication header, with the public API surface enabled or disabled by one setting.
Documented HTTP status codes — 200, 400, 401, 403, 404, 409, 500 — plus a balance and history inquiry endpoint for reconciliation.
Technology Stack
A single async web application, an async database pool, four background workers, and two smart contracts — production infrastructure without operational bloat.
Who It Serves
Any platform with a user system and a backend ledger can bolt on USDT collection with one REST call and one webhook listener. Your product keeps the customer relationship — Broker Wallet handles the chain.
CRM-Native · Built For This First
A drop-in USDT funding rail for the back-office CRM: one wallet per client, a webhook on every deposit, automated reconciliation, and treasury consolidation on your schedule.
High-Volume
Customer-specific deposit addresses, real-time crediting into your existing user ledger, full transaction history, and operational control over consolidation.
White-Label-Ready
Stablecoin collection infrastructure deployed API-first on your own terms — with a custody boundary you can explain precisely to partners and counterparties.
Existing User Base
USDT collection for any business that already runs a user system and backend ledger — one REST call to assign an address, one webhook to credit the account.
Broker Wallet is deposit-collection infrastructure. It does not perform fiat conversion, card processing, KYC or AML screening, trading, or customer-facing withdrawals — those responsibilities remain with your platform, where they already live.
Deployment Journey
A guided path from installation to the first mainnet deposit, with every stage validated end to end on Nile and Chapel before real value moves.
01
Stand up the service and MariaDB on your servers, set the environment configuration, and complete the first-run administrator and two-factor setup.
02
Deploy the Factory and Implementation contracts for each network from the guided panel, with pre-flight checks and live progress.
03
Batch-create proxy wallets and enable allocation so the API can hand out addresses the moment customers ask to fund.
04
Wire the API and webhook into your CRM, send a testnet deposit, and confirm the ledger entry and callback arrive end to end.
05
After full testnet sign-off, switch the network flag to mainnet, fund the operational wallet, and start collecting.
Frequently Asked Questions
No. Deposits rest at on-chain proxy addresses that have no private key, and they move only when an operator-controlled worker wallet sweeps them to your Master or Backup treasury. The application stores the transaction ledger — never the funds.
Yes. Each customer identity is assigned a permanent, unique on-chain deposit address. Allocation is idempotent, so the same UserId and email always resolve to the same wallet.
Broker Wallet supports TRON (TRC-20 USDT) and BNB Smart Chain (BEP-20 USDT), with the Nile and Chapel testnets available for pre-production validation. The platform deliberately focuses on these two networks rather than spreading across chains it cannot support deeply.
Through webhooks configured separately for each network. When a deposit confirms, Broker Wallet sends a GET or POST callback containing the wallet address, customer identity, amount, transaction hash, and timestamp, and retries automatically until your endpoint acknowledges. Every attempt is recorded in a searchable delivery log.
Yes. Wallet allocation is idempotent by design. Requesting a wallet for a known customer identity returns the existing address rather than assigning a new one, so network timeouts and duplicate requests are harmless.
Yes. Every workflow — contract deployment, wallet creation, deposits, sweeps, and webhook delivery — can be validated on the Nile and Chapel testnets before mainnet is enabled through a single configuration change.
Balances are derived from the sum of immutable ledger entries rather than stored as running totals. Each entry is deduplicated by transaction hash and log index, which prevents double-counting and eliminates balance drift.
Yes. Master and Backup treasury destinations are fixed immutably in the smart contracts at deployment, and every sweep is directed to one of the two. No other destination is possible at the contract level.
Yes. Broker Wallet is a single Python service with a MariaDB database, deployed on servers you control. There is no mandatory managed-cloud dependency and no external service in the custody path.
Broker Wallet provides the infrastructure rails. The operator remains responsible for server hardening, database protection, key governance, backups, monitoring, and regulatory obligations in its jurisdiction.
No. Broker Wallet maintains the on-chain deposit ledger and notifies your backend about every confirmed transaction. Your platform remains the system of record for customer accounts, balances, and entitlements.
No. Broker Wallet is engineered specifically for TRON and BNB Smart Chain, where USDT liquidity is deepest and transfer costs are lowest. Support for other networks is not implied or advertised.
Next Step
A technical demo walks the live console end to end — contract architecture, wallet allocation, deposit detection, webhook delivery, and treasury sweeps — mapped to your CRM and your deployment constraints.
Write to Sales@BrokerSetup.org for sales or Info@BrokerSetup.org for anything else — mention your target networks, your CRM or backend platform, and your deployment timeline.