Wallets
Every HelaMesh merchant gets a non-custodial HD wallet at signup. You own the funds — HelaMesh never holds your keys.
How it works
When you sign up, HelaMesh generates a 24-word BIP39 seed phrase and encrypts it server-side using AES-256-GCM. The seed never leaves the server in plaintext. From that seed, HelaMesh derives a BIP44 HD wallet for each supported chain:
| Chain | Coin type | Derivation path |
|---|---|---|
| TRON | 195 | m/44'/195'/0'/0/N |
| BSC | 60 (EVM) | m/44'/60'/0'/0/N |
N is the derivation index. Index 0 is your main address — shown in the dashboard and used for outbound sends. Indexes 1, 2, 3… are used for per-invoice payment addresses so every invoice gets a unique receiving address.
What this means for you
- Funds go directly to your wallet. Customers pay to a unique address derived from your seed. HelaMesh monitors that address and fires your webhook when payment is confirmed — but the USDT lands with you, not HelaMesh.
- No custody risk. HelaMesh cannot move your funds. The encrypted seed can only be decrypted with your OTP-verified session.
- Export at any time. Go to Wallets → Export phrase in the dashboard. You'll receive a 6-digit OTP by email. After verifying, your 24-word phrase is displayed and you can import it into Trust Wallet, MetaMask, or any BIP44-compatible wallet.
Programmatic wallet derivation
If you're building a platform where your own users need individual wallet addresses (e.g. a payment app, savings product, or exchange), HelaMesh supports HD sub-wallet derivation via API. Your users share your master seed — each one gets a unique address at a different HD index. See Derive sub-wallets.
Sending USDT
You can send USDT from your main wallet (index 0) directly from the HelaMesh dashboard, or programmatically via API. See Send USDT.