Security
Built so your money can only reach you
Payment platforms usually ask you to trust that nobody will misuse the keys they hold. TrLegend is designed so the most important rule doesn't depend on trust at all: the contracts that receive your customers' USDT can only send it to your wallet.
We never hold your fundsNo TrLegend balance sits between your customers and your wallet.
No key can redirect themDeposit addresses have no private key; their only exit is your wallet.
Every action is recordedWho did what and when, in a log that shows if anyone tampers with it.
Layer 1
On the blockchain
- Your own contract. Each merchant gets a dedicated factory contract on TRON with the merchant's wallet fixed inside it as the only destination.
- Only your wallet can change it. Not TrLegend staff, not our servers, and not whoever deployed the contract. Only your wallet itself can move the destination.
- Addresses are proven before use. Every deposit address is calculated twice, once by our software and once by the contract itself, and the two must match before it's issued.
- Only genuine tokens count. Payments are checked on TRON's final (irreversible) chain against each currency's verified contract, and look-alike tokens or failed transactions are never credited.
Layer 2
Moving funds
- A signer that can only sweep. The one component allowed to submit transactions can only call "sweep to the merchant's wallet" on contracts registered to that merchant. It has no general "send" ability.
- The fee wallet only pays fees. It holds a small amount of TRX for network fees and never receives customer money.
- Spending caps and a kill switch. There are daily fee caps per merchant and platform-wide, sweeps pause instantly with one switch, and they pause automatically if anything ever lands outside a merchant's wallet.
- Flagged money is held. Deposits from blocked senders stay in place for review instead of reaching your wallet, which protects it from issuer freezes.
Layer 3
Accounts & people
- Two-factor authentication for everyone. Every staff, merchant and admin account must use an authenticator app. Codes can't be reused, and recovery codes are issued once.
- Fresh 2FA for sensitive actions. Exports, API keys, webhook changes, sweep-now and role changes ask for a new code, even when you're already signed in.
- Two people for the riskiest changes. Settings, team changes, corrections and releasing held money need a second admin to approve, and nobody can approve their own request.
- Strong passwords. Passwords are stored with Argon2id. Temporary passwords must be replaced at first sign-in, and accounts lock for 30 minutes after 3 wrong passwords or 2FA codes.
Layer 4
Data & isolation
- Merchants are walled off in the database. Every record carries its merchant and the database itself refuses cross-merchant reads, so even a bug in our code can't show one merchant another's data.
- Encrypted secrets. 2FA secrets and webhook keys are encrypted at rest, and platform keys live in Google Secret Manager, never in code.
- Tamper-evident audit log. Each entry is chained to the previous one, so editing or deleting history is detected, even if done directly in the database.
- Nightly reconciliation. Our records are compared with actual on-chain balances every night, and any mismatch raises a critical alert.
Layer 5
Infrastructure
- Cloudflare at the edge for encrypted connections and protection against attacks and abusive traffic.
- Google Cloud with a private managed database, point-in-time backups, daily snapshots and least-privilege service accounts for each component.
- Signed webhooks. Every notification to your systems is signed (HMAC-SHA256) and time-stamped, so it can't be forged or replayed.
- Scoped API keys with permissions per key, optional IP allowlists, and instant revocation.
What happens to one payment
Customer paysUSDT (TRC20) arrives at the customer's own deposit address.
We verifyWe confirm the transaction succeeded on the final chain, using the genuine USDT contract, to the right address.
You're notifiedA signed webhook and your dashboard show the exact amount received, net of any exchange fee.
It reaches youThe contract sweeps it to your wallet, the only place it can go, and the books are reconciled.
Being straight with you
- An independent smart-contract audit and a penetration test are planned before mainnet launch. We'll publish the results.
- Your wallet's safety is up to you: we recommend a hardware wallet or a multisig wallet as your destination.
- USDT issuers can freeze addresses. Our screening reduces that risk for your wallet but can't remove it entirely.
Found a security issue?
Please tell us privately before sharing it. Sign in and contact the platform team, or reach us through your account manager.